Abhishek S.
Shipping in public. Listening in private.

Abhishek

I lead women’s Indo-Western & Premium at Max Fashion. I also wrote the AI that runs the buying floor.

Rare profile. Category operator who ships production code.

Senior Buying Leader · Max Fashion Women’s Indo-Western & Premium · 530+ India stores NIFT ’12 · Twelve years on the floor

abhishek@bengaluru ~ %
>role: senior buying lead
>dept: women’s indo-western + premium
>floor: 530+ stores india

Normal Accidents in AI Organizations

A five-agent workflow can make five 95%-reliable steps produce a fully correct run only 77.4% of the time. Assumption: each step fails independently and has equal reliability. Charles Perrow’s 1984 argument is sharper than “complex things break”: when interactions are hard to predict and steps are tightly coupled, failure can emerge without a careless person.

How an accident becomes normal

Perrow built his theory around the March 28, 1979 partial meltdown at Three Mile Island Unit 2. A relief valve stuck open while a control-room indicator reported the command sent to the valve, not its physical position. Operators saw a plausible display, took locally defensible actions, and worsened the coolant loss. The Kemeny Commission’s 1979 report treated the accident as an organizational failure as much as an equipment failure.

AI agent chains reproduce this shape. One model decomposes the goal, another gathers evidence, a third writes code, and a fourth holds credentials and acts. A wrong premise becomes shared state; later agents receive it as an input rather than a claim requiring proof.

[ P(\text{complete success}) = p^n ]

Here, (p) is the reliability of one handoff and (n) is the number of handoffs. At (p=0.95), five steps yield 77.4%; ten yield 59.9%. Correlated errors, shared prompts, and common tools can make the actual result worse.

Interaction pattern Loose coupling Tight coupling
Linear Draft, review, then publish Fixed job with automatic execution
Complex Agents explore; evidence waits for review Shared memory, live credentials, recursive action

The lower-right cell is Perrow’s danger zone.

Designing for interruption

Perrow’s question is not merely whether the model can be instructed to behave. It is whether the chain can be interrupted before uncertainty becomes action.

Useful friction includes queued handoffs, typed inputs, source provenance, spending limits, reversible writes, and credentials scoped to one task. A human gate belongs before the irreversible action, not after the audit log. An independent monitor helps only when it can inspect raw evidence; a monitor reading the same generated summary is another coupled component.

What’s contested

Perrow’s claim of inevitability remains disputed. Karlene Roberts’s 1990 study examined nuclear aircraft carriers as organizations that operated hazardous machinery with unusually few catastrophic failures. Andrew Hopkins argued in 1999 that normal accident theory applies narrowly and leaves “complexity” and “coupling” too ambiguous for some policy claims.

Evidence from AI organizations is thinner. Anthropic’s 2025 study tested 16 models in controlled corporate simulations and explicitly reported no evidence of the observed conduct in real deployments. That experiment studied intentional goal pursuit, not normal accidents. Treating it as proof would merge two different failure theories.

Why this crosses realms

concept civilization scale coordination asks how partial minds produce one result; normal accident theory asks how their handoffs produce a result nobody intended. concept ironies of automation explains why the nominal human supervisor may lose the skill needed for rare interventions.

concept distributed cognition locates the working mind across people, prompts, queues, and logs. concept bus factor asks whether anyone can reconstruct that mind after failure. concept ai alignment studies the objectives inside each model; Perrow studies the machinery connecting them.

An open question

If no person can replay why an agent chain changed an external system, is the missing artifact a better model, or an organizational black-box recorder?

Key Sources

Further Reading

Abhishek's take

On the buying floor, I keep agents away from a live range-plan change until each handoff carries the source and the owner’s approval. A neat summary can hide one bad assumption for three steps. The useful control is a queue with a reversible write, not a longer prompt.