Skip to content
Book a demo Get Started

The library of organizational structures and models.

Over the years we have written up the ways organizations choose to structure themselves, from Kotter’s dual operating system to Haier’s RenDanHeYi. Here they are side by side, each with a guide to how it works and what it looks like in practice.

Two colleagues at a drafting table spread with different ways of drawing an organization, one holding up the structure that fits their team

Side by side

Ordered from the models that keep the hierarchy to the ones that replace it.

Model Who decides How work is organized Fits best Origin
Dual operating system The hierarchy runs the business, a volunteer network drives change Line organization plus projects and working groups Established companies that need to change while they keep running John Kotter, 2012
Mission Based Teams Teams that form around a mission, next to the formal structure Mission teams, staffed from across the line organization Large enterprises tackling problems that cut across departments Roche
SAFe (Scaled Agile Framework) The portfolio sets direction, release trains plan together each increment Agile release trains of teams, alongside the line organization Large enterprises coordinating many teams on one portfolio Dean Leffingwell, 2011
Spotify model Autonomous squads, with chapters keeping craft standards Squads grouped into tribes, crossed by chapters and guilds Product and software organizations scaling agile teams Spotify, 2012
Dynamic Shared Ownership Autonomous teams, with leaders who coach rather than approve Small teams working in 90-day cycles Large corporations removing layers of management Bayer, 2024
RenDanHeYi Microenterprises, each with its own customers and results Microenterprises linked in ecosystems Companies that want every team close to its customer Zhang Ruimin, Haier, 2005
Viable System Model Each unit steers itself, higher levels serve and coordinate the ones below Nested units, each able to run itself, inside larger ones Organizations that want autonomy at every level without losing coherence Stafford Beer, 1972
Beta Codex Teams at the periphery, facing the market, with the center serving them Cells in a center and periphery network (the Peach model) Organizations moving from command and control to networks Niels Pfläging, 2008
Buurtzorg model Self-managing teams, supported by coaches instead of managers Neighborhood teams of up to 12 people Service work done close to clients, such as care Jos de Blok, 2006
Semco Style Employees, who vote on decisions and set their own hours and pay Small self-managing units Companies ready to build radical trust and transparency Ricardo Semler, Semco, 1980s
Holacracy Roles, through a written constitution and governance meetings Circles of roles, each with a purpose and accountabilities Organizations that want explicit, rule-based self-management Brian Robertson, 2007
Sociocracy and S3 Circles, by consent: a decision passes when no one has a reasoned objection Nested circles, linked by people who sit in both Cooperatives, nonprofits and values-led teams Gerard Endenburg (1970s), S3 since 2015

The guides

Most organizations run a mix

Few organizations follow one model to the letter. Map yours as it really is, and see which parts of which model it already uses.

Start mapping Explore live maps