Stakeholder Engagement for Delivery Leads

Why Stakeholder Trust Breaks Down

Stakeholders don't lose trust because of bad news. They lose trust because of surprises. If you tell them early that something is at risk, they can help. If you tell them the day before the deadline, they feel blindsided.

The formula is simple: Early transparency + clear asks = trust.

The Stakeholder Engagement Model

1. Map Your Stakeholders

Not all stakeholders need the same level of engagement. Use a simple 2x2:

• High power, high interest: Manage closely (weekly updates, 1:1s)
• High power, low interest: Keep satisfied (monthly summary, escalation only)
• Low power, high interest: Keep informed (newsletter, team demos)
• Low power, low interest: Monitor (quarterly update)

2. Set Expectations Early

In the first week of any programme, align on:

• What "done" looks like (scope, quality, timeline)
• How often they'll hear from you (cadence)
• What format updates will take (email, meeting, dashboard)
• How decisions will be made (who decides, who advises)
• What you need from them (decisions, resources, access)

3. The Weekly Update Format

Keep it to 5 lines maximum:

` PROGRESS: [What was delivered this week] NEXT: [What's planned for next week] RISK: [Top risk and what we're doing about it] ASK: [Decision or support needed from you] CONFIDENCE: [Green/Amber/Red with one-line reason] `

Send this every Friday at the same time. Consistency builds trust.

4. Managing Difficult Conversations

When delivering bad news:

• Lead with the impact, not the excuse
• Present options, not just problems
• Be specific about what you need from them
• Give them time to react before asking for a decision

When saying no:

• Acknowledge the request genuinely
• Explain the trade-off clearly: "If we add X, we lose Y"
• Offer alternatives: "We can't do it this sprint, but we can do it next"
• Document the decision so it doesn't come back

When they change their mind:

• Don't resist — understand why
• Quantify the impact: "This adds 2 weeks and costs £X"
• Get formal sign-off on the change
• Update the plan and communicate to the team

5. Decision Logs

Every decision should be documented:

• What was decided
• Who decided it
• When it was decided
• Why (the rationale)
• What alternatives were considered

This prevents "I never agreed to that" conversations. It also helps new stakeholders understand context.

Building Trust Over Time

Be predictable. Same format, same cadence, same level of honesty. Stakeholders should never wonder "what's happening?"

Underpromise, overdeliver. If you think it'll take 3 sprints, say 4. Delivering early builds trust. Delivering late destroys it.

Share credit generously. When things go well, credit the team publicly. When things go wrong, own it personally. This is leadership.

Make their life easier. Anticipate their questions. Provide the data they need before they ask. Format updates for their audience (board, investors, customers).

Anti-Patterns

• Hiding bad news — it always comes out, and later is always worse
• Over-communicating — 10 emails a week is noise, not communication
• Asking for decisions without options — always present 2-3 choices
• Treating all stakeholders the same — the CEO and the team lead need different things
• Only communicating when you need something — build the relationship before you need it

---

Use the [Stakeholder Update template](/templates) format for consistent, trust-building communication.