Dysfunction 3: Lack of Commitment

Lesson 5: Dysfunction 3 — Lack of Commitment

Commitment is the product of two things: clarity (everyone knows exactly what was decided and what it means for them) and buy-in (everyone actually agrees to support the decision, even if they argued against it). Dysfunctional teams have neither: decisions are fuzzy, and support is feigned.

Root cause: the desire for consensus and certainty. Consensus — universal agreement — is unattainable and counterproductive, so waiting for it means deciding nothing. And the craving for certainty — knowing the decision will work before making it — means waiting forever, because certainty never arrives.

What it looks like in practice

  • Ambiguity about the team's priorities — ask three members what the top goal is and get three answers.
  • Decisions are made, then quietly re-litigated in hallways for weeks.
  • "I'll see what I can do" culture; deadlines treated as suggestions.
  • Confusion about who is responsible for what.
  • Teams that miss opportunities because they waited for a decision that never came.
  • The telltale sign: revisiting. A committed team moves on; an uncommitted team reopens every decision at every meeting.
Feigned buy-in is worse than honest disagreement. An executive who says "yes" in the room and "this won't work" in the hallway leaves the team with ambiguity and himself with plausible deniability. Commitment doesn't mean agreement — it means support. The team needs both aired dissent and a promise to execute.

How it relates to the other dysfunctions

Lack of commitment is the child of fear of conflict: opinions that were never aired never get addressed, so people never feel their concerns were heard — and people only commit to decisions they helped shape. If the debate never happened, "agreement" is just politeness wearing a costume. Lack of commitment is then the parent of avoidance of accountability: you can't hold people to standards that were never clear, and people don't feel entitled to call out others on a plan they never really bought into.

There's a second, subtler cause worth naming: teams that demand consensus before deciding are actually demanding certainty — a guarantee the decision is right. That's impossible. Great teams make the best decision they can with the information they have, and then throw their weight behind it.

How to combat it

  1. Cascading messaging. At the end of every meeting, review the decisions made and agree explicitly on what will be communicated to each layer below. If the exec team can't articulate the same message to their reports, they haven't committed to it yet. This single practice exposes feigned buy-in immediately.
  2. Deadlines. Not just for deliverables — for decisions. "We will decide X by Friday" converts endless deliberation into closure. Equally important: agree on when the decision gets revisited, so people know the choice isn't forever and don't fight it forever.
  3. Disagree and commit. The famous rule: everyone gets heard, the team decides, and then everyone — including the dissenters — commits fully to executing the decision. Dissent belongs in the room, not after it. (This is the same discipline Andy Grove made famous at Intel and that Amazon codified in its leadership principles.)
  4. Worst-case scenario analysis. When the team is paralyzed by fear of a bad decision, ask: "What's the worst that could happen if we're wrong — and what would we do about it?" Naming the disaster shrinks it to a manageable contingency. Most feared decisions turn out to be reversible.
  5. Low-risk exposure therapy. Let the team practice deciding — and living with the consequences — on small, reversible choices. Each survived decision builds the muscle and the evidence that "deciding beats not deciding."
Fable tie-in: DecisionTech's executives each had their own private priority list until Kathryn forced real debate, then forced a single answer: new customer acquisition, with a public target of 18 new deals. Everyone argued, everyone committed — and for the first time, the whole company received one consistent message about what mattered.

Further Reading

🧠 Knowledge Check

1. Commitment is the product of which two things?

2. What is the telltale sign of a team that lacks commitment?

3. What does "disagree and commit" require of a team member who lost the argument?