Module 6

Effective Communication and Stakeholder Management

Lead without authority — structure your thinking, write clear PRDs, align stakeholders, negotiate trade-offs and communicate with every function.

≈ 9 h studyDraftedSources: Lectures 13, 14, 18, 22, 24, 30, 52, 53; Companion ch. 18, 19; Extra topics 11, 15

Mark module complete Expand all

On this page

1. Why communication is the PM's core tool
2. Structured problem-solving communication
3. Storytelling with data
4. Stakeholder mapping and influence
5. Cross-functional collaboration
6. Negotiation and conflict resolution
7. Decision-making meetings
8. Writing PRDs
9. Engineering collaboration
10. Communicating with every function — dialogue examples
11. Handling conflicting priorities and difficult stakeholders
12. Customer empathy
13. Giving and receiving feedback
14. Leadership communication and executive product reviews
15. Exercises with model answers
16. Interview perspective
17. Key takeaways
18. Check your understanding
19. Recommended resources

6.1 Why communication is the PM's core tool

PMs rarely have formal authority over the people who build, sell or support the product. Influence comes from clarity, evidence, trust and consistency. Most PM failures are communication failures: unclear problems, unshared trade-offs, surprises, or decisions nobody wrote down.

Principles

1. Start with the answer (then support it).
2. Know your audience — what decision do they need to make, and what do they care about?
3. Make trade-offs explicit — options, cost, benefit, risk.
4. Separate facts, assumptions and opinions — label each.
5. Write it down — decisions, owners, dates.
6. No surprises — share bad news early, with a plan.
7. Listen more than you talk — especially with customers and engineers.

6.2 Structured problem-solving communication

6.2.1 The Pyramid Principle and SCQA

Barbara Minto's Pyramid Principle: lead with the governing thought (answer), group supporting arguments (ideally mutually exclusive and collectively exhaustive, MECE), and support each with evidence. SCQA frames the opening: Situation → Complication → Question → Answer.

6.2.2 Executive summaries

An executive summary fits on one screen: the ask/decision, the recommendation, why (2–3 bullets with numbers), risks and mitigations, what you need (people, money, decision by date). Put it at the top of every doc.

6.2.3 STAR and PREP

