Most enterprises do not have an AI technology problem. They have a collective-action problem, and AI makes it more expensive.
Only 5% of companies capture AI value at scale, while 60% report minimal gains despite substantial spend (BCG, 2025). Just 39% see any enterprise-level EBIT impact from AI (McKinsey, 2025). The models are not the bottleneck. The way groups of people decide is.
Three classic pieces of organizational research explain this better than any technology roadmap I have seen. In this post I connect them, turn them into a simple framework, and tie it back to the operating model every CXO is now redesigning for AI.
Executive summary
- Three theories explain the gap. Smith and Berg show why groups freeze. Harvey shows why they agree on what nobody wants. Pfeffer and Sutton show why they know what to do but do not do it.
- Together they form one failure chain. A group can fail to decide (Stuck), decide wrongly through false consensus (Silent), or decide rightly and not act (Stalled). There is no fourth way to miss the right action.
- AI raises the cost of each failure. Pilots approved by polite consensus, agent programmes nobody owns, and value nobody measures are the same three failures at machine speed.
- The fix sits in the operating model. Five levers matter: decision rights, team design, workflow, metrics and incentives, and leadership behavior.
- CXOs can start in 90 days. Diagnose the top 10 AI decisions, install dissent and decision-latency mechanisms, and move execution authority to outcome-owning human-agent teams.
Three diagnoses, one failure chain
1. Stuck: why groups freeze (Smith and Berg)
Kenwyn Smith and David Berg's Paradoxes of Group Life (1987) argues that group life is made of opposing pulls that cannot be resolved. They group 12 paradoxes into three clusters:
- Belonging: identity, involvement, individuality and boundaries.
- Engaging: disclosure, trust, intimacy and regression.
- Speaking: authority, dependency, creativity and courage.
Their companion paper in Human Relations makes the key point: these conflicts are "released" rather than resolved once a group sees them as essential to its life. A group that treats a paradox as a problem to settle, picking one side to win, oscillates or freezes.
Where it fails: before the decision. No decision is made.
2. Silent: why groups agree on what nobody wants (Harvey)
Jerry Harvey's The Abilene Paradox tells the story of a family that makes a hot, 53-mile drive to Abilene that nobody wanted. Each member assumed the others wanted to go. Harvey's insight is that the hard organizational problem is managing agreement, not conflict.
He describes a recognizable pattern:
- Members privately agree on the problem and on the fix.
- They fail to say so, and send misleading signals instead.
- The group acts against what its members actually want.
- Frustration, blame and subgroups follow, and the cycle repeats.
The deepest driver is fear of separation from the group. Mark Murphy in Forbes recently framed the same issue as a team-design problem: silence gets read as agreement.
Where it fails: at the decision. The wrong decision is made.
3. Stalled: why knowing is not doing (Pfeffer and Sutton)
Jeffrey Pfeffer and Robert Sutton's The Knowing-Doing Gap (2000) shows that firms usually know what to do. Five things stop them doing it (chapter summary):
- Talk substitutes for action.
- Memory substitutes for thinking.
- Fear prevents acting on knowledge.
- Measurement obstructs good judgment.
- Internal competition turns colleagues into rivals.
Stanford GSB's excerpt stresses the last one: zero-sum internal contests destroy the cooperation that interdependent work needs.
Where it fails: after the decision. The right decision is not executed.
Why AI raises the stakes
AI adoption is broad, but value is narrow. Every major 2025 study finds a small leading group pulling away from a large stalled majority.
The three failure modes map directly onto these numbers:
- Stuck shows up as decision latency. AI shifts authority, identity and dependency all at once. Those are exactly Smith and Berg's paradoxes of speaking and belonging. When leaders are unsure whether a human or an agent owns an outcome, they default to committees. Gartner expects at least 15% of day-to-day work decisions to be made autonomously by 2028 (W.Media). Decision rights written for a human-only firm will not hold.
- Silent shows up as pilot theatre. Many AI programmes get approved because nobody wants to look like the sceptic in the room. The approvals look like consensus. The cancellations that follow are the drive home from Abilene.
- Stalled shows up as the value gap. Most firms know AI needs workflow redesign, yet McKinsey's high performers are almost three times more likely to actually do it. MIT NANDA blames a "learning gap" and brittle integration, not model quality. That is the knowing-doing gap in its purest form.
The human signal is moving the wrong way. Manager engagement fell from 30% to 27% in 2024 (Gallup). Positive views of GenAI rise from 15% to 55% where leadership support is strong, yet only about a quarter of frontline staff say they get that support (BCG). Managers are the layer through which all three failures flow.
My framework: the Movement Stack
A group misses the right action in only three ways, and each is fixed through the same five operating-model levers. The failure modes are mutually exclusive by symptom: no decision, a wrong decision, or a right decision left undone. Together they cover the whole path from tension to action.
The five levers are the parts of an operating model that shape how groups decide and act:
- Decision rights: who decides, and by when.
- Team design: how humans and AI agents share the work.
- Workflow: how work moves end to end.
- Metrics and incentives: what gets counted and paid.
- Leadership behavior: what leaders model every day.
Diagnose first, then apply the lever. Adding more dissent, a Silent fix, to a Stuck team only adds paralysis.
If you are Stuck: create decisiveness
- Decision rights: one named owner per decision, with a decide-by date.
- Team design: define what humans own above the loop and what agents do inside it.
- Workflow: sort decisions into reversible and irreversible, and give the reversible ones a fast lane.
- Metrics and incentives: track decision latency as a board KPI.
- Leadership behavior: name the paradox out loud and hold both sides instead of forcing a choice.
If you are Silent: create real voice
- Decision rights: collect independent written positions before any group discussion.
- Team design: rotate a formal challenger role, and add an AI red-team agent that is told to disagree.
- Workflow: run a pre-mortem and set kill criteria before any AI investment is approved.
- Metrics and incentives: measure voice, such as recorded dissent and "my opinion counts" scores.
- Leadership behavior: the most senior person speaks last and rewards bad news.
If you are Stalled: create motion
- Decision rights: execution authority sits with the team that owns the outcome.
- Team design: small, cross-functional human-agent teams replace functional committees.
- Workflow: redesign end to end; every pilot scales or stops within 90 days.
- Metrics and incentives: a few P&L-linked value measures, and no rankings that pit teams against each other.
- Leadership behavior: treat reasonable failure as learning, and build the system rather than making every decision.
This is consistent with where operating models are heading anyway. McKinsey's work on the agentic organization describes small, outcome-focused teams of humans who supervise AI workflows, with governance that is real time rather than periodic. Those teams will only work if the three failure modes are designed out from the start.
What CXOs should do in the next 90 days
Treat collective action as an operating-model workstream with an owner, a baseline and a deadline, not as a culture campaign.
Days 0 to 30: Diagnose
- Take the 10 largest open AI decisions and investments, and classify each as Stuck, Silent, Stalled or healthy.
- Baseline three numbers: decision latency, pilot-to-production rate, and share of AI spend with a tracked P&L outcome.
- Run Harvey's test anonymously with each leadership team: would members privately reverse a decision they publicly backed?
Days 31 to 60: Install the mechanisms
- Give every AI decision a single owner and a decide-by date.
- Make pre-mortems and kill criteria a gate for AI investments above an agreed threshold.
- Collect written positions before every steering committee, and have the most senior person speak last.
- Redraw decision rights for three end-to-end workflows, stating where humans sit in the loop, above it, or out of it.
Days 61 to 90: Move authority and money
- Hand two or three workflows to small human-agent teams that own the outcome end to end.
- Shift part of leadership incentives from functional KPIs to shared value measures.
- Scale or stop every pilot older than 90 days.
- Report the three baseline numbers to the board quarterly, next to the financials.
The test of success is simple: fewer open decisions, more pilots scaled or stopped, and dissent recorded before decisions rather than blame after them.
Limits of this argument
I stress-tested this framework the way I would review a colleague's work. A few honest caveats:
- Scope. The framework does not cover honest error, where genuine debate still picks the wrong option. Nor does it cover drift, where a good decision goes stale because nobody revisits it. A fourth mode, failure to learn after acting, may be worth adding.
- Evidence quality. The BCG and McKinsey figures come from large but self-reported surveys, and the link between workflow redesign and performance is correlation, not proof of cause. The MIT 95% figure is widely quoted but rests on a small sample, so I treat it as directional. The decision-making and psychological-safety data predate GenAI.
- Regional fit. All three theories come from US research. In the hierarchical cultures common across APAC, I suspect Silent is the dominant failure mode, and "the leader speaks last" on its own will not unlock voice.
- AI can make Silent worse. AI assistants tend to agree with whoever is asking. A red-team agent only helps if it is explicitly instructed to disagree and its objections are logged.
Smith and Berg would also warn against using this framework as an either/or tool. The aim is not to maximize dissent or speed. It is to hold speed and voice, autonomy and control, in useful tension.
HTH...
A Tech Artist 🎨
Sources
- Smith, K. K. and Berg, D. N., Paradoxes of Group Life, Jossey-Bass, 1987: Internet Archive record, Stanford SearchWorks, Scribd summary
- Smith, K. K. and Berg, D. N., "A Paradoxical Conception of Group Dynamics", Human Relations, 1987
- Harvey, J. B., "The Abilene Paradox: The Management of Agreement"
- Murphy, M., "The Abilene Paradox Is Why Overly Polite Teams Make Terrible Decisions", Forbes, Dec 2025
- Pfeffer, J. and Sutton, R. I., The Knowing-Doing Gap, 2000: notes, Stanford GSB excerpt, Bookey summary
- BCG, The Widening AI Value Gap, Sep 2025
- BCG, AI at Work 2025, Jun 2025
- McKinsey, The State of AI in 2025
- McKinsey, The Agentic Organization, 2025
- McKinsey, Decision Making in the Age of Urgency, 2019
- McKinsey, Psychological Safety and the Critical Role of Leadership Development, 2021
- MIT NANDA, The GenAI Divide, Jul 2025, via Virtualization Review
- Gartner agentic AI prediction, Jun 2025, via Reuters/The Star
- Gallup, State of the Global Workplace 2025



No comments:
Post a Comment