Stakeholder Leadership and Executive Communication

Stakeholder Mapping

Before attempting to influence or communicate with stakeholders, map them.

Power / Interest Grid

             HIGH INTEREST
                  │
    MONITOR       │      MANAGE CLOSELY
    (Keep         │      (Active engagement;
    informed;     │       meeting, briefing,
    watch for     │       collaborative)
    shifts)       │
──────────────────┼──────────────────────
    MINIMAL       │      KEEP SATISFIED
    EFFORT        │      (Regular updates;
    (Peripheral)  │       manage concerns;
                  │       limited deep engagement)
                  │
             LOW INTEREST
    LOW POWER          HIGH POWER

Manage Closely (high power, high interest): These are the critical stakeholders. Engage frequently; involve them in decisions; surface bad news to them before it spreads.

Keep Satisfied (high power, low interest): Can derail the project if disengaged or surprised. Give them regular status; avoid surprising them with problems.

Monitor (low power, high interest): Often informal influencers. Can build coalition support or resistance. Keep them informed; watch for them gaining power as the engagement progresses.

Coalition Building

Identify which stakeholders are natural allies (aligned on the project objective) and which are skeptics or opponents. Build support with allies before difficult steering committee meetings. Understand opponents’ objections — often they reflect legitimate risks or organizational realities.

---

Executive Communication: BLUF Format

Bottom Line Up Front (BLUF) is the executive communication standard. Busy executives make decisions before they read the supporting material. Structure every executive communication to lead with the answer.

BLUF Structure

1. SITUATION: One sentence of context (what we're addressing)
2. RECOMMENDATION or FINDING: The answer (what we recommend, or what we found)
3. RATIONALE: 2-3 bullets of supporting evidence
4. IMPLICATIONS or NEXT STEPS: What happens next / what decision is needed
5. [Supporting detail if needed — appendix-level]

Anti-pattern: Presenting the analysis process (here’s what we did, here’s what the data showed, here’s what we found…) and burying the recommendation at the end. Executives often disengage before the punchline. Lead with the conclusion.

Elevator Pitch Structure

For spontaneous executive conversations (hallway, pre-meeting small talk):

1. What we’re working on (1 sentence)
2. What we’ve found so far (1 sentence)
3. What we’re asking for or what they should know (1 sentence)
4. Stop talking — let them respond

---

Difficult Conversations: SBI Feedback Model

For delivering critical feedback to a client, a colleague, or a team member — without triggering defensiveness:

S — Situation: Describe the specific context (“In the steering committee on May 10th…”) B — Behavior: Describe the observable behavior, not the interpretation (“…you interrupted the analysis presentation three times before the data was on the screen…”) I — Impact: Describe the impact on you, the team, or the project (“…which caused the client team to disengage and we lost the opportunity to get alignment on the findings.”)

SBI avoids:

• Generalizations (“You always do this”)
• Character judgments (“You’re dismissive”)
• Accusations without evidence

Follow SBI with a question: “What was going on for you in that moment?” This invites dialogue rather than defense.

---

Managing Up

Briefing senior leaders — both client and internal — is a distinct skill.

Principles:

• No surprises: Brief them on bad news early and privately, before it surfaces publicly. “I wanted to make sure you heard this from me first” is a trust-building phrase.
• Frame the decision, not the analysis: “You need to decide between A and B. A gives us X but costs Y. B gives us less X but costs half. What’s your preference?” Not: “Here are 47 slides of analysis.”
• Respect their time: If you asked for 30 minutes, use 25 and offer to go back with detail later. Never run over without explicit permission.
• Know what you’re asking for: Do you need a decision? Awareness? Resources? Specify at the top of the meeting.

---

Reading the Room

Signals of stakeholder disengagement or resistance:

• Side conversations during presentation
• Phone checking with increasing frequency
• Interruptions that redirect the topic
• Questions that are actually objections in disguise (“Have you considered…?” = “I don’t think you’ve considered…”)
• Short, flat answers to engagement questions (“Sure,” “Fine,” “We’ll see”)

Response protocol:

1. Name what you observe (“I want to make sure we’re addressing the right question — it feels like there may be a concern I haven’t addressed yet.”)
2. Create space for the real objection to surface
3. Don’t steamroll past disengagement — it will resurface as opposition later

---

Navigating Client Politics

Every client organization has a political landscape. Navigating it without becoming part of it:

• Maintain neutrality in internal client conflicts — your job is to help the organization, not take sides
• Avoid being used as a weapon (“Tell them what you told me about their process”) — redirect to data
• Build relationships across organizational layers, not just with your main sponsor
• Be aware when your recommendations will create winners and losers internally — plan stakeholder communication accordingly
• If a stakeholder is actively blocking progress, escalate within the engagement (to the project sponsor) rather than working around them