Bonus 7 — Stakeholder Management & Cross-functional Leadership

60-Second Summary

Bonus module 7 of the program (Critical Skills extension). Theme: Managing sideways — the skill most new managers fail on.
Weekly stakeholder check (15 min, Fridays) — the ritual you install.
Same rhythm as weeks 1–12: pre-read, cohort live, ritual, falsifiable homework.
Closes a high-priority gap most new-manager programs ignore.

First-time managers spend ~60% of their week on lateral and upward work — alignment meetings, escalations, executive comms, negotiations with peers. Yet most training treats direct reports as the whole job. This module names the skill explicitly: managing sideways. You will leave with a stakeholder map, a written influence strategy per stakeholder, and a rehearsed escalation script.

What the evidence says

CCL research: 'managing up and across' is the #1 derailer of new managers, ahead of feedback delivery and delegation.
Gallup: managers who report strong cross-functional relationships are 2.3× more likely to hit goals than those who don't.
Cialdini's influence principles (reciprocity, commitment, social proof, authority, liking, scarcity) remain the most-cited evidence base for influence without authority — used routinely by product/program management.

Pre-read (60 minutes)

Read: the four quadrants of stakeholders — high power/high interest, high power/low interest, low power/high interest, low power/low interest — and how each is managed differently (20 min).
Read: Influence without authority — Cohen & Bradford's currencies-of-exchange model (20 min).
Read: executive communication — BLUF (bottom-line up front), the 30-second update, the one-page memo (15 min).
Reflect (5 min): list every stakeholder you depend on this quarter. Mark each: ally, neutral, blocker, unknown.

Live session (90 minutes)

Cohort flow with a senior coach

1
Stakeholder map (20 min)
Each manager draws their stakeholder map on paper: 4 quadrants × power/interest, then overlay ally/neutral/blocker. Coach challenges: who is missing? Who do you avoid?
2
Currencies of exchange (20 min)
For each blocker, name what they care about (recognition, resources, risk reduction, status, information). Coach demonstrates how to ask for what you need by paying in their currency, not yours.
3
Executive update role-play (20 min)
Pairs practice the 60-second exec update: outcome, status (R/Y/G), top risk, ask. Coach gives the harsh edit — most updates are 3× too long and bury the ask.
4
Escalation script (20 min)
Scenario: another team's missed dependency is about to slip your goal. Coach demonstrates the four-move escalation — name the impact, name what you've tried, name what you need, name the decision date. Pairs rehearse.
5
Wrap (10 min)
Each manager commits to one new stakeholder relationship to invest in this month and one overdue escalation to send this week.

The ritual you install

Weekly stakeholder check (15 min, Fridays)

Once a week, scan your stakeholder map. For each high-power stakeholder, ask: when did I last give them something (information, recognition, help)? When did I last ask for something? Any relationship debt accumulating? Send one proactive update or thank-you per week to a stakeholder you don't directly report to.

Modern tools for this skill

Category	Examples (2026)	Use
Stakeholder mapping	Miro / Mural templates, FigJam, Notion stakeholder DB	Visualise power/interest and ally/blocker; revisit quarterly
Async exec updates	Loom, Granola, Linear updates, Notion weekly memo	Push status to leadership without booking their calendar
Working agreements	RACI matrix, DACI template, team API doc	Make cross-team interfaces explicit before they break
Negotiation	Voss's 'Never Split the Difference' tactical empathy, Fisher & Ury BATNA	Frameworks tested in adversarial conversations

Copy-paste AI prompt

I have a cross-functional escalation to send. Context: [my team's goal, the dependency, what's slipping, what I've already tried, who I need to act and by when]. Draft: (1) a 60-second exec summary using BLUF, (2) a one-page memo to the blocking team's leader, (3) an escalation note to my skip-level with a clear ask and decision date.

Homework — falsifiable artefacts

Stakeholder map drawn and stored; reviewed with your manager.
One executive update written using BLUF — sent and saved.
One overdue escalation sent with named decision date.
One proactive relationship investment made (info share, recognition, offer to help) with a peer outside your function.

Success signal

By end of this module, you can name every stakeholder you depend on this quarter, you have a written one-line influence strategy per blocker, and your last three exec updates fit on half a page with the ask in the first sentence.

Reviewer notes

HR Director (15+ yrs)

The managers who get promoted are not the ones with the best teams — they're the ones whose names come up positively in other functions' staff meetings. Cross-functional reputation is built in 100 small interactions; this module is the system that makes those interactions deliberate instead of accidental.

Line Manager (20+ yrs)

In twenty years I've never seen a manager fail because of their reports. I've seen many fail because Product hated working with them, or Legal stopped picking up the phone. Sideways management is the job — direct reports are the deliverable.

OB / HR Professor (25+ yrs)

Mintzberg's classic time studies show senior managers spend less than a third of their week on direct reports; the rest is lateral and external. The skill compounds: every cross-functional relationship is a permanent asset or a permanent liability.

Written by Pawan Joshi.Sources cited inline.

First published 30 Jun 2026See site changelog →