Reinventing how organisations work: the operating system model

Executive overview

Most organisations worldwide run on management assumptions invented on factory floors 100+ years ago — and those assumptions are now causing measurable harm: falling corporate longevity, declining return on assets, stagnant productivity.

Aaron Dignan argues that every organisation has an invisible operating system (OS): the norms, assumptions, and structures that govern how decisions get made and work gets done. Changing that OS — not just the tools or remote-work policies — is what produces real improvement.

The core insight: bureaucracy is the disruptor; adaptive organisations built on trust outperform command-and-control on every metric that matters.

Why the current model is failing

• Management was engineered for factory-scale consistency, not knowledge work or fast-changing markets
• Remote work and digital tools change the wrapping paper, not the underlying assumptions
• Corporate longevity on the S&P 500 has dropped from ~60 years to ~12–15 years
• Return on assets and productivity growth are both declining despite better technology
• Command-and-control systems are immobilising in dynamic environments

The traffic light vs. roundabout model

• A lighted intersection assumes people can't be trusted; it demands compliance and requires a central control apparatus
• A roundabout assumes people are competent; it uses two simple rules and trusts judgment
• Roundabouts are safer on fatalities, higher throughput, cheaper to build and maintain, and more resilient when the power fails
• Most organisations are full of traffic-light policies; the goal is to introduce more roundabouts
• Example: instead of a travel freeze, publish everyone's travel spend transparently — social accountability does what bureaucracy can't

The organisational OS: key components

• Purpose — not just a wall banner; needs ongoing dialogue at every level; should be held lightly and allowed to evolve
• Authority — who decides, and how; most orgs centralise authority but make decisions informally and intuitively
• Resources — how time and money are invested
• Workflow — how work moves; limiting work in progress is a high-leverage lever
• Information — empowering people without sharing information just produces bad decisions; the two must move together
• Seven further components exist; start with wherever you feel the most tension

The decision stack

• Below a risk threshold ("above the water line"): anyone can decide
• Mid-level decisions: you can decide, but must first seek advice from affected parties
• High-stakes decisions: require consent from multiple perspectives — not consensus, just "safe to try"
• Leaders should constantly ask: is this decision reversible? If yes, push it down

Starting from wherever you are

• Solopreneurs control workflow, tools, information flow, and how they make decisions — start there
• Team members without authority can still control how their team meets, communicates, and sets norms
• Most leaders are equally frustrated by bureaucracy; surfacing tensions and proposing experiments is often enough to unlock change
• Chesterton's Fence principle: understand why a rule exists before removing it — reinvent, don't just demolish
• Every tradition was new at one point; the five-day work week is as questionable as anything else