Purpose and mandate
Orders purpose, vision, mission, values and objectives into a structural hierarchy, built upwards from why rather than downwards from a number.
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
Richard Whittington's ordering of the related strategy concepts into a structural hierarchy, built from the foundation upwards rather than from objectives downwards. Purpose sits at the base as the philosophical answer to why the organisation exists; vision, mission and values sit progressively closer to day-to-day behaviour; objectives sit at the top as the quantitative measures that should, if the hierarchy is coherent, follow from everything beneath them.
- Purpose
- The most fundamental answer to why the organisation exists, beyond making money for its owners. The philosophical foundation everything else should be built on, and the layer most organisations have never actually written down.
- Vision
- What the organisation is trying to become — a picture of a future state, distinct from purpose in that it can change as the organisation grows, where purpose typically does not.
- Mission
- What the organisation actually does, day to day, to pursue the vision in service of the purpose — the operational translation of the two more abstract layers above it.
- Values
- How the organisation behaves while pursuing the mission — the constraints and commitments that hold regardless of which specific strategy is being pursued at a given time.
- Objectives
- The quantitative measures at the top of the pyramid. Built from the layers beneath, rather than a starting point in their own right — an objective with no purpose beneath it is a number nobody can explain.
- Hybrid reconciliation
- For organisations holding both a commercial purpose and a mission-driven one, the exercise's hardest and most valuable output: naming explicitly how the two relate, rather than leaving them to coexist unreconciled and periodically in tension.
How you run it
- Write purpose first, before anything else in the hierarchyWhy the organisation exists beyond making money for its owners. Resist the pull to start from objectives, which is backwards.
- Build vision and mission from the purposeWhat the organisation is trying to become, and what it actually does day to day to get there — both explicitly traced back to the purpose above them.
- Name the values that hold regardless of the specific strategyThe commitments that constrain how the mission is pursued, not a generic values-statement list.
- Derive objectives from everything beneath themQuantitative measures that follow from the purpose, vision, mission and values — not invented separately and bolted on top.
- Surface and name any genuine disagreementEspecially in a hybrid organisation holding both commercial and mission-driven purposes. An unreconciled tension left unnamed resurfaces at the worst possible moment.
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
- Genuine leadership disagreement, if it exists, surfaced rather than papered over
- The organisation's actual stated purpose, vision, mission and values, wherever they currently live
- For a hybrid organisation, both the commercial and the mission-driven purposes it holds
You’ll end up with
- Purpose, vision, mission, values and objectives ordered and reconciled, rather than existing as disconnected statements
- Any genuine internal disagreement about purpose named rather than left unresolved
- A single-sentence purpose statement the leadership team can agree on