62:50
stakeholder management
Bruce McCarthy and Melissa Appel, authors of "Align" (O'Reilly), argue that stakeholder management is the underrated "secret lubricant" behind product success: treating stakeholders as real people, mapping the organization's real (informal) power structure instead of the org chart, and actively building alignment — not mere consensus — matters more than simply being right.
Stakeholder management is called "the secret lubricant behind success" — once the hard/technical things are in place, the soft relational things determine outcomes.
A roadmap is a reflection of goals and objectives, not a list of features and dates; disagreement over roadmap contents usually signals unresolved disagreement over goals.
Apparent group agreement is often shallow (illustrated with a cartoon of people nodding while their private thought-bubbles show different shapes) and must be actively tested, e.g. via "mining for conflict" and "Fist of Five."
"Saying no" to a stakeholder should become "saying no together": walk through cost of delay, opportunity cost, risk, and dependencies jointly so the stakeholder often reaches the "no" conclusion themselves.
The official org chart has little to do with how decisions and power actually flow; behind it is what the speakers call "the Matrix," and mapping real "Power Players" and "CEO Whisperers" matters more than reporting lines.
Every company has a dominant function (sales-, marketing-, engineering-, or PE/finance-driven), and identifying it determines who truly belongs on a stakeholder list.
Difficult stakeholders should be diagnosed before being judged: check whether it's just you, check external context, and identify whether the person is simply difficult or "mission-driven."
Vulnerability ("I don't know, you tell me") builds more credibility than false expertise and functions as an informal customer interview.
Distributed/remote stakeholder relationships need the highest-bandwidth communication available (in person > 1:1 video > group call > async email) to build trust, after which async communication becomes viable.
Cultural and departmental context shapes how disagreement, hierarchy, and even ordinary terms are communicated; assuming shared definitions or communication norms causes hidden misalignment.
Alignment decays over time as people get distracted by other priorities, so goals must be repeated and reinforced, not just agreed once.
Alignment matters more than being right: an unaligned organization will not execute a correct idea, and full consensus in a large group is essentially impossible, so the real goal is "disagree and commit," not universal agreement.
There is a legitimate point at which to stop pursuing alignment with a difficult stakeholder or role and move on, ideally guided by criteria set in advance.
Five Levels of Why — A classic PM technique of repeatedly asking "why" with genuine curiosity rather than a judgmental tone, later reused in reverse to restate an implied conclusion and test whether a group's stated goals genuinely support it. Apply: Ask "why" several times in succession with a curious tone, or say "so that would imply we should do this and not that" to see whether the person still agrees or reveals a more complicated truth.
Stakeholder Interview — A conversation modeled on a customer interview where you let the stakeholder go first, asking about their job, success/failure criteria, how their boss measures them, and what's keeping them up at night. Apply: Before presenting a plan or roadmap, interview the stakeholder with questions like "tell me about your job" and "what challenges are keeping you up at night" to find common ground between their goals and yours.
Mining for Conflict — A technique borrowed from Patrick Lencioni's "Five Dysfunctions of a Team" for deliberately surfacing disagreement that people are reluctant to voice in a group. Apply: Actively probe the edges of a discussion or follow up one-on-one with quiet attendees to surface hidden disagreement before assuming the room has truly aligned.
Deliberately Bad Idea Opener — Opening a discussion with an idea known to be a poor fit for the goals, inviting the group to critique it. Apply: Present a purposely flawed option first so participants practice critique on a safe target, making it easier to later critique ideas they'd otherwise feel unsafe challenging.
Fist of Five — A simultaneous show-of-hands confidence check (0 = fist, 5 = fully confident) used to gauge a group's real agreement with a decision. Apply: Have everyone hold up 0–5 fingers at once to reveal hidden doubts a verbal "yes" would conceal, then address what the low scorers are worried about.
Shuttle Diplomacy — Going one-on-one with individuals who won't voice disagreement in a group, or privately gathering advice and buy-in before a big meeting where a decision must be finalized. Apply: Talk to skeptical or powerful stakeholders privately, ahead of or alongside group sessions, to surface real objections and pre-build support before the decision-making meeting.
Co-creation / IKEA Effect — The named phenomenon where people rate something they helped build as better, making a roadmap harder to critique once stakeholders helped create it. Apply: Involve stakeholders in building the roadmap itself, not just presenting it, so they're less likely to reject it later and more likely to defend it.
Say No Together / Cost-of-Delay Analysis — A framework for jointly walking through cost of delay, opportunity cost, risk of delaying vs. switching, and dependencies with a stakeholder pushing an urgent request, instead of unilaterally declining it. Apply: When a stakeholder pushes to jump the roadmap queue, work through these four factors together so they reach the "not now" conclusion themselves.
Ignore the Org Chart / Find "the Matrix" — The principle that the official org chart has little to do with how decisions and power actually flow, and that a hidden network ("the Matrix") is the real driver, populated by "Power Players" who can kill or fund an initiative regardless of title. Apply: Discard the formal reporting-line chart when deciding who to influence and instead map who actually swings decisions, regardless of whether they're in your reporting hierarchy.
CEO Whisperers — A named category of people without formal authority (no big title, no direct reports) who hold informal influence over a CEO or executive, evidenced by things like daily coffee chats or uninvited meeting attendance. Apply: Watch for behavioral clues — who has informal facetime with leadership, who shows up uninvited and asks pointed questions — to identify and cultivate relationships with these informally powerful people.
Dominant-Function Diagnosis — A diagnostic question — is this a sales-, marketing-, engineering-, or PE/finance-driven company — for identifying which function actually holds organizational power. Apply: Look for concrete evidence (who gets cross-departmental awards, who can still hire during a freeze, who has the CEO's ear) to identify the dominant function, then ensure people from it are on your stakeholder list.
Stakeholder Canvas — A tool from the "Align" book, downloadable free at alignthebook.com, that replaces the org chart by mapping the most important power players and the role they play in decisions. Apply: Fill out the canvas to list and classify your real power players, optionally layering a DISC personality category onto each entry, instead of relying on the formal reporting structure.
Tony Fadell's Difficult-People Typology — A typology from Tony Fadell's book "Build" distinguishing types of difficult people, including "mission-driven" people who believe harsh behavior drives results. Apply: Diagnose which type of difficult person you're dealing with before reacting; for mission-driven types, work toward a "we're on the same team" framing rather than assuming personal animosity.
Vulnerability / "Tell Me What It Does, I Don't Know" — A technique, illustrated by the speaker's father selling Polaroid cameras, of openly admitting you don't know something and asking others to explain it to you, which doubles as an informal customer interview. Apply: When you lack expertise, say so directly and ask the knowledgeable person to explain it — people typically respond with help rather than ridicule, and admitting what you don't know builds credibility.
Tying Initiatives to Stakeholder Priorities — A buy-in technique of explicitly connecting your project to an existing company-wide initiative executives already care about, as in the warehouse-direction project tied to a damage-reduction initiative. Apply: Identify a goal executives are already championing and frame your project's benefit in those terms to win their support.
Asking for Advice as Buy-in — A technique of asking a power player for advice on a plan before it's finalized, rather than presenting a completed plan for approval. Apply: Approach a stakeholder early with "I have a couple of questions you could help with" so they contribute advice, become invested as an early supporter, and later share credit for the project's success.
Trust But Verify — A Cold War-derived phrase applied to validating whether a stakeholder's stated position actually reflects their true plans. Apply: Don't take a stated agreement at face value; independently check it against other information sources or people before relying on it.
Cross-Checking with Multiple Stakeholders — A verification technique of asking a related colleague the same or a related question to see whether their answer matches what the first stakeholder said. Apply: When unsure of a stakeholder's real position, independently ask someone who works closely with them the same question and compare answers, expanding to more people as needed.
Mirroring — A technique of repeating back what you believe you heard, in your own words, and explicitly asking whether you got it right. Apply: Restate a stakeholder's position in your own words and ask for confirmation, especially when they've said two seemingly contradictory things, to surface real understanding instead of surface-level agreement.
Alignment Decay — A named concept describing how stakeholder agreement, once reached, naturally erodes over time as people get distracted by other priorities. Apply: Counter it by repeatedly reminding stakeholders of the goals, why the work matters, and what's done and coming next, rather than treating one round of alignment as permanent.
Bandwidth/Intimacy Ladder for Distributed Communication — A ranking of communication channels by bandwidth (ability to convey tone and body language) and intimacy — in person, then 1:1 video, then group calls, then async email — for building trust with distributed stakeholders. Apply: Use the highest-bandwidth channel available for key stakeholders, ideally meeting in person at least occasionally, to build rapport before relying on lower-bandwidth async communication.
Un-Meeting — A guerrilla in-person tactic of checking a stakeholder's calendar to know where they'll physically be, then engineering a "chance" hallway encounter to ask a quick question. Apply: Use calendar knowledge to intercept a hard-to-schedule stakeholder in passing rather than waiting for a formal meeting slot.
Coffee-Machine Ambush — A guerrilla tactic of setting up with a laptop near the coffee machine closest to a target stakeholder's office and waiting for them to appear. Apply: Position yourself where a busy stakeholder is likely to pass by during the day to catch them for a brief informal conversation.
Short-Message Technique for Busy Executives — A messaging approach for reaching senior executives on Slack/WhatsApp: skip casual slang and long text, and instead ask permission for a short synchronous conversation. Apply: Send a brief message like "I have one or two quick questions, have you got two minutes?" and resolve it live on a short video call rather than in a long written message.
Short Explainer/Screen-Recording Videos — Using a short recorded video or screen recording (examples ranged from roughly 5–10 seconds to about 2 minutes) to correct an executive's misperception or clarify a product point instead of scheduling a meeting. Apply: When an executive is confused about a feature or data point, record a short video showing the real picture and send it directly; it can also get forwarded and drive broader alignment.
Definitional-Alignment Probe — A technique for catching hidden misalignment where stakeholders assume they agree on a term's definition (e.g., "archivist") when they actually don't. Apply: Ask each stakeholder to explicitly define a term everyone assumes is obvious, then reflect the differences back to them ("yours seems quite specific, yours seems much broader — is that right?") to surface real disagreement.
The Culture Map (Erin Meyer) — A referenced book describing average national/cultural differences in directness of communication, respect for hierarchy, and decision-making style (e.g., Israelis and Dutch cited as very direct, Japanese as more indirect). Apply: Use its dimensions as a rough lens for interpreting a stakeholder's cross-cultural communication style, while treating them as generalizations rather than certainties for any individual.
DISC Personality Framework — An existing personality framework the authors adopted, after finding their own invented model was roughly 90% identical to it, to describe individual behavioral differences; described as related to but distinct from Myers-Briggs. Apply: Layer a DISC category onto each entry in your stakeholder canvas to inform how you tailor communication to that person's style.
Rule of 40 — A finance metric referenced as a marker of PE-owned, finance-driven companies. Apply: If a company is PE-owned and focused on metrics like the rule of 40, expect finance to be the dominant function and prioritize finance stakeholders accordingly.
"Inception" Buy-in Technique — A named technique for securing alignment by leading stakeholders to believe your idea is their own idea. Apply: Use tactics like asking for advice or co-creation so the stakeholder feels ownership of the idea, increasing their support even though it originated with you.
Being Wrong (Kathryn Schulz) — A concept from Kathryn Schulz's book "Being Wrong," cited to explain that at the moment you're actually wrong, it still feels like being right — realization only comes afterward. Apply: Stay open to being shown wrong after the fact rather than assuming present confidence proves correctness, so you can update and realign when new evidence appears.
Quitting Criteria (Annie Duke, "Quit") — A framework from Annie Duke's book "Quit" for setting in advance what you hope to accomplish in a role or relationship and a threshold at which you'll disengage if it's not met. Apply: Define concrete criteria up front (e.g., learning, working with great people, mission accomplishment) and a trial period of about six months, so you know objectively when to move on from a blocked stakeholder relationship.
Escalation to Shared Authority — Bringing two stakeholders with genuinely conflicting objectives to a common manager or higher authority to get a priority call, rather than resolving it peer-to-peer. Apply: When two parties' goals are legitimately in conflict through no one's fault, escalate to whoever has a broader view of priorities to make the call.
Negotiated Trial with Predefined Success Criteria — A negotiation technique of agreeing in advance to try a disputed approach one way, with predefined success criteria, and switching approaches if those criteria aren't met. Apply: Propose "we'll try it your way; if we don't hit X by a point, will you try it my way?" to resolve a disagreement empirically rather than by argument.
Disagree and Commit — A distinction between consensus (everyone actually agrees) and alignment (people are willing to proceed even while disagreeing), premised on the idea that perfect consensus in a large group is essentially impossible. Apply: Aim for people's willingness to commit to a decided direction despite lingering disagreement, rather than insisting on full consensus before moving forward.
Empathy-Based Disagreement Script — A scripted response for handling disagreement: acknowledge it, invite the person to explain fully, assume good faith and shared goals, trace back through repeated "whys," then explain your own final reasoning. Apply: Say something like "I hear that you disagree, tell me all about it, I want to understand," genuinely listen and probe with why questions, then explain your reasoning if the final call is yours.
Pre-Recorded Demos as Shareable Artifacts — A practice, adopted after a live demo failed due to an undisclosed partner API change, of always pre-recording product demos in advance. Apply: Record demos ahead of time to de-risk technical failure, and edit them into short, shareable clips that spread alignment across the company beyond the original audience.
Implicit Non-Confrontational Retrospective Framing — A team norm for giving feedback after something didn't work: state what was done and its outcome, then propose a different approach next time, without direct criticism. Apply: Frame post-mortems as "we did it this way, this was the outcome, how about we try it this way next" instead of assigning blame, letting the team draw the lesson implicitly.
Bruce assumed his e-commerce employer was engineering-led because he sat among hundreds of engineers, but the real power center was sales — revealed only through indirect clues (only sales gave cross-departmental awards, only sales could hire during a freeze, and the CEO's daily coffee partner was the head of sales operations).
A CTO who showed full public agreement (Fist of Five, all 4s and 5s) on four quarterly OKRs privately crossed off two of them the next morning with his own team — proving that group-level confidence checks can still mask real private disagreement, which is why one-on-one "shuttle diplomacy" is needed to surface the truth.
The word "archivist" meant a library/museum or brand-heritage role to US stakeholders but something closer to "records manager" or "system administrator" to stakeholders in Asia, Japan, and Europe — the team didn't even realize they disagreed until each side was asked to explicitly define the term.
A confused new CEO's misunderstanding was resolved not with a meeting but with a roughly 2-minute recorded video, which the CEO then forwarded company-wide, turning a one-off clarification into a scaling alignment tool other executives asked to promote further.
A live product demo to a major partner's CEO failed not because of the team's own code but an undisclosed API change on the integration partner's side — the embarrassment permanently changed practice to always pre-recording demos, which had the side benefit of producing shareable artifacts that spread alignment across the company far beyond the original audience.
The speaker's own idea with genuine product-market fit later became, in essence, the $2 billion company Vista Print when someone else executed it with organizational alignment behind them — being right without alignment behind you produces nothing.
The authors initially tried to invent their own personality-difference framework for the book, then discovered it was about 90% identical to the existing DISC framework and simply adopted DISC instead of building something new.
«this is the most important topic that nobody ever talks about this is the secret lubricant behind success once you have the hard things in place there are the soft things that you need to worry about.»
— 02:52
«a road map is not a list of things to do it's not a list of deliverables it's not a bunch of features with dates it's a reflection of your objectives it's a reflection of your goals.»
— 07:14
«the idea is to say no together you don't just say no to stakeholders and give them a reason you have them in the process the whole time.»
— 12:08
«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.»
— 14:51
«behind the org chart is the Matrix and the Matrix is what really drives things.»
— 15:18
«people like to be listen to and if you listen to them, they think you're smarter»
— 29:35
«you tell me what it does, I don't know»
— 30:41
«admit what you don't know, that's the biggest credibility booster you can possibly have»
— 31:29
«trust but verify»
— 36:31
«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»
— 40:12
«I have one or two quick questions, have you got two minutes?»
— 43:40
«alignment is the most important thing because even if you're right they have the power you will not get what you want.»
— 53:31
«I invented Vista Print before Vista Print»
— 54:44
«You don't know what you don't know.»
— 55:21
«I hear that you disagree, tell me all about it, I want to understand.»
— 59:14
«but everybody just knows Hey listen we did it this way this was the outcome how about we try it this way next»
— 62:25
Reception
The single comment is highly positive, praising the talk as relatable and recommendation-worthy.
The video is a dense, technique-heavy practitioner talk that functions as a live extension of the authors' book "Align," packing in dozens of named, reusable tactics (Fist of Five, shuttle diplomacy, stakeholder canvas, disagree-and-commit, etc.) rather than a single novel argument, making it most valuable as a reference list of concrete moves rather than a theoretical treatise.
62:50