The sequence is the model. Listen. Decide. Communicate. Three verbs, fixed order, no substitutions. Most leaders get the ingredients right and the recipe wrong — they decide before they listen, or they listen endlessly and never decide, or they decide brilliantly and communicate so poorly that the organisation executes a different decision entirely. The framework's power is in the sequence, and violating the sequence produces predictable failures that look like leadership deficits but are actually process errors.
Listen means gathering signal, not noise. It means asking questions before forming opinions. It means sitting in a room with the people closest to the problem and resisting the executive reflex to diagnose before the examination is complete. Satya Nadella spent his first months as Microsoft CEO in 2014 doing almost nothing that looked like leading. He visited teams. He asked what wasn't working. He sat in meetings where engineers described the internal competition between Windows, Office, and Azure that was cannibalising the company's ability to ship coherent products. He didn't arrive with a strategy. He arrived with questions. The strategy emerged from what he heard — a cultural transformation built on the phrase "growth mindset" that was not Nadella's invention but his synthesis of what hundreds of Microsoft employees told him was broken. The listening wasn't passive. It was the most consequential strategic act of his tenure.
Decide means committing with incomplete information. Not reckless commitment — calibrated commitment. The kind of commitment that accepts 70% certainty because waiting for 90% means the window closes. Jeff Bezos codified this as "disagree and commit": once you've listened, once the perspectives are in, someone decides and everyone executes. Indecision is not caution. Indecision is a decision to let circumstances choose for you, and circumstances are a terrible strategist. The leader who postpones a call because they want more data is often not seeking information — they're seeking the emotional comfort of certainty that complex decisions cannot provide. The Listen phase is where you gather. The Decide phase is where you stop gathering and act.
Communicate means explaining the decision clearly, repeatedly, and through every channel that reaches the people who must execute it. A decision that lives in the CEO's head is not a decision — it is a private opinion with no operational consequence. Reed Hastings at Netflix learned this the hard way in 2011 when he decided to split the company's DVD and streaming businesses into separate brands — Netflix for streaming, Qwikster for DVDs. The decision had logic behind it. The communication was catastrophic. Hastings announced the split in a blog post that confused customers, alienated investors, and prompted 800,000 subscriber cancellations in a single quarter. The decision wasn't wrong in principle — Netflix did eventually exit the DVD business. The communication was so poor that a defensible strategic move became a case study in how to destroy $12 billion in market value through bad messaging. Within weeks, Hastings reversed course on Qwikster. The listening had been insufficient (customers didn't want two accounts), and the communication had been worse. The sequence broke at both ends.
The three phases are not equal in time allocation. Listening should consume the most time — 60% or more of the cycle. Deciding should be fast, often a single meeting or a single day once the listening is complete. Communicating should be ongoing, repetitive, and multi-format. The asymmetry is counterintuitive. Leaders believe their value is in deciding. Their actual value is in listening well enough that the decision becomes obvious, and then communicating that decision so clearly that 10,000 people execute it as if they'd made the call themselves.
Section 2
How to See It
Listen Decide Communicate is operating wherever a leader's effectiveness depends less on the quality of their thinking and more on the quality of the process by which they gather input, commit to a direction, and align the organisation behind it. The diagnostic: trace back from the execution. If the team executed the wrong thing, the failure was probably in Communicate. If the team executed the right thing too late, the failure was probably in Decide. If the decision itself was wrong, the failure was almost certainly in Listen.
Corporate Leadership
You're seeing Listen Decide Communicate when a new CEO takes over a struggling company and spends the first 90 days in listening mode — visiting offices, attending team standups, asking frontline employees what's broken — before announcing any strategic changes. Satya Nadella at Microsoft, Alan Mulally at Ford, and Jørgen Vig Knudstorp at Lego all ran the same playbook. The instinct to arrive with a plan and announce it on day one is strong. The leaders who resist that instinct and listen first consistently outperform the ones who don't, because the information that determines the right strategy lives in the organisation, not in the new leader's head.
Product & Engineering
You're seeing Listen Decide Communicate when a product leader holds a decision meeting and starts by asking every person in the room for their perspective before stating their own view. The order matters. A leader who opens with their opinion converts the meeting from a listening exercise into a confirmation exercise — the team provides evidence for the conclusion the leader already telegraphed. Amazon's silent memo-reading ritual is a Listen mechanism: thirty minutes of silent reading ensures every participant has absorbed the same information before anyone speaks. The listening is structural, not optional.
Startups
You're seeing Listen Decide Communicate when a founder makes a difficult pivot decision and then over-communicates the rationale to every stakeholder — investors, employees, customers, and partners — through multiple formats over multiple weeks. Stewart Butterfield's email to Slack employees explaining the pivot from gaming to enterprise messaging is a masterclass in the Communicate phase. He didn't announce the pivot. He explained the listening that led to it, the decision logic behind it, and what it meant for every person in the room. The communication made the decision executable because the team understood not just what was changing but why.
Military & Operations
You're seeing Listen Decide Communicate when a commander gathers intelligence from multiple sources, issues a clear order, and then confirms that every unit has understood the order through back-briefing. The military's obsession with "commander's intent" is the Communicate phase formalised: the order includes not just the action but the purpose behind it, so that when conditions change on the ground, subordinates can adapt their actions while preserving the intent. The decision survives contact with reality because the communication included the reasoning, not just the instruction.
Section 3
How to Use It
Decision filter
"Before acting on any significant decision, audit the sequence: Did I listen to the people closest to the problem? Did I resist the urge to form my opinion before hearing theirs? Have I decided — actually committed, not deferred — based on what I heard? And have I communicated the decision with enough clarity and repetition that the last person in the chain can explain it back to me?"
As a founder
The Listen phase is where first-time founders fail most often. The founder's identity is built on having the answer — the vision, the product insight, the market thesis. Listening feels like weakness. It isn't. The best founders listen with the intensity of someone whose survival depends on the accuracy of the signal — because it does. Brian Chesky at Airbnb spent weeks living with hosts, interviewing guests, and mapping every friction point in the booking experience before making product decisions. The listening produced insights that no amount of internal brainstorming could have generated: that professional photography doubled booking rates, that the host-guest relationship was more important than the property itself, that trust was the binding constraint on growth.
For the Decide phase: set a decision deadline before the listening begins. "We will decide on the pricing model by Friday" is a structural commitment that prevents the listening from becoming procrastination. The deadline forces the team to synthesise what they've heard rather than gathering indefinitely. Without a deadline, the Listen phase expands to fill all available time, and the decision never gets made because there's always one more data point to collect.
As an investor
Listen Decide Communicate is the diagnostic for evaluating a CEO's operating system. In board meetings, watch the sequence. Does the CEO present a recommendation and then ask for input? That's Decide-Communicate-Listen — inverted. Does the CEO open with a question, synthesise the board's input, and then propose a direction? That's the correct sequence. The distinction predicts the quality of the CEO's decisions over time, because a CEO who listens before deciding has access to more information than one who decides before listening.
The Communicate phase is where board-CEO relationships fracture. A CEO who makes a strategic decision but communicates it poorly to the board — burying the rationale in a dense slide deck, announcing the change without context, or failing to connect the decision to the board's prior input — creates the impression of unilateral action even when the decision was sound. Invest in CEOs who can articulate not just what they decided but who they listened to and why the input led to this specific conclusion.
As a decision-maker
The highest-leverage application in large organisations is in the Communicate phase, because large organisations are where communication fails most spectacularly. A decision made by the executive team on Monday is a rumour by Wednesday, a misinterpretation by Friday, and a grievance by the following Monday. The fix is repetition across formats. Announce the decision in an all-hands. Explain the reasoning in a written memo. Have each director communicate it to their teams with context specific to their function. Follow up in the next all-hands with a progress report that reinforces both the decision and its rationale.
Jeff Bezos's rule: if you've communicated something once, you haven't communicated it. Seven repetitions across different contexts is the threshold at which a message begins to stick. Most leaders communicate a major decision once and assume it's done. It isn't. The organisation is large, attention is fragmented, and every person filters the message through their own concerns. The Communicate phase is not an announcement. It is a campaign.
Common misapplication: Treating Listen as consensus-building. Listening doesn't mean agreeing with what you hear. It means absorbing the information so your decision is informed by reality rather than assumption. A leader who listens to fifteen people and then decides against all fifteen hasn't failed at listening — they've completed the sequence. The Listen phase is about input, not about votes.
Second misapplication: Skipping Communicate because the decision "speaks for itself." No decision speaks for itself. Every decision requires translation — from the context the decision-maker holds to the context the executor holds. The gap between those two contexts is where misexecution lives. Communicate bridges that gap. Skip it and the organisation executes a distorted version of what you intended.
Section 4
The Mechanism
Section 5
Founders & Leaders in Action
The leaders below didn't stumble into the Listen Decide Communicate sequence. They engineered it into their operating rhythms — building listening systems, creating decision protocols, and investing disproportionately in communication infrastructure that most CEOs neglect.
Nadella inherited a company at war with itself. Microsoft in 2014 was a $300 billion company running on Windows hegemony, with a culture that Steve Ballmer's former chief of staff described as "every team competing against every other team." The Windows division vetoed products that threatened Windows revenue. The Office team resisted cloud migration. Azure was a side project. Nadella's first act wasn't a strategic announcement. It was a listening tour that lasted months. He visited engineering teams in Redmond, Hyderabad, and Beijing. He asked a single question in dozens of variations: what would you do differently if you could? The answers converged on a single theme — the company's internal competition was killing its ability to serve customers. Nadella synthesised what he heard into three words: "mobile-first, cloud-first." The decision was to de-centre Windows as Microsoft's identity and reorganise around cloud and services. He killed the internal stack-ranking system that had incentivised competition over collaboration. He released Office for iOS and Android — a move that would have been heretical under Ballmer. Then he communicated relentlessly. His 2014 memo to all employees ran over 3,000 words and was followed by town halls, one-on-ones with every senior leader, and a book (Hit Refresh, 2017) that explained not just what had changed but why. Microsoft's market capitalisation went from $300 billion to over $3 trillion. The sequence — listen to the organisation, decide on the transformation, communicate until the last engineer understands the why — was the mechanism.
Bezos operationalised each phase of the sequence into distinct organisational rituals. The Listen phase is the six-page narrative memo: before any meeting, the team writes a detailed document that the decision-makers read in silence for thirty minutes. The silence is the listening. No one speaks until everyone has absorbed the same information. The format eliminates the distortion that verbal presentations introduce — charismatic presenters don't get an advantage over clear thinkers, and the quietest person in the room has equal access to the decision-maker's attention. The Decide phase is "disagree and commit." Bezos described it in his 2016 shareholder letter: "If you have conviction on a particular direction even though there's no consensus, it's helpful to say, 'Look, I know we disagree on this, but will you gamble with me on it?'" The decision is made. Debate ends. Execution begins. The Communicate phase at Amazon is the PR/FAQ — a press release and FAQ document written before a product is built, explaining the decision in customer-facing language. The PR/FAQ forces the team to communicate the decision's value in plain language before writing a line of code. If the press release doesn't make sense, the decision doesn't make sense. Each phase has a structural ritual. None are optional. The sequence isn't a suggestion at Amazon. It's infrastructure.
Section 6
Visual Explanation
The three-phase flow at top shows the fixed sequence with its time asymmetry — Listen gets the most time, Decide gets the least. The violation patterns below expose the three most common failures: deciding before listening (ego-driven leadership), listening without deciding (fear-driven leadership), and deciding without communicating (disconnected leadership). The time allocation bars at bottom quantify the counterintuitive truth: leaders should spend six times longer listening than deciding.
Section 7
Connected Models
Listen Decide Communicate is a leadership operating system. The connected models below are the subsystems that make each phase more effective — sharpening the listening, improving the decision, and amplifying the communication.
Reinforces
[OODA Loop](/mental-models/ooda-loop)
Boyd's Observe-Orient-Decide-Act loop is the military ancestor of Listen Decide Communicate. Observe and Orient map to the Listen phase — gathering information and synthesising it into a coherent picture. Decide maps directly. Act encompasses both the decision's execution and the communication required to coordinate that execution. The OODA loop adds a critical dimension: speed. Boyd's insight was that the competitor who cycles through the loop faster forces the opponent into reacting to obsolete conditions. The same dynamic operates in business — the leader who listens, decides, and communicates faster captures the initiative while competitors are still in their listening phase.
Reinforces
Commander's Intent
Commander's Intent is the Communicate phase engineered for resilience. Instead of communicating the specific actions the team should take, the leader communicates the purpose behind the decision — so that when conditions change on the ground, the team can adapt their actions while preserving the intent. A CEO who says "we're cutting costs by 15%" has communicated an action. A CEO who says "we need eighteen months of runway to reach profitability, so we're cutting costs by 15% starting with non-customer-facing expenses" has communicated intent. The second version survives contact with reality because it tells the organisation not just what to do but why — enabling intelligent adaptation when the specific instructions become impractical.
Reinforces
Radical Candor
Kim Scott's framework makes the Listen phase productive rather than performative. Radical Candor — caring personally while challenging directly — creates the psychological conditions under which people tell leaders the truth rather than what leaders want to hear. The Listen phase collapses without candour, because the information gathered is filtered through the subordinate's calculation of what the leader wants to hear. Organisations where radical candour operates produce higher-quality listening, which produces better-informed decisions, which produces decisions that require less communication effort because the team already understands the reasoning.
Section 8
One Key Quote
"I think the most important thing a leader can do is to listen — to listen to what people are trying to tell you, to listen to what they're not telling you, and to use that to inform the decisions you make."
— Satya Nadella, Hit Refresh (2017)
Nadella published this after three years of running the Listen Decide Communicate sequence at a scale that few leaders in history have attempted. Microsoft had 120,000 employees when he took over. The listening tour wasn't a PR exercise — it was the data-gathering mechanism for the most consequential set of decisions in Microsoft's post-Gates era. De-centring Windows. Embracing open source. Releasing Office on competitors' platforms. Acquiring LinkedIn for $26 billion and GitHub for $7.5 billion. Each decision emerged from what Nadella heard, not from what he assumed.
The phrase "what they're not telling you" is the sophisticated addendum. Listening isn't just absorbing explicit statements. It's reading the silences — the products no one mentions, the initiatives no one defends, the questions no one asks. At Microsoft, the silence around Windows Phone told Nadella more than any strategy presentation could: the organisation had already given up on mobile, but no one would say it because Ballmer had invested the company's identity in the platform. Nadella listened to the silence, decided to exit mobile, and communicated the rationale without blame. The sequence, executed completely, transformed a $300 billion company into a $3 trillion one.
Section 9
Analyst's Take
Faster Than Normal — Editorial View
Listen Decide Communicate is the simplest leadership framework that actually works, and the one most consistently violated by the leaders who need it most. The violation is always the same: skip Listen, rush to Decide, under-invest in Communicate. The result is decisions that are technically sound but organisationally inert — brilliant strategies that no one executes because no one understands them, or worse, decisions based on assumptions that three conversations with frontline employees would have corrected.
The Listen phase is where the real work happens, and it's the phase that ego resists most violently. A CEO who has been promoted through twenty years of having the right answers does not naturally sit in a room and ask questions. The promotion process selected for decisiveness, not for curiosity. The best leaders I've studied — Nadella, Mulally, Jørgen Vig Knudstorp at Lego — all share a specific trait: they are genuinely interested in being wrong. Not performatively humble. Actually curious about what they don't know. That curiosity makes their Listen phase productive, which makes their Decide phase accurate, which makes their Communicate phase credible because the organisation saw them listen.
The Decide phase is where good leaders separate from popular ones. Listening to everyone and deciding in favour of the consensus is not leadership. It's polling. The framework demands that the leader absorb the input and then make a judgment that may contradict it. Bezos's "disagree and commit" is the mechanism, but the principle is older: the leader's job is to hold the information that no individual contributor holds — the full picture across functions, markets, and time horizons — and to make the call that the full picture demands. Sometimes that call disappoints the people who were heard. The Listen phase earned their trust. The Decide phase spends it. The Communicate phase replenishes it by explaining the reasoning.
The Communicate phase is the one that scales worst and matters most. At ten employees, communication is ambient — everyone hears everything. At a thousand, communication is architecture — it requires systems, repetition, and deliberate multi-channel reinforcement. The leaders who fail at scale are almost always failing at Communicate, not at Listen or Decide. They made the right call based on good information, and then they sent one email and assumed the organisation understood. It didn't. The email was filtered through layers of interpretation, each layer adding distortion. By the time the message reached the frontline, it was unrecognisable. The fix is unglamorous: say it seven times, in seven formats, and then say it again.
Section 10
Test Yourself
The scenarios below test whether you can diagnose which phase of the sequence failed — and whether you can distinguish authentic execution of the framework from its common counterfeits.
Where did the sequence break?
Scenario 1
A new VP of Engineering joins a 400-person company. In her first week, she announces a reorganisation: all teams will shift from feature-based squads to platform-based teams. She presents data from her previous company showing that platform teams ship 30% faster. Three months later, velocity has dropped 20%, senior engineers are leaving, and the CEO asks what went wrong.
Scenario 2
A CEO spends three months talking to customers, employees, and board members about whether to enter the European market. She gathers extensive data. She hosts four strategy sessions. She commissions a market study. At the end of the three months, she tells her leadership team: 'I want to keep exploring this — let's reconvene next quarter.' The CFO privately tells a board member: 'She does this every time. We've been evaluating Europe for two years.'
Scenario 3
A startup CEO listens to customer feedback for two months, decides to pivot from B2C to B2B, and sends a Slack message to the company: 'We're going B2B. More details to follow.' Two weeks later, the sales team is still pitching B2C prospects, the marketing team has updated the website but not the sales collateral, and three engineers are building features for the B2C roadmap. The CEO is frustrated: 'I told everyone we're pivoting.'
Section 11
Top Resources
The literature on leadership communication, decision-making under uncertainty, and organisational alignment converges on the Listen Decide Communicate sequence — though it often uses different vocabulary. Start with Nadella for the Listen phase in action, Bezos for the Decide phase operationalised, and Grenny for the mechanics of communication that actually changes behaviour.
The most complete case study of the Listen phase executed at enterprise scale. Nadella describes his listening tour, the cultural signals he absorbed, and how the information gathered in those first months shaped every strategic decision of his tenure. The book is also an unusually candid account of how a leader communicates transformation to an organisation of 120,000 people — the repetition, the multi-format approach, and the patience required.
The foundational document for the Decide phase. Bezos's articulation of "disagree and commit" and the 70% information rule provides the operational mechanics for converting listening into committed action. The letter also describes the structural rituals — silent memo reading, the PR/FAQ — that make the Listen and Communicate phases systematic rather than ad hoc.
The definitive guide to the Communicate phase when the message is difficult, the stakes are high, and the audience is resistant. The book provides frameworks for maintaining dialogue under pressure — the precise conditions that exist when a leader must communicate a decision that not everyone agrees with. Essential for leaders who listen well and decide well but lose the organisation in the Communicate phase because they cannot hold space for disagreement while maintaining commitment.
Drucker's argument that effective executives are distinguished by the discipline of their decision process — not by the brilliance of their conclusions — is the intellectual foundation for Listen Decide Communicate. His chapters on effective decision-making describe a sequence that mirrors the framework: concentrate on the few decisions that matter, gather information from people who disagree with you, and communicate the decision in terms that make the commitment clear and actionable.
Marquet's account of transforming the USS Santa Fe from the worst-performing submarine in the fleet to the best illustrates the framework applied to hierarchical organisations where communication failures are operationally dangerous. His "leader-leader" model pushes the Listen phase down the chain of command — giving subordinates the authority and expectation to surface information proactively rather than waiting to be asked. The result is a Listen phase that operates continuously rather than episodically.
Leaders who apply this model
Playbooks and public thinking from people closely associated with this idea.
Listen Decide Communicate — The three-phase leadership sequence. The order is fixed: gather signal, commit to a direction, then align the organisation through repeated, clear communication.
Leads-to
Disagree and Commit
Disagree and Commit is the protocol that converts the Decide phase into organisational action. Without it, the transition from Decide to Communicate stalls — dissenters re-litigate the decision, passive resistance slows execution, and the leader spends the Communicate phase defending the decision rather than explaining it. Bezos's formulation closes the loop: disagree during Listen, commit after Decide. The framework ensures that the team's energy shifts from debating the decision to executing it — which is the precondition for the Communicate phase to function as alignment rather than argument.
Tension
Decision [Velocity](/mental-models/velocity)
Decision Velocity — the speed at which an organisation converts information into committed action — creates productive tension with the Listen phase. Pure decision velocity says move faster. Listen Decide Communicate says listen first, which takes time. The tension resolves through calibration: the Listen phase should be proportional to the decision's reversibility and consequence. For a Type 2 decision, Listen might be a fifteen-minute conversation. For a company-defining strategic shift, Listen might be a three-month research process. The framework doesn't say "always listen for months." It says "always listen before deciding" — and the depth of listening should match the weight of the decision.
Servant Leadership prioritises the team's needs above the leader's agenda — which can create a distortion in the Decide phase. A leader so committed to serving the team that they cannot make an unpopular decision has confused listening with deferring. The Listen phase absorbs the team's input. The Decide phase may override it. A servant leader who listened to the team's preference for remote work and then decided to require three days in-office because the business data demanded it hasn't failed at servant leadership — they've completed the sequence. The tension: servant leadership strengthens the Listen phase but can weaken the Decide phase if the leader conflates serving with agreeing.
The framework's deepest insight is about sequence, not content. Two leaders can listen to the same people, make the same decision, and communicate the same message — and produce different outcomes because one ran the sequence correctly and the other didn't. The leader who decided before listening and then communicated is defending a pre-formed opinion. The leader who listened before deciding and then communicated is explaining a conclusion the team watched them reach. The team can tell the difference. The sequence is not just a process. It's a signal of respect for the organisation's intelligence, and that signal determines whether the communication is received as alignment or as propaganda.
The AI-era implication: the Listen phase is about to get dramatically more powerful and dramatically more dangerous. Leaders will soon have access to real-time sentiment analysis, meeting transcript summaries, and pattern detection across thousands of employee interactions. The listening surface area will expand by orders of magnitude. The danger is that synthetic listening — reading AI-generated summaries instead of sitting in rooms with real people — will produce a Listen phase that is broader but shallower. The data will be richer. The understanding will be poorer. The best leaders will use AI to augment their listening, not to replace it. They'll use the patterns to know where to go deeper, not as a substitute for depth itself.