• STAR (behavioural answers): Situation, Task, Action, Result — with your actions and a real result (or say it wasn't measured).
• PREP (quick opinions and updates): Point, Reason, Example, Point — great for meetings and 60-second answers.

Situation	Structure	Shape	Typical length
Recommendation to leadership	Pyramid + SCQA	Answer → reasons → evidence	1 page / 3 minutes
Behavioural interview story	STAR	Situation → Task → Action → Result	2 minutes
Opinion in a meeting or stand-up	PREP	Point → Reason → Example → Point	30–60 seconds
Feedback to a colleague	SBI	Situation → Behaviour → Impact → ask	2 minutes
Bad news / incident	What · impact · cause · plan · next update	Facts first, then plan	5 sentences

6.3 Storytelling with data

Data persuades when it answers a question for a specific audience. Principles (in the spirit of Cole Nussbaumer Knaflic's Storytelling with Data):

1. Lead with the takeaway as the chart title (“Checkout loses most users at payment”), not “Funnel Q1”.
2. Choose the right chart: trend → line; comparison → bar; part-to-whole with few parts → stacked bar; distribution → histogram; relationship → scatter. Avoid 3D and pie charts with many slices.
3. Remove clutter; highlight the one thing that matters with colour.
4. Give context: baseline, target, comparison period, sample size.
5. Show uncertainty (ranges, confidence intervals).
6. End with the action you want.

6.4 Stakeholder mapping and influence

Stakeholder mapping identifies who matters and how to engage them. The power–interest grid: manage closely (high power, high interest), keep satisfied (high power, low interest), keep informed (low power, high interest), monitor (low, low).

Decision-rights frameworks

• RACI — Responsible (does the work), Accountable (one person owns the outcome), Consulted (two-way input), Informed (kept updated).
• DACI — Driver (runs the decision process), Approver (one person decides), Contributors, Informed. Useful for product decisions.

Role	Who	What they do
Driver	PM, Checkout	Frames options, gathers evidence, schedules the decision
Approver	Head of Product	Makes the call by the agreed date
Contributors	Design, Eng lead, Analytics, Payments, Legal	Provide input, risks, estimates
Informed	Support, Marketing, Sales	Told the decision and its implications

Influence without authority — what actually works: shared goals (“we both want fewer failed payments”), evidence, reciprocity (help others hit their goals), early involvement (“co-authors defend what they wrote”), credibility through follow-through, and making it easy to say yes (clear asks, small first steps).

6.5 Cross-functional collaboration

6.6 Negotiation and conflict resolution

Negotiation principles (from Getting to Yes, Fisher & Ury): separate the people from the problem; focus on interests, not positions; invent options for mutual gain; use objective criteria; know your BATNA (best alternative to a negotiated agreement).

Sales position

• “Build custom reports for Client X by June.”

Product position

• “Not this quarter — checkout comes first.”

Sales interest

• Keep a ₹40 lakh renewal
• Client's finance team needs monthly numbers

Product interest

• Hit the checkout-completion goal
• Avoid one-off custom features

Options that serve both

• Scheduled CSV export in 2 weeks (meets the client's job)
• Custom reports evaluated in Q3 with evidence from other clients

Conflict modes (Thomas–Kilmann): competing, collaborating, compromising, avoiding, accommodating.

PMs default to collaborating for important, high-trust issues; compromising for time-bound trade-offs; accommodating on low-stakes items to build goodwill; avoid only for trivia.

A conflict-resolution sequence: (1) restate each side's interest until they agree you understood; (2) agree on the shared goal and decision criteria; (3) lay out options with evidence; (4) decide — or escalate together with a joint summary; (5) document and move on.

6.7 Decision-making meetings

• Before: circulate a one-page decision brief 24–48 hours ahead (context, options, recommendation, evidence, open questions); state the decision type (decide, consult, inform).
• During: confirm the decision and decider; walk through options and trade-offs; invite dissent explicitly (“what would make this wrong?”); decide or agree what information is missing.
• After: within 24 hours send the decision, rationale, owner, next steps and review date.

6.8 Writing PRDs

A PRD aligns the team on the problem and intended solution. It is a living document, sized to the team's needs.

1 · Summary & decision

• One paragraph: problem, proposal, expected impact
• Status, owner, reviewers, last updated

2 · Problem & evidence

• Who, what task, why it's hard
• Data, research, quotes (with sample sizes)

3 · Goals & success metrics

• Primary outcome metric and target
• Leading indicators; guardrails

4 · Users & use cases

• Segments/personas
• Key scenarios and edge cases

5 · Scope

• In scope / out of scope
• Assumptions and dependencies

6 · Requirements

• User stories + acceptance criteria
• Non-functional: performance, security, accessibility, privacy

7 · Design & analytics

• Links to flows/prototypes
• Tracking plan (events, properties)

8 · Launch & risks

• Rollout plan, flags, rollback
• Risks + mitigations; open questions; decision log

6.8.1 User stories and acceptance criteria

• User story: As a [user], I want [capability] so that [benefit].
• INVEST checklist: Independent, Negotiable, Valuable, Estimable, Small, Testable.
• Acceptance criteria: testable conditions, often written Given / When / Then.
• Definition of Ready (criteria before work starts) vs Definition of Done (quality criteria for completed work).

6.8.2 Writing one-pagers

A one-pager pitches an idea before a full PRD: problem, why now, who, proposed approach, expected impact (with range), cost, risks, the ask. If you can't write it on one page, the idea isn't clear yet. (Amazon popularised the related PR/FAQ — a mock press release and FAQ written before building — as a way to test whether the customer benefit is compelling.)

6.8.3 Jira and Confluence in the workflow

6.9 Engineering collaboration

• Involve engineers in discovery — they often see the simplest solution.
• Ask for estimates as ranges with assumptions, not commitments on the spot.
• Story points are relative effort for a team's planning — not a productivity score and not comparable across teams.
• Trade scope, not quality: offer smaller slices before asking for overtime.
• Respect technical debt — reserve capacity; understand the cost of delay of not fixing it.
• Be available during the sprint to answer questions quickly.

6.10 Communicating with every function — dialogue examples

6.11 Handling conflicting priorities and difficult stakeholders

Conflicting priorities: bring them to a common yardstick (the goal and a framework such as RICE or cost of delay), make trade-offs visible, escalate jointly if needed with a one-page options paper, and record the decision.

Difficult stakeholders — patterns and responses

6.12 Customer empathy

Empathy is understanding the customer's situation and feelings well enough to make better decisions — not agreeing with every request. Practise it through regular customer calls, listening to support calls, reading tickets, using the product as a new user, and shadowing operations.

6.13 Giving and receiving feedback

SBI model: Situation (when/where), Behaviour (observable, not judgement), Impact (effect on you, team, user). Then ask, listen and agree next steps.

Receiving feedback: thank, clarify, don't defend in the moment, decide what to act on, close the loop.

Audience	Format	Cadence	Contents
Leadership	One-page update	Weekly / fortnightly	Metrics vs target, decisions needed, risks
Cross-functional partners	Channel post + sync	Weekly	Progress, blockers, upcoming asks
Support & sales	Release notes + FAQ	Per release	What changed, how to explain it, known issues
Whole company	Demo / newsletter	Monthly	Outcomes and learnings
Anyone affected by an incident	Incident message	Immediately, then on a schedule	Impact, plan, next update time

6.14 Leadership communication and executive product reviews

Executives want: the decision you need, how it serves the strategy, the numbers, the risks, and what you're not doing. Prepare for an exec review:

1. One-page memo at the top (or a 6-page narrative memo in memo-culture companies).
2. Metrics vs targets with honest status (green/amber/red with reasons).
3. Learnings — what surprised you, what you stopped.
4. Decisions needed — clearly listed.
5. Appendix for detail; anticipate the three hardest questions.

Delivering bad news: state it plainly, the impact, the cause (if known), what you're doing, what you need, when you'll update next.

6.15 Exercises with model answers

Model answer

“Recommendation: test showing the delivery fee in the cart, starting next sprint. Why: (1) 30% of checkout starters leave at payment; (2) 6 of 8 interviewees cite fee surprise; (3) engineering estimates a simplified v1 at ~2 weeks (full live estimate ~2 months). Ask: approve the two-week v1 and an A/B test; loyalty moves to Q3.”

Model answer

Given a logged-in user with no saved addresses, when they complete an order with a new address, then offer “Save this address” (unchecked by default). Given a user with saved addresses, when they open checkout, then show up to 5 most recent addresses with the last used pre-selected. Given a saved address fails validation, when it is selected, then show a plain-language error and an Edit option without losing the cart.

Model answer (example)

Manage closely: Head of Risk (co-design KYC changes), Compliance (review copy and consent). Keep satisfied: CFO (monthly KPI summary). Keep informed: Customer Support (training and macros), Marketing (launch messaging). Monitor: partner bank's ops team (notify of timeline). Re-map after the pilot.

6.16 Interview perspective

“Tell me about a time you influenced without authority.” — STAR model answer outline

S: Team wanted to build a feature a large client requested; I believed checkout reliability was more urgent. T: Align sales, engineering and my VP on priorities. A: Pulled funnel data and support tags, quantified lost orders, met sales to understand the client's real need, proposed a 2-week workaround for the client, and presented options with a recommendation. R: We fixed payment retries first; failed-payment recoveries rose (state the real measured number — or say it wasn't measured); the client accepted the workaround and renewed. Learning: start with shared goals and offer options. Mistake to avoid: inventing results or describing only what the team did.

“How would you communicate a delayed launch to executives?” — 60-second answer

“I'd tell them as soon as I know, in one message: the launch will slip by two weeks; the cause is a payment-gateway certification we underestimated; the impact is roughly X orders and no customer-facing risk; options are to launch without the new payment method or wait; my recommendation is to wait because the old flow is the main pain point; and I'll update them every Friday until launch. Then I'd document the learning for future estimates.”

6.17 Key takeaways

• Answer first (Pyramid/SCQA); support with MECE reasons and evidence.
• Use STAR for stories and PREP for quick points; never invent outcomes.
• Make decision rights explicit (RACI/DACI) and write decisions down.
• Negotiate on interests, with options and objective criteria.
• PRDs are living alignment tools: problem, metrics, scope, testable requirements, risks.
• Tailor to each function's needs; no surprises.

6.18 Check your understanding

6.19 Recommended resources

• Barbara Minto, The Pyramid Principle — publisher page.
• Cole Nussbaumer Knaflic, Storytelling with Data.
• Fisher, Ury & Patton, Getting to Yes — Harvard Program on Negotiation.
• Atlassian: DACI decision-making framework.
• Atlassian Support: Create a Jira work item and Use Jira and Confluence together (from your course notes).
• Center for Creative Leadership: SBI feedback model.