strategyplaybook.aiSqwyz
Sign in
← All 124 tools
Execution · Plan

Target operating model design

Designs how the organisation must work to deliver the strategy — processes, structure, people, technology, governance. Heavy machinery, and premature restructuring destroys more than it builds.

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.

Stage
04 Plan
Works at
All levels
Maturity
Established SME → Large organisation
Time
Six to twelve weeks for a real one

What it is

A description of how an organisation must be configured to deliver its strategy, across every layer from process to governance. Distinct from an organisation chart, which is one output of it, and from a restructure, which is what happens when the design step is skipped.

Value streams and process
How work flows end to end to produce something a customer values. The foundation — structure should follow this, not precede it.
Organisation and structure
How people are grouped, who reports where, and where accountability sits. An output of the design rather than its starting point.
People and capability
What skills are needed, in what numbers, where, and how the gap is closed.
Technology and data
The systems that enable the processes, and the data that flows through them. Frequently the binding constraint on how fast the model can change.
Governance and decision rights
Who decides what, at what threshold, with whom consulted. The layer that determines whether the model works in practice.
Locations and sourcing
Where work happens and who does it — internal, outsourced, offshore, partnered.
The mistake people makeBeginning with the org chart is the classic failure. It produces a reorganisation that moves people between boxes, changes nothing about how work flows, and costs a year of productivity.
What it’s forDelivering the strategy needs the organisation to work differently, not just harder.
What it’s not forYou are early. TOM work is heavy, and premature restructuring destroys more than it builds.

How you run it

  1. Start from capabilities, not from the org chartWhat must this business be able to do? Design the model to deliver those, then work out who sits where. Reversing this produces a reorganisation.
  2. Design the value streams firstHow does work actually flow end to end to deliver for a customer? Structure should follow the flow, not cut across it.
  3. Work through every layerProcess, organisation, people and capability, technology and data, governance and decision rights, and locations. Skipping any produces a model that fails at the seam.
  4. Decide the decision rights explicitlyWho decides what, at what threshold, and who must be consulted. This is the layer that determines whether the model actually functions and the one usually left implicit.
  5. Sequence the transition with gatesBig-bang operating model changes fail. Sequence by value stream or capability, with checkpoints to stop or adjust.

The prompt

Two ways to run it

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.

🔒 Prompt locked

Everything above is free — what this tool is, what it is for, what it is not for, and how to run it as a workshop. Three tool prompts a month are free with an account; beyond three, and for the printable canvas, it is the paid part.

See plans — from £19 a month

Your playbook

It lands in the earliest stage this tool suits. Move it on the Playbook page.

You’ll need

  • A settled strategy and the capabilities it needs
  • Current-state process and structure documentation
  • Executive sponsorship that will survive the difficult phase

You’ll end up with

  • The operating model across each layer
  • A gap analysis against current state
  • A sequenced transition plan with decision points

Runs well with

AI risk classification and governanceAlliance and partnership designAssumption logBackcasting