Strategy making: reading a strategy against what the organisation does

A strategy states what an organisation intends. The organisation goes on deciding, spending and hiring in ways the strategy may or may not describe. This method reads the one against the other. It treats the scenarios strategists already write as fiction to be labelled and used for tests, not as evidence.

What is already known

Strategy has long been understood as more than a plan. Mintzberg and Waters separate the strategy an organisation intends from the one it realises, and the emergent pattern in between (Mintzberg and Waters 1985). Rumelt separates a strategy, which has a diagnosis, a guiding policy and coherent action, from a list of goals (Rumelt 2011).

There are working methods for reading a strategy as a text. Vaara and colleagues follow the making of a Finnish city’s strategic plan and name five features that give it force: self-authorisation, special terminology, discursive innovation, forced consensus and deonticity, the language of obligation (Vaara et al. 2010). Kornberger and Clegg read a city strategy as performative, something that does work in the organisation (Kornberger and Clegg 2011). Rouleau follows how middle managers interpret and sell a strategy in everyday routines (Rouleau 2005). The first of these reads what the text does to its readers and does not test it against what the city later did. That test is what Holagram adds.

The gap between what organisations say, decide and do has its own literature. Brunsson describes organisations in which talk, decisions and actions are decoupled, because each answers a different demand (Brunsson 1989). Meyer and Rowan describe formal structure adopted for legitimacy and kept apart from activity (Meyer and Rowan 1977), and Bromley and Powell review decoupling in the contemporary world (Bromley and Powell 2012). A strategy that does not match what the organisation does may therefore not be a fault to expose. It may be a document doing a different job.

The cascade, in which objectives become targets and targets become unit goals, assumes that levels add up. Its critics show what happens to a measure once it is a target: gaming in UK public spending numbers (Hood and Piotrowska 2020), metric fixation (Muller 2018), and rankings that reshape what they rank (Espeland and Sauder 2007). The second principle of Hola, that no level sums up another, says the same in general terms. Planning, on the other hand, does help on average: a meta-analysis of 87 correlations from 31 studies finds a positive, moderate effect of strategic planning on organisational performance, strongest for formal planning, in public and private organisations (George et al. 2019). A reading that calls a strategy ceremonial has to explain that.

Fiction already has a place in strategy, in scenario planning, and the evidence on it is mixed. With practising experts, using several scenarios did not change confidence overall, but judgement of a move shifted with how the move fared in each scenario (Phadnis et al. 2015). In a simulation, analysing several scenarios reduced strategic persistence through belief in a new strategy (Healey and Hodgkinson 2024). The route is belief, so a vivid scenario can persuade whether or not it is sound. One of the few published failures was a senior team that avoided the exercise (Hodgkinson and Wright 2002), and a later comparison with a successful intervention suggests checking how receptive the organisation is before starting (Wright et al. 2008). Causal layered analysis reads a statement at four depths, from the surface claim to the myth beneath it (Inayatullah 1998).

Practitioners already run forms close to this one. Policy steering rooms arrange material on four walls: the patterns, the proven, the promising and the possible (Mulgan and Quaggiotto 2023). Holagram’s registers can be laid over such a room, with a stamp for the register and the level on each item, and a separate hand for the test.

What Holagram adds to all of this is narrow: the four registers, a stated level on every claim, the rule that no reading judges itself, a test at a level below the document, and a place for synthetic hands.

Levels, and what each admits as a Trace

LevelNameTypical traces
5WorldDemographic, ecological, political and technological conditions; scenarios published by others
4FieldPeers’ strategies, regulators’ requirements, sector statistics, funding conditions, rankings and benchmarks
3OrganisationThe strategy document, board papers, annual report, budget, organisation chart
2UnitUnit budgets and plans, minutes, structure changes, recruitment notices
1MoveA decision, a purchase, a hire, a cancellation: the smallest unit of strategy in use

The layers of causal layered analysis measure depth of discourse and not scale. They belong inside the Reading register and are not mapped onto these levels (Inayatullah 1998).

The text and the ground

The text is the strategy document read with its siblings and not alone: earlier drafts, the mission statement, the annual report narrative, board papers, indicator sheets, budget and procurement notices, organisation charts, job adverts. Begin each study with a document sheet: who wrote it, for whom, from what template, and what job it does (to coordinate, to signal, to legitimate).

The ground is the pattern in what the organisation does (Mintzberg and Waters 1985), not a second document. Four public streams give it: what is funded (budget lines, grants), who is hired or appointed (job adverts, organisation chart changes), what is bought (procurement notices) and what is stopped (closures, withdrawn programmes). Each is a trace at move or unit level. The strategy’s claim is a trace at organisation level. The link between them is a Reading and cannot be a Trace. Indicator figures are the organisation’s own paper, with an author and an incentive (Hood and Piotrowska 2020), and are read as documents before they are used as traces.

Three tests

Agents

Boards, unit heads, staff, those the strategy is for, peers, regulators, and models that draft or summarise strategy documents. A recent strategy may be partly machine-drafted, so the document sheet asks which sections were written by whom, as a hands note would. For comparing passages, one early test of language-model judging found that pairwise comparison separated stronger from weaker corporate climate reports and held up better against text a model had been asked to wash (Chuang et al. 2025). It is a workshop paper, so treat it as a lead.

A worked entry

Invented, to show the shape.

LevelOrganisation (3), hands shown per register
TracehumanStrategy 2026–2030, p. 6: “resilience” appears 23 times. Annex B gives the two programmes that carry the word 2 per cent of spend.
Readinghuman“Resilience” relabels existing programmes. It does not change priorities. Layer: litany, with a worldview behind it that treats resilience as a brand. Coupling predicted: absent.
Fictionsynthetic, edited by humanIn the year of the review every programme has been renamed and none moved. The review finds the strategy implemented, and no one asks what was different.
Testhuman and synthetic, at unit level (2)The Fiction’s observables: budget lines unchanged, unit plans quoting the old names, no structure change. Check the 2025 and 2027 lines for the six programmes; ask two unit heads what changed in their work. Adversary: the label signals a later reallocation, so look for it in the next budget round. Result: unchecked

Where it goes wrong

Objections the literature raises

First study: a strategy whose term has ended, three weeks

Choose a strategy whose term has ended, so the outcomes are on record, from a public organisation that is not a client: a city, an agency, a university, or a national agenda with indicators set against benchmarks. Prefer one that has already been analysed in print, such as the strategic plan of Lahti (Vaara et al. 2010) or Sustainable Sydney 2030 (Kornberger and Clegg 2011), so that a published reading gives a second reader to set against Holagram’s. Public material only. Readings are about the organisation and its offices, not about named people.

WeekWorkProduces
1 · DocumentDocument sheet. Pick five priority claims. Write Readings, tag the layer and the coupling each predicts.About ten entries at the organisation level.
2 · GroundTrace each claim into budget lines, procurement notices, structure changes and published decisions. Alter writes the world in which the strategy worked; list its observables.Traces at move and unit level. Observables as leads.
3 · TestsCheck the observables. With consent, ask two people at unit level, or read public minutes. The Adversary writes the failure world. Compare the readings with the published analysis. Close entries.The diagram, the failure log, a two-page case, a conventional write-up of about 2,000 words.

What would show it works. The counts on the Research page, and at least one claim of the form “the strategy says X, the organisation does Y” that was tested at the unit level and either held or broke for a stated reason.

Read next