Rethinking how organizations work: the operating system framework

Executive overview

Most organizations worldwide still run on a management model designed for factory floors 100+ years ago — built for compliance, hierarchy, and predictability. That model is failing: corporate longevity is shrinking, return on assets is declining, and productivity growth has stalled despite better technology.

Aaron Dignan argues that every organization has an operating system — the underlying assumptions, norms, and practices that govern how work gets done. Changing the wrapping paper (remote work, new tools) without changing the OS changes nothing.

The goal is to replace command-and-control defaults with systems that trust people, distribute authority, and treat reversible decisions as safe to try.

The factory model and why it persists

• Scientific management (Taylor, Fayol) separated thinking from doing — managers decide, workers execute
• Assembly line logic delivered real gains: consistency, quality, scale
• That model spread into knowledge work where it has no business being
• Corporate longevity on the S&P 500 has dropped from ~60 years (1960s) to ~12–15 years today
• Return on assets and productivity growth are both declining despite better tools
• The bureaucracy has become the bottleneck, not the enabler

Traffic lights vs roundabouts

• The traffic light assumes people are untrustworthy — it demands compliance and requires central control
• The roundabout assumes people can use judgment with minimal rules: yield to traffic in the circle
• Roundabouts are safer on fatalities, have higher throughput, cost less to build and maintain, and work when the power goes out
• The ratio in the US: ~1,113 traffic lights for every roundabout
• Most organizational policies, processes, budgets, and approval chains are traffic lights
• The goal: find the minimum constraints that let adults solve problems together

The organizational OS and its 12 components

• The OS is the set of assumptions and practices an organization runs on — visible only when you look for it
• Changing it requires questioning things treated as permanent: five-day weeks, manager approvals, centralised functions
• The 12 components include: purpose, authority, resources, workflow, information, and seven others
• They overlap and interact — improving one without the others can backfire (empowering people without sharing information leads to bad decisions)
• Start where the tension is highest, not at the top of the list

Purpose

• Purpose has shifted from pure profit to meaning, intent, and direction — but most organizations stop at the banner on the wall
• The risk: either too vague (grandiose statement, ignored) or too narrow (cascaded top-down, misses emergent opportunities)
• AWS would not have emerged from Amazon if purpose had been defined too narrowly around bookselling
• Better approach: ongoing dialogue about personal, team, and organizational purpose — explore the gaps rather than resolve them by decree
• Purpose is in flux as membership changes; hold it lightly but keep tuning it

Authority and the decision stack

• Traditional authority says: look up, comply, the boss decides — but most decisions are actually made by gut instinct, not decision science
• In fast-moving markets, authority needs to sit closer to where reality is being experienced
• A practical decision stack:
  • Below the waterline: decisions that require collective consent (irreversible, high stakes)
  • Advice-required tier: you can decide, but must seek counsel from affected or experienced parties first
  • Above the waterline: anyone can make the call — safe to try, reversible (e.g. Ritz-Carlton's $200/day guest resolution rule)
• Leaders should constantly ask: is this decision reversible or irreversible? Am I intervening where I don't need to?
• Pushing authority to the edge increases speed, adaptivity, and learning

Workflow and information

• Workflow problems: too much work in progress, lack of prioritisation, structure misaligned with how value is actually created
• Information problems: decisions made without enough context, knowledge siloed at the top
• A simple alternative to a travel freeze: publish everyone's travel spend transparently — creates social pressure, surfaces abuses, spreads best practices
• Transparency replaces control and treats people as adults
• Empowerment without information produces bad decisions and erodes trust in delegation

What individuals and teams can do without top-down permission

• Solopreneurs and team members alike control more than they think: workflow, tools, decision norms, meeting structure, communication patterns
• Ask: what's stopping us from doing the best work of our lives? Then sort by what's actually within your control
• Teams at the edge can set their own norms for how they meet, decide, and hold each other accountable
• Raise tensions explicitly in town halls or forums — most leaders are equally frustrated and looking for a way forward
• Frame experiments as "safe to try" rather than permanent changes — this lowers the barrier to leadership buy-in
• Chesterton's Fence: understand why a rule exists before tearing it down; reinvention starts with understanding, not demolition