The strategy document is one of the most consistently misused tools in organisational life. Organisations invest significant time and money in strategy processes, produce a document, and then watch it sit unused while the organisation continues to operate on instinct and habit. This is not always a failure of the strategy. Often it is a failure of the document. This article is about the editorial and structural choices that make the difference.

Length: the thirty-page rule

A strategy document that cannot be read in a single sitting will not be read at all. At Absolute Derive, we aim for thirty pages maximum for a full organisational strategy. This is not an arbitrary limit. It is a discipline that forces clarity. If a strategic priority cannot be explained in two pages, it is not yet clear enough to act on. The process of cutting a sixty-page document to thirty pages is itself a useful strategic exercise: it forces the organisation to decide what actually matters.

Structure: what to include and what to leave out

A useful strategy document contains four things: a clear statement of what the organisation is for (not a mission statement, a plain sentence), an honest assessment of the gap between current reality and that purpose, three to five specific strategic priorities for the next three years, and a set of decisions that need to be made in the first six months. It does not contain a values list, a SWOT matrix, or a stakeholder map. Those belong in the working papers that informed the strategy, not in the strategy itself.

Language: writing for the person who will use it

Strategy documents are usually written for the person who will approve them, not the person who will use them. The result is language that is careful, hedged, and abstract. A document written for the director and her three heads of department looks different: it names specific decisions, uses the organisation's own vocabulary, and is direct about what is uncertain. We always ask, before we write a word, who specifically will sit down with this document on a Monday morning and try to make a decision from it.

Including disagreement

The most useful strategy documents we have produced include sections that record disagreement. Not as a failure of the process, but as an honest account of the organisation's current state. When a leadership team genuinely disagrees about a strategic priority, recording that disagreement in the document is more useful than papering over it with a compromise formulation that nobody believes. It creates the conditions for the disagreement to be resolved deliberately, rather than playing out in the organisation's day-to-day decisions.

The review cycle

A strategy document without a review cycle is a document without accountability. We recommend a formal review at six months and twelve months, structured as a short meeting with a specific agenda: what has changed in the operating environment, which priorities are on track, which are not, and what decisions need to be revisited. The review meeting should produce a short written update to the strategy document. Over three years, this creates a record of how the organisation's thinking has evolved, which is itself a useful strategic asset.

If you are working on a strategy document and finding that the process is producing something you do not quite trust, our thinking on strategy has more on this. Or you can start a conversation directly.