CATWOE Analysis
CATWOE analysis is a six-element checklist used to build, then test, the sentence that says which system is under discussion, its root definition: Customers, Actors, Transformation, Weltanschauung, Owner, Environment. It comes from Soft Systems Methodology, the approach Peter Checkland developed for situations where stakeholders do not agree on what needs solving. Its deliverable is one root definition or several, each with its six-line grid. A team settles those definitions before eliciting requirements. The statement is tested against the six questions: a root definition in which one of the elements cannot be found is rewritten until it is there. One situation admits several, one per worldview held in the organisation.
Goal
CATWOE analysis frames a human activity system before its content is discussed. It breaks that system into six elements and forces each one to be named: who receives its output (Customers), who carries it out (Actors), what change of state it performs (Transformation), what worldview makes that change sensible (Weltanschauung), who has the power to stop it (Owner), what it has to take as given (Environment). The completed grid is then used to write or correct the sentence that says which system is under discussion.
The method has a name for that sentence: the root definition, a concise statement of a human activity system, built on the PQR formula, a system to do P, by Q, in order to achieve R. The checklist appears in Smyth and Checkland in 1976. Checkland describes the sequence in one direction: the root definition is drafted first, from a description of the situation, then the grid serves to check that it is well formed, each of the six elements having to be identifiable in it or implied by it. In a workshop the order is often reversed, the group answering the six questions before composing the sentence. Both directions describe the same iteration, the sentence and the grid correcting each other until they hold together.
The technique sits ahead of requirements elicitation and alongside the stakeholder-analysis techniques. Where the stakeholder list, map or personas and the stakeholder matrix establish who is concerned and with what weight, CATWOE asks what each of them believes the system is there to do. It extends problem shaping and reframing by producing one statement per worldview held in the organisation.
Usage
When to use
- Disagreement about purpose: several stakeholders defend different aims for the same initiative.
- Organisational transformation or service redesign: establishing what the system has to transform before a single requirement is written.
- Taking over or merging a service: naming who can stop the arrangement and what it has to take as given.
- Preparing an elicitation: avoiding the collection of requirements in the service of a purpose that is contested and never stated.
- A stalled project: reopening the question of purpose when requirements pile up without converging.
When not to use
- A stable, shared purpose: there is nothing to surface, go straight to process modelling or to elicitation.
- A bounded technical requirement: the discipline of the root definition costs more than it returns, a use case or an interface analysis frames the need faster.
Description
Transformation at the centre
The Transformation is the heart of the root definition: a defined input state, converted into a defined output state. The other five elements qualify or bound it. "Improve internal communication" names neither an input nor an output and leaves the analysis with nothing to work on. "Committee decisions that are not circulated become decisions the teams concerned can consult" names both: each of the other five questions can then be answered.
The participants: Customers and Actors
Customers are the beneficiaries or the victims of the transformation, whoever receives its output. A system converts inputs into outputs that sometimes work against people downstream of it, and naming them keeps the root definition honest. The client who commissioned the study is a Customer only if it receives the system's output.
Actors carry out the transformation. The word covers the people who do the work, without saying who decides that it continues: that authority belongs to the Owner. The common confusion is to write all the stakeholders into this box, which empties the question.
The worldview: Weltanschauung
Weltanschauung is Checkland's term for the worldview that makes the transformation sensible and explains why it is described the way it is. It is the element that quick accounts of the technique flatten to "context" or "the big picture". A Weltanschauung is an assumption: it treats the transformation as an activity that deserves to exist. The box calls for a belief that an identifiable person holds and that another can contest.
A different worldview produces a different transformation, so a different root definition. One situation therefore admits several legitimate root definitions, one per worldview held in the organisation, and the analyst's work is to bring them all out. A workshop that obtains a single answer per element in half an hour has produced a token consensus. What the technique produces is the disagreement made explicit, together with the root definitions that carry it.
What bounds the system: Owner and Environment
The Owner is the body with the power to stop the system or to change it fundamentally. The manager who directs the Actors day to day is the Owner only if that manager can also shut it down. In practice the box receives the project sponsor or the process owner in the sense of a RACI matrix, two roles that do not hold that power: in a cantonal administration the authority to close something down almost always sits at the political level or with the department that issues the service mandate. The question that settles it is: who can decide tomorrow that this stops.
The Environment gathers what the system has to take as given: regulation, budget ceilings, the infrastructure in place, neighbouring systems. A constraint the organisation can lift belongs to the content of the transformation, and filing it under Environment declares untouchable something that is negotiable.
Running the analysis
The session assumes a description of the situation is already in place, often a rich picture, the drawing with which the method captures the actors, the flows and the tensions of a confused context.
- Name the candidate system
A system relevant to illuminating the situation, framed narrowly enough that a single transformation can be described in it. Several candidates are normal at this stage. - State the transformation
An input state, an output state, the same thing passing from one to the other. This is the step that takes the longest and the one that decides the quality of everything else. - Name the worldview that supports it
The belief that makes this transformation an activity worth the effort. Putting it down early avoids discovering at the end of the session that two people were describing two systems. - Fill in the other four elements
Customers, Actors, Owner, Environment. For each, insist on named roles rather than a generic category. - Write the root definition in PQR
One sentence: what, by what means, in order to achieve what. Q names the means the Actors put to work, P and R come from the transformation and the worldview. - Hold the sentence against the grid
Is each of the six elements identifiable in the sentence or implied by it. Checkland holds that a root definition missing an element weakens the whole analysis that follows from it: the sentence is rewritten until all six are in it. - Replay for each distinct worldview
One grid per worldview, each treated as valid. The rival root definitions are presented to decision-makers together.
AI considerations
A language model works upstream of the session. Fed with the scoping documents, the committee minutes and the interview notes, it proposes a candidate grid and a provisional root definition for the workshop to contest. It can also be asked to state two or three rival worldviews on the same situation, the ones a homogeneous group will not produce on its own, after which the people concerned are asked whether anyone actually holds them. It is also a formal reviewer, checking that the transformation states an input state and an output state and that the six elements are found in the PQR sentence.
A Weltanschauung is a fact about people, and the model has no access to what the head of finance believes: it will produce a plausible and false one. It is equally ignorant of who can stop the system, a political fact that appears in no document. A model favours coherence, so it smooths over the divergences it is given, when divergence is the product being sought. Statements attributed to stakeholders are, finally, personal data, and passing them to an external service brings the Federal Act on Data Protection into play: the question is settled before the workshop.
Examples
A public-transport operator in Suisse romande is studying a real-time display of on-board occupancy, to reduce overcrowding on its bus lines at peak hours. The example illustrates one point only: two worldviews produce two root definitions of the same proposal.
Root definition held by the operations division: a system, run by the dispatch centre and the drivers, to convert unpredictable vehicle occupancy into crowding information available in real time (P), by instrumenting the vehicles and publishing occupancy at the stops and in the mobile app (Q), so that commuters choose a less crowded departure and the dispatch centre redeploys capacity, which improves punctuality without additional rolling stock (R).
CATWOE grid
Occupancy display, as the operations division sees it
| Letter | Element | Answer for this case |
|---|---|---|
| C | Customers | Commuters and season-ticket holders, in particular passengers with reduced mobility: beneficiaries if the information is accurate, worse off if the display sends them to a departure that is already full. |
| A | Actors | Drivers, dispatch-centre staff, the IT team that instruments the vehicles and runs the counting system. |
| T | Transformation | Vehicle occupancy that is invisible and unpredictable becomes crowding information published in real time at the stops and in the app. |
| W | Weltanschauung | The operations division holds that making crowding visible improves punctuality and perceived quality at a better price than buying vehicles. The finance division does not share that belief. |
| O | Owner | The director of operations, who holds the budget line and can shut the arrangement down, answerable in turn to the cantonal transport authority. |
| E | Environment | The service mandate agreed with the canton, the existing on-board electronics, an investment ceiling of CHF 400'000 and the Federal Act on Data Protection, counting on board being done by camera. |
The finance division holds another worldview: overcrowding is resolved by capacity and information only documents the lack of it. Its root definition of the same proposal would be a system, run by the finance division and the controlling unit, to convert observed but unquantified saturation into documented evidence of the capacity shortfall (P), by counting on board and by a periodic load report addressed to the canton (Q), in order to justify the purchase of additional vehicles (R). The Customers become the bodies that decide on the investment and the Owner becomes the head of finance. The display at the stops is now a by-product of the counting, where it was the very output of the system in the first definition. As long as this disagreement stays implicit, elicitation harvests requirements that serve two purposes.
Visualisations
The six elements hold different roles around the Transformation, and that structure can be read in space: the transformation at the centre, Customers and Actors as the direct participants, the Weltanschauung as the belief that makes it sensible, Owner and Environment at the limits of the system. A diagram gives that grouping at a glance.
The completed grid, for its part, is made of values: an element, its answer for one case. The deliverable of the session is the PQR sentence with that table, the one a team takes away, completes and corrects when the root definition moves.
Cost
| Phase | Level | Rationale |
|---|---|---|
| Preparation | Medium | Describing the situation before the session and bringing together stakeholders who hold different views. The effort goes into choosing the people: a homogeneous room makes the workshop pointless. |
| Execution | Medium | Two to three hours of facilitated workshop per candidate system: stating the transformation, filling in the six elements, writing the root definition and correcting it. Each additional worldview adds a pass. |
| Documentation | Low | One page per root definition, the PQR sentence and its six-line grid. It is revisited only if the purpose of the system shifts. |
Tooling
The most effective support is still a whiteboard or a flipchart with six zones drawn in advance and the PQR sentence written large above them. A colour code per stakeholder group shows that one box receives two irreconcilable answers. The exercise calls for no specialised equipment.
For distributed work, the collaborative whiteboards (Miro, Mural, FigJam) carry the same layout and keep the artefact editable between sessions, when rival root definitions are built over several weeks. For keeping, a wiki page or a scope document in the requirements tool holds the root definition and its grid next to the requirements they govern. A spreadsheet does the job as soon as several candidate systems are being compared.
Sources
- Smyth, D. S. and Checkland, P. B. (1976), Using a Systems Approach: The Structure of Root Definitions, Journal of Applied Systems Analysis, 5(1), pp. 75-83: the article in which the root-definition checklist appears in print for the first time, out of Smyth's work in Checkland's team at Lancaster.
- Checkland, P. B. (1981), Systems Thinking, Systems Practice, Chichester, John Wiley & Sons: the book that codifies Soft Systems Methodology and fixes the CATWOE acronym under its settled name and definition, including the Weltanschauung and the requirement that the six elements be found in the root definition.
- Checkland, P. B. and Scholes, J. (1990), Soft Systems Methodology in Action, Chichester, John Wiley & Sons: the mature formulation of the checklist, where the Owner is the body that could stop the system and the Weltanschauung what makes the transformation sensible.