Concept

Organisational Kayfabe

concept organisational-design strategy complexity emergence

Organisational Kayfabe

Organisational kayfabe is the systemic divergence between what an organisation officially believes and what its individual members privately know to be true. The term is borrowed from professional wrestling (a carny word for the collective fiction that the bouts are real fights), where kayfabe means “a thing everyone knows is fake and yet everyone acts as if real.” Alex Komoroske uses it to describe a near-universal property of large organisations, not a moral failure.


The mechanism

The entire phenomenon can be derived from a single asymmetry: you cannot make your boss look dumb.

  1. An individual contributor marks a project status yellow-green rather than red, knowing it will be fixed before it reaches leadership.
  2. Their manager does the same upward — a locally rational, often genuinely well-intentioned decision.
  3. After several layers, leadership operates on information many orders of magnitude from ground truth.
  4. When ground truth surfaces, the person who surfaces it is perceived as the cause of the problem, not the discoverer.
  5. Leadership response: “help me fix it, don’t announce it.” This is a reasonable ask.
  6. If fixing fails, holding the cognitive split (private truth + public kayfabe) becomes unsustainable. The easiest resolution: genuinely believe the kayfabe.
  7. Result: zombie organisation — every individual privately agrees the strategy cannot work; the collective continues to execute it regardless.

No bad actors required. The single asymmetry is sufficient and necessary.


What it is not

Komoroske is explicit: acknowledging kayfabe is not cynicism. It is a structural description, like acknowledging that coordination costs scale with the square of group size (see Slime Mold Principle — see transcript) or that entropy increases in closed systems. Once you can see the force, you can navigate it.


How it manifests

  • Status reports that are always green until a project is cancelled.
  • Strategies that every senior person privately doubts but publicly supports.
  • Post-mortems that identify process failures rather than the kayfabe that prevented earlier course correction.
  • “Alignment” meetings that produce agreement without belief.
  • Middle managers who act as kayfabe amplifiers because surfacing bad news costs them more than it saves the organisation.

Working with it, not against it

Kayfabe in small doses is lubricant — enthusiasm before a thing is proven. The pathology arises when it compounds through hierarchy.

Practical responses:

  • Frontier group / early adopter cohort. Allow a subset of the organisation to operate at ground truth, shielded from the kayfabe layer. (See also Aparna Chennapragada on AI Product at Microsoft — the Frontier programme as one implementation.)
  • Gardening rather than building. Don’t write official plans that require kayfabe to survive; plant cheap seeds that prove themselves without demanding organisational belief first.
  • Cover fire model. Deliver visible, unambiguous value (70% of effort) to earn the trust that allows ground-truth work in the remaining 30%.
  • Adjacent possible. Avoid committing the organisation to long-horizon bets that require sustained kayfabe to execute; prefer sequences of small, defensible steps.

Vehicle metaphor

Organisation sizeVehicleDriving style
SmallSports carTight steering, fast pivots
LargeBig rigFewer turns, more programme management, more slack in planning
DistributedSwarm of sports carsVisible incoherence; anti-fragile in aggregate

Apple: chose big-rig coherence, executed it brilliantly. AWS: chose the swarm, accepted visible incoherence, built anti-fragile capability.


Where mainstream views differ

Mainstream management literature tends to treat status-report distortion as a cultural problem solvable by “psychological safety” initiatives. Komoroske’s view is more structural: the asymmetry is thermodynamic, not cultural. Psychological safety interventions help at the margin but cannot eliminate the root asymmetry. The stronger intervention is structural: remove the penalty for surfacing bad news, or route around the hierarchy (early adopter cohorts, autonomous small teams).


See also