Organisation design
Turns the operating model into an actual structure — who reports to whom, how many, and what each unit is accountable for. The step between deciding how the business must work and telling anyone their job has changed.
The printable canvas and the handoff into Claude Code are part of a paid plan. See what a plan includes. It needs the Claude desktop app on this machine, and your team and the prompt library already installed in that project — we cannot see your disk, so open it there.
What it is
The design of reporting lines, unit boundaries and accountabilities so the organisation can execute the strategy it has chosen. It starts from the work — the processes and decisions the operating model requires — and derives structure from that, rather than starting from the current chart and moving the boxes around.
- The work first
- Which processes and decisions the structure has to support. Designing from the existing chart preserves the existing problems with new names on them.
- Grouping logic
- By function, geography, customer, product, or a matrix of two. Each grouping makes one thing easy and another thing hard; the choice is which trade-off you would rather spend the next three years managing.
- Spans and layers
- How many people report to each manager, and how many levels sit between the top and the front line. Narrow spans create layers, and layers slow decisions more reliably than anything else in the design.
- Accountability
- What each unit owns and is measured on. Two units accountable for the same outcome means neither of them is.
- Interfaces
- Where units have to work together, and how that is governed. Most of the pain in a new structure sits in the gaps between the boxes rather than inside them.
- The people question
- Which roles are new, changed, contested or gone. It is a separate exercise from the design, and running the two together is how a design gets bent to fit the incumbents.
How you run it
- Start from the operating model, not the chartList the decisions and processes the structure must support. If nobody can do that, the design work is premature and will be redone.
- Generate two or three genuine optionsOne option is a proposal, not a design. Each should make a different trade-off, and each should be describable in a single sentence.
- Set spans and layers explicitlyDecide the targets, then test the design against them. Layers accumulate by accident and are never removed by accident.
- Name what each unit is accountable forOne owner per outcome. Where two units share one, either merge them or split the outcome — do not leave it shared and hope.
- Design the interfaces, then the peopleGovernance for the gaps between units first, and only then who sits where. Reversing that order is how the design bends around whoever is already in post.
The prompt
Run this tool in your own Claude
The short prompt starts your partner against the library on your disk. The long one carries everything with it and needs nothing installed.
Your playbook
It lands in the earliest stage this tool suits. Move it on the Playbook page.
You’ll need
- An agreed target operating model, or at least the processes it implies
- The current structure with real headcount, spans and layers
- The decisions each unit must be able to make without escalating
You’ll end up with
- Two or three structural options, each with its trade-off named
- Spans, layers and accountabilities for the chosen shape
- The roles that are new, changed, contested or gone