This chapter is about the part of product work that no framework covers: how influence actually flows through an organization, and what to do once you know. It moves from the claim that alignment matters more than correctness, through mapping real (informal) power and interviewing stakeholders before pitching them, to the mechanics of surfacing hidden disagreement, reading organizational signals that mislead, handling conflict that turns out to be real, and maintaining the trust that makes any of it survive. Most of the material is practitioner report — heavily weighted toward Bruce McCarthy and Melissa Appel's Align, with contributions from Tamar Yehoshua, Tom Verrilli, John Cutler, Stukan, Osterwalder and the Wiz story.
The organizing claim of this chapter belongs to Bruce McCarthy and Melissa Appel: once the hard mechanics of building a product are in place — roadmapping, process, delivery — the soft, relational work of managing stakeholders is what actually determines whether the product succeeds. They call it the secret lubricant behind success, the topic nobody talks about relative to its actual leverage. The claim is deliberately uncomfortable: it says a technically correct decision, made by a competent team, in an organization that is not aligned behind it, will not be executed well.
Their own case study makes the point sharper than an argument would. One of the authors had, by his own account, genuine product-market fit for an idea that later became — in essence — Vista Print, a company eventually worth roughly $2 billion, once someone else executed the same idea with organizational alignment behind them. "I invented Vista Print before Vista Print." The interesting part isn't the missed opportunity. It's that being right about the idea generated exactly zero value; alignment behind the idea is what turned it into a company.
The second leg of the foundation is a caution against your own confidence, drawn from Kathryn Schulz's Being Wrong: at the exact moment you are wrong about something, it feels indistinguishable from being right. There is no internal signal for error — the realization only ever arrives afterward, from new evidence or from someone else's pushback. Applied to stakeholder work, that produces a blunt formulation: even if you're right, they have the power, and you will not get what you want unless you stay open to being shown wrong and realigning.
So this chapter assumes the strategy work of Strategy, Vision, and the Decision Stack and the planning work of Roadmaps, Prioritization, and Outcomes have been done honestly, and asks the next question: how does a decision that is defensible on the merits acquire enough organizational backing to actually happen?
McCarthy and Appel's advice about the reporting hierarchy is unusually direct: "ignore that, just put it in the trash — it's got nothing to do with how decisions really get made or how power is distributed throughout the organization." In its place they describe "the Matrix" — the real, informal network of influence, populated by Power Players whose backing can fund or kill an initiative regardless of their formal title.
A specific and easily-missed subtype is worth naming on its own: CEO Whisperers, people with informal, high-trust access to an executive despite no senior title and no direct reports. You identify them behaviorally, not structurally — daily coffee chats with the executive, showing up uninvited to meetings and asking pointed questions. Because none of that appears on paper, they are systematically absent from any stakeholder list assembled from the formal hierarchy.
Where to look for these people is a separate question from who they are, and it has its own answer: every company has a dominant function that disproportionately shapes decisions — sales-, marketing-, engineering-, or PE/finance-driven. The diagnostic evidence is observable rather than declared: who receives cross-departmental awards, who can still hire during a general hiring freeze, and who has regular informal access to the CEO's ear. (One tell for finance dominance specifically: the "Rule of 40" showing up as an organizing metric, which is disproportionately common in PE-owned companies.) McCarthy's own case is the cleanest illustration — he assumed his e-commerce employer was engineering-led because he sat among hundreds of engineers. Sales was the real power center, visible only through indirect clues: sales alone gave out cross-departmental awards, sales alone could hire during a company-wide freeze, and the CEO's daily coffee ritual was with the head of sales operations. None of it was on the org chart; all of it showed up in who could get things done.
The artifact that replaces the org chart is the Stakeholder Canvas (a free download at alignthebook.com): a list of the power players who matter for a given decision and the specific role each plays in that decision, rather than their title or reporting line. An optional layer classifies each entry by DISC category — Dominance, Influence, Steadiness, Conscientiousness — to inform how each person should be approached. The provenance of that layer is itself a small lesson: the authors built their own personality framework first, found it roughly 90% identical to the existing DISC model, and adopted DISC instead of publishing a redundant one.
One more mapping move, from Christian Idiodi, applies when you join an unfamiliar team: find the smartest person in the room — not whoever holds the title, but whoever the room actually defers to. The tell is behavioral, as with the Matrix generally: watch for colleagues double-checking with a particular person before decisions get finalized, and treat that person as the source to learn from.
The default move with a stakeholder is to present a plan. The techniques in this chapter almost all invert that order. The stakeholder interview is modeled directly on the customer interview: before showing anything, ask about their job, how they define success and failure in it, how their boss measures them, and what's keeping them up at night. The goal is to locate the genuine overlap between their goals and yours before attempting to persuade anyone of anything.
What makes that work is a posture most people resist. Opening from vulnerability — "I don't know, you tell me" — builds more credibility than performing expertise. The illustration is a speaker's father selling Polaroid cameras by telling customers "you tell me what it does, I don't know" and having them explain the product back to him, which doubled as an informal interview into how customers actually understood it. The claim in the source is strong: admitting what you don't know is "the biggest credibility booster you can possibly have." The Wiz version is the highest-stakes instance in this chapter — VP Raaz Herzberg was running 10–15 customer calls a day, and weeks in admitted to the team, not just to herself, that she still didn't understand what they were building. That admission, rather than any of the calls' surface-level positive reactions, is what triggered the pivot from network security to cloud security.
Alex Osterwalder supplies the analytic version: apply jobs, pains and gains to the skeptical executive themselves — treat their job-to-be-done as the thing you're designing for, the same way you'd design a value proposition for a customer, and deliberately avoid methodology jargon like "Lean Startup" or "testing" while doing it. That reframes internal buy-in as a design problem rather than a persuasion problem. The classic five levels of why is the drilling tool: ask why repeatedly, with genuine curiosity rather than a prosecutorial tone, to find the real objective under the stated request. It also runs in reverse — state the implied conclusion out loud ("so that would imply we should do this and not that") and watch whether the stakeholder still agrees.
Once you understand what they want, the next move is to stop treating them as a reviewer. Asking for advice means approaching a power player while the plan is still unfinished — "I have a couple of questions you could help with" — so they contribute actual input and acquire standing to share credit later. The structural, upstream version is the IKEA effect: people value what they helped build, so a roadmap stakeholders co-created is far harder for them to reject and far more likely to be defended by them to others. Some practitioners call this "Inception" — leading someone to believe your idea is theirs. Chandra Janakiraman applies the same effect to strategy documents: having the working group co-author the doc, rather than having a PM write it solo and present it, is what makes the alignment durable, because "something that comes from you feels a lot more familiar and easy to accept."
Two narrower buy-in tactics round this out. Tying an initiative to a priority an executive already champions — a warehouse-direction project pitched in terms of an existing damage-reduction initiative rather than on its own merits — works because it borrows an existing commitment instead of asking for a new one. And when the stakeholder's scarce resource is bandwidth rather than openness, Stukan (CEO, Bizzy) advises framing your request as help with what they're already trying to ship, not as one more competing ask.
The single most-repeated warning in this chapter is that apparent consensus in a room is usually shallow. McCarthy and Appel illustrate it with a cartoon of people nodding along while their thought bubbles show completely different shapes. Mining for conflict — the term is borrowed from Patrick Lencioni's The Five Dysfunctions of a Team — is the discipline of actively probing for the disagreement people won't volunteer: asking pointed follow-ups, inviting dissent explicitly, and treating a too-quiet room as a signal to dig rather than as evidence of alignment.
Several mechanisms operationalize it. Fist of Five is a simultaneous show of hands, 0 to 5 fingers, of confidence in a proposed decision; because everyone reveals at once, it exposes doubt that a verbal "does everyone agree?" lets people hide behind a nodding majority, and low scores are treated as the start of the conversation rather than a vote to be overridden. Gibson Biddle's repeated live polling extends the same mechanic across time: poll the room early, add context and trade-offs, poll again, and let the audience watch its own answer move — which demonstrates that a hard call is a judgment made with a particular set of information rather than a fixed truth. Used at a Lean Product Meetup on a set of Netflix initiatives, it also surfaced a gap between a company's public investor narrative and informed outside opinion.
The deliberately bad idea opener attacks the same problem from the other end: open with an idea intentionally chosen to be a poor fit for the stated goals and invite critique. Because the idea is flawed on purpose and low-stakes to attack, participants get practice at voicing criticism — which makes it easier for them to later challenge an idea they'd otherwise feel unsafe criticizing, including a powerful stakeholder's. Tamar Yehoshua reports the seniority-side counterpart from her time at Amazon: rather than opening with his own view, Bezos would poll every lead in the room systematically and state his own opinion last. The polling step is what made speaking last effective — it surfaced un-anchored opinions from everyone, not just the most vocal or highest-status people present.
Two techniques check understanding rather than sentiment. Mirroring means repeating back what you think a stakeholder said, in your own words, and explicitly asking "did I get that right?" — especially valuable when they've said two things that seem to contradict each other, since restating both forces either a clarification or an admission of the tension. The definitional-alignment probe applies the same reflect-and-ask move to a single word. A team didn't realize they disagreed about a project until each stakeholder group was asked to define "archivist": to US stakeholders it meant a library, museum or brand-heritage role; to stakeholders in Asia, Japan and Europe it meant something closer to a records manager or systems administrator. Wiz's version was "what exactly are we building" — pushing past a plausible-sounding problem/solution pitch to granular detail, asked of both the internal team and of prospects, revealing that neither side actually shared a specific mental model of the product.
That archivist case points at a root cause the chapter takes seriously: cultural and departmental norms shape how disagreement gets expressed, and how a shared term is understood. Silence, hedged phrasing, or deference to hierarchy may read as agreement when they are a culturally-shaped indirect "no." Erin Meyer's The Culture Map is cited as a rougher-grained version at national level — Israelis and Dutch as very direct, Japanese as more indirect — with the explicit caveat that it's a generalization about a culture, not a guarantee about any individual in it.
And when a group setting suppresses disagreement structurally, the answer is to leave the group. Shuttle Diplomacy — named for the mediator who travels between parties that won't meet directly — means going one-on-one with skeptical or powerful stakeholders ahead of the decision meeting, so their real objections surface before the decision rather than during it, and so buy-in is pre-built. The chapter's most instructive failure is exactly here: a CTO gave full public agreement on four quarterly OKRs, a Fist of Five check with all 4s and 5s, and then privately crossed two of them off his own team's plan the next morning. The group check didn't lie about the room's mood; it just didn't reach a private disagreement that only one-on-one follow-up would have caught.
If nodding can't be trusted inside a meeting, several other everyday signals can't be trusted outside one either. Trust but verify applies the Cold War phrase to stakeholders: a stated "yes, I agree" is not a reliable predictor of behavior, and a verbal commitment is not the end of the diligence. The same source sets it in a three-stage autonomy spectrum — verify-then-trust, trust-but-verify, totally trust — where a person's position should track the trust they've actually earned rather than their role or tenure.
The concrete mechanism is cross-checking: when unsure whether a stated position is the real one, independently ask a colleague who works closely with them the same or a related question, compare the answers, and expand the circle if they diverge. The verification runs around the stakeholder through their own network rather than back at them — which avoids putting anyone on the spot while still surfacing the gap between stated and actual positions. It's the counterpart to mirroring, which checks understanding with the person directly.
Silence deserves its own warning. John Cutler names reading a lack of complaints as evidence that no problem exists as the biggest organizational antipattern. The reading is confounded: the people who would raise the loudest objections tend to leave dysfunctional organizations, and those who stay adapt their expectations downward to survive. What looks like consent is often the residue of attrition and adaptation — a lagging, survivorship-biased signal rather than a health metric.
Noise is equally unreliable in the opposite direction. Yehoshua's vocal-minority caution says the people who complain loudest about a product change are rarely representative of the larger, often silent, future user base the change is designed for — Slack's Calls-to-Huddles transition being the example, where complainers skewed toward the existing invested users rather than the much larger group who hadn't adopted yet. Put the two together and the lesson is that neither the presence nor the absence of vocal feedback can be read at face value; what matters is who the feedback sample actually represents.
A sharper version of the same instinct is the anecdote-over-data rule, attributed by Tom Verrilli (Whatnot CPO) to Jeff Bezos: "When you have data and an anecdote, trust the anecdote." The rule is not "ignore data." Aggregate data is usually an average or a rate, and a credible anecdote is often the leading edge of a real subgroup the average is hiding — so the rule functions as a tripwire to go segment the metric and find the blind spot, rather than as license to dismiss numbers.
Holding a decision against vocal opposition puts weight on how it gets communicated. The chapter's answer is respect rather than marketing speak: be transparent about the real reason for the change, don't dismiss the complaints, and give people time and a choice in how they migrate instead of forcing an abrupt cutover — "the bottom line was respect." Yehoshua pairs this with the Heath brothers' Switch framework, the elephant and the rider, where the rider is rationality and the elephant is emotion: leaders who lay out only the logical plan have directed the rider and left the harder-to-move emotional part of the organization entirely unaddressed.
Everything above is about detecting disagreement. This section is about what to do when it exists, is visible, and doesn't dissolve on contact.
The opening move is a listening script from McCarthy and Appel: acknowledge the disagreement, invite the full explanation, assume good faith and a shared underlying goal, then why-ladder back to the root of the divergence — and only then explain your own reasoning, if the call is yours. "I hear that you disagree, tell me all about it, I want to understand." The order is the technique: explaining first turns the conversation into a defense of a decision rather than an investigation of a disagreement, which leaves the other side unheard even when you were right.
Verrilli's version is more procedural and handles the asymmetric case, disagreeing with a senior person's unexpected call. First, curiosity before pushback: ask whether they have context you lack, before arguing the decision itself. If that doesn't resolve it, run three checks — is their mind already made up (if so, stop); if it's open, does either side have data (bring it if you do); and if neither side has data, defer to seniority without treating it as a loss. "If nobody's got data, it's just two opinions, the CEO's opinion is going to win... Check your ego at the door, get to the answer, but if you've got data, bring it." The protocol explicitly ranks data over seniority over ego.
Requests are a special case of disagreement, and the chapter offers a graded set of responses. "Yes, and" borrows the improv rule: rather than rejecting a stakeholder's proposed solution, accept the opening and ask them to elaborate on the problem underneath it, redirecting from solution back to problem without spending the relationship. A companion move from Hickman defuses requests with a bigger number — compare their pitch against a quantified alternative already in flight, a $1M idea against a $10M initiative in progress. As he puts it: "No stakeholder is like you must do my idea, they just don't know you're working on anything more valuable." When the answer really is no, say it together: walk the stakeholder jointly through cost of delay, opportunity cost, risk of delaying versus switching, and dependencies, so they arrive at the "not now" conclusion themselves rather than receiving a verdict.
When the argument is about approach rather than priority, the negotiated trial converts it into an empirical test both sides pre-agreed was fair: "we'll try it your way; if we don't hit X by a certain point, will you try it my way?" And when two stakeholders' objectives are structurally at odds — through no one's fault — peer-to-peer negotiation is simply the wrong tool. Escalating to whoever sits above both and asking them to prioritize is framed as a legitimate move, not a relationship failure; sometimes the honest answer is that a shared manager needs to choose between you.
A specific structural failure gets its own name: the Two Dads problem, where two senior leaders each give a team conflicting direction on the same workstream. The fix isn't better communication between the team and each leader — it's the leaders explicitly resolving accountability so only one direction reaches the team. Yehoshua names the PM/engineering variant "ask mom, ask dad": when ownership between a product and an engineering leader isn't explicitly divided, people learn to shop requests to whichever leader is likelier to say yes. Her operating model for that partnership, from Slack, is the positive counterpart — explicit ownership splits drawn ahead of conflict ("you drive this, I drive this"), mutual trust as the default, disagreement raised directly with the peer rather than back-channeled through teams, and shared rituals: joint OKR reviews, joint exec updates, and a weekly four-person sync with both chiefs of staff to surface organizational issues before they escalate.
Finance deserves a note because product leaders routinely misread it. Capex/opex treatment and project-based funding gates look immovable but are more negotiable than assumed once you grasp that finance thinks in assets and capital rather than features; much of the perceived rigidity comes from product people forcing requests into a binary "projects vs. products" framing instead of tailoring funding to a product's lifecycle stage. Marty Cagan's reframe for CFO audiences specifically: discovery should be understood as product development, not R&D — the R&D framing invites treatment as speculative overhead.
Finally, the chapter is unusually willing to say when to stop. Before writing someone off as difficult, diagnose the situation — is the friction specific to you, is the person under unrelated pressure like a reorg or a missed number, and are they genuinely obstructive or "mission-driven" in Tony Fadell's sense, pushing hard because they care about the outcome? For the mission-driven type the productive frame is "we're on the same team." There is nonetheless a legitimate stopping point, and it should be set against criteria decided in advance rather than in the moment. Annie Duke's Quit supplies the shape: define what you hope to get out of the relationship and a trial period — roughly six months — before you're inside the frustration, so the decision to disengage is objective rather than emotional. Marshall Goldsmith's rule, cited by Osterwalder, closes it: when a decision is genuinely outside your decision-making power, let it go — and if you find yourself repeatedly letting go of decisions that matter to you, treat that as a signal about the role's fit rather than about that one decision.
A surprising amount of this chapter is about logistics — which channel, which altitude, how many points, and how to reach someone whose calendar is full.
Channel comes first because trust forms at bandwidth. The bandwidth ladder ranks in person above 1:1 video, above group video calls, above async written communication, and says to use the highest rung available for a given stakeholder. The reasoning is that trust built at high bandwidth is what makes lower-bandwidth async communication viable later — building a new relationship purely over email skips the step where trust actually forms. As the source puts it, "people aren't quite 100% real to each other until they've actually met in person and shaken hands, then somehow they're not pixels anymore, they're a human."
Two guerrilla tactics exist to manufacture that top rung when a formal meeting isn't available. The un-meeting uses calendar knowledge — find out where a hard-to-schedule stakeholder will physically be, then engineer a "chance" hallway encounter for a quick question, a meeting that never appears on anyone's calendar. The coffee-machine ambush relies instead on the predictable gravity of a shared amenity: set up with a laptop near the machine closest to their office and wait. And for executives whose attention is the scarcest resource in the set, the short message is a door-opener rather than a payload — skip slang and long explanations, ask permission for a brief synchronous conversation ("I have one or two quick questions, have you got two minutes?"), and resolve it live.
The distributed-work material is thin — two tactics rather than a worked practice. Coaching in bursts proposes replacing weekly virtual one-on-ones with quarterly multi-day in-person visits to recreate the coaching density remote work costs, with the strong claim that concentrated in-person time can substitute for, not merely supplement, regular remote check-ins. It comes with a note about the politics of remote work generally: "You can't give a benefit like remote work and then take it away and expect people not to be really pissed at you."
Altitude is the next dial. Blagoja Golubovski's 10,000 ft / 3,000 ft / in the grids framework says the same strategic call needs three different tellings — a strategic view for the executive team and board, a mid-level view for peers, and ground-level detail for execution teams. This is about how you talk about decisions, not about who owns them; the decision-rights question belongs to The Product Operating Model.
Within an altitude, the targeting layer is Stukan's three-style taxonomy: numbers people who want data up front (a CFO), business-impact people who want the commercial "so what," and story/context people who need narrative before they'll engage with specifics. Format discipline follows. The numbers-first structure runs goals → where growth will come from → roadmap → current tracking vs. goals → data learnings → recommended actions last, on the logic that asking before establishing the numbers forces the audience to evaluate a request without the evidence that would make it land. The two-to-three point rule caps each slide — and each communication generally — at what people can actually retain, with a client's 76-page roadmap deck offered as the cautionary case: "It's always harder to make it shorter than to make it longer." And because guessing at an audience is worse than asking one, treat the presentation itself as discovery — ask stakeholders directly whether the content is relevant, read engagement even on video, and adjust the next one.
Finally, two artifact techniques exploit the fact that a recording travels further than a meeting. The short explainer video — anywhere from ten seconds to about two minutes of screen recording — replaces a meeting scheduled to correct an executive's misperception; in one case a confused new CEO's misunderstanding was resolved by a two-minute video that the CEO then forwarded company-wide, at which point other executives asked to promote it further. Pre-recorded demos were adopted after a live demo to a partner's CEO failed on an undisclosed API change on the partner's side; the original motive was risk reduction, but the side effect mattered more — a recording can be cut into a clip and shared far past the room it was made for.
Every technique above draws on a reserve that has to be built before it's needed. Stephen Covey's model, as Simonetta Batteiger presents it, gives that reserve two dimensions: character — integrity, intent, honesty, congruence, motives — and capabilities, the results actually produced. Neither alone is sufficient: good intentions without delivered results, and reliable execution without honest intent, both fail to establish trust. Batteiger maps it as a house, character and vision as foundation, capabilities and results as the structure on top, and extends it to agentic AI products — an agent, or the team that built it, gets evaluated on what it's built to value and whether it reliably delivers on that.
The deposit-making version is specific and unglamorous. Direct engagement means earning trust with legal, sales or analysts through sincere, recurring one-on-one contact rather than political maneuvering or formal process. The canonical illustration is the eBay relationship with Rob Chestnut: proactively flagging gray-area product ideas to legal before launch, repeatedly, builds a track record of judgment that eventually earns latitude — deposits made long before the withdrawal.
Trust can also be imported rather than built. Wiz's four co-founders share roughly 22 years of history — Israeli army service together, then a prior company, Adallom, built and sold to Microsoft. Herzberg credits that pre-existing history for the company's fast decision-making and its flat culture, where admitting "I don't understand" is normalized rather than treated as a status risk — the same culture that made her pivot-triggering admission possible.
Scope matters as much as depth. Most employees experience a company locally — through their manager, their team, their rituals — not company-wide, which means a leader can build a real boundary of trust around their own team even when the broader organization is dysfunctional or badly led elsewhere. The scope a leader actually controls is smaller than the scope they worry about, and that smaller scope is where intentional design pays off. Note the tension with survivorship silencing: a locally fine-feeling pocket is not evidence that the organization is fine.
Small rituals maintain the balance. For routine misses that don't require rebuilding trust, McCarthy and Appel describe an implicit retrospective framing — state neutrally what was done and what happened, propose a different approach next time, and leave the lesson unspoken: "But everybody just knows: hey, listen, we did it this way, this was the outcome, how about we try it this way next." And when a non-technical stakeholder needs convincing that proactive status communication is worth anything, the home-renovation contractor analogy does the work without process jargon: a bad contractor goes dark for weeks; a good one gives plain-language updates even when there's no material news, and that steady visibility, more than the work itself, is what preserves the client's trust.
The closing point is that none of this holds still. Alignment decays — not because people change their minds, but because they get pulled toward more urgent priorities, forget the original reasoning, and drift back toward default assumptions. Treating one successful round of alignment as a permanent state is the mistake; the fix is repetition on a recurring cadence, reminding stakeholders of the goals, why the work matters, and what's done versus what's coming. It's also why mining for conflict is a habit rather than a kickoff-meeting checkbox. The transformation narratives in Transformation in Practice show what that maintenance looks like at organizational scale, and the individual judgment all of this presumes is the subject of Product Leadership and Career Craft.
A caveat worth stating plainly about this chapter as a whole: it is a technique catalogue drawn almost entirely from practitioner report, with a heavy concentration in a single source, McCarthy and Appel's Align. The tactics are vivid and specific, but the material contains essentially no evidence about which of them work, for whom, or how often — the anecdotes illustrate the techniques rather than test them.