The structural blueprint of the enterprise. Processes, decision rights, data and systems go on one page, and the places where they contradict each other get named there rather than discovered late, when the contradiction is already being paid for as a delivery failure and the cheapest moment to have settled it has long passed.
A major systems decision is approaching and nobody can say, on one page, how the enterprise actually runs.
Decisions route through everyone because decision rights were never written down, or were written down once in a governance pack and never tested against a decision anyone actually had to make.
Two organisations must become one after an acquisition, and the integration is being scoped against two contradictory architectures.
Every programme rediscovers the same process, data and system conflicts at month nine, at their most expensive.
Processes, decision rights, data and systems on one signed page per business unit. The conflict log comes with it, and that is the page clients read twice.
Who decides what, tested against the last ten real decisions before adoption. Adoption follows the test, not the workshop.
The structural choices, their rationale and their owners, versioned from day one. Where a later version contradicts an earlier one, the earlier one stays in the file with the date it was superseded, so a reader can see what we got wrong and when we corrected it.
Every in-flight and proposed initiative scored against the blueprint: aligned, conflicting, or duplicative.
We draft each layer from source material the client already holds, which means maps, minutes, catalogues and contracts, and it is slower than interviewing people about how they believe the process works. Written evidence first. Interviews second.
The four layers go on one wall with the executive team. Every conflict is named, owned and logged. The session needs the people who can settle an argument, not their delegates.
The reconciled blueprint signed as the single reference; the decision ledger tested against the last ten decisions.
Initiatives are tested against the blueprint at the monthly forum. Changes are versioned, never improvised.