The Situation
A delivery slipped, and the stakeholder is escalating frustration and losing trust.
The Answer
Your first move isn’t fixing the plan — it’s stabilising trust. Stakeholders can tolerate delays; they struggle with surprises and silence.
Acknowledge the miss quickly and clearly. No defensiveness, no over-explaining. State what happened in simple terms and take ownership as the manager, even if the issue sits within the team.
Then give them something solid: what you know, what you don’t yet know, and when you’ll update them. This reduces uncertainty, which is usually what’s driving the emotion.
Internally, separate two things: immediate recovery and root cause. Don’t run a full post-mortem while the house is still on fire. Focus first on: what can be delivered, by when, and what trade-offs are required.
Once stabilised, then look at why it happened — estimation, dependencies, unclear scope, or lack of escalation.
What to Do Next
- Contact the stakeholder quickly — don’t wait
- Acknowledge the miss and take ownership
- Share a revised short-term plan (even if partial)
- Set a clear next update time
- Run a root cause review after stabilisation
Common Mistake
Going silent while trying to “fix it first” — which damages trust more than the delay itself.
How the Companion Helps
Guides you through structuring the stakeholder message, captures decisions and trade-offs, and helps you reflect afterwards to prevent repeat issues.
Source: Real-world IT delivery scenario ---
Bring this to your AI Companion
The answer above is universal. Your situation isn't. The Companion takes this same situation and works through it with you — with your team, your stakeholders, your context.
Reflect with the Companion