One page that makes processes, decision rights, data and systems explicit — and their conflicts visible.
Process maps live in operations, decision rights in nobody’s drawer, the data model in IT, the systems landscape in a vendor deck. Each is roughly right and collectively they contradict — and the contradictions surface as delivery failures eighteen months into a programme, priced at their most expensive.
The Blueprint forces the four layers onto one page: core processes, the decision rights that govern them, the data those decisions consume, and the systems that carry it. The value is not the page but the conflicts it makes visible — every place where a process assumes a decision right that does not exist, or a decision depends on data no system owns.
Each layer drafted from source material — process maps, minutes, data catalogues, contracts — before anyone is interviewed. The blueprint starts from what is written, not what is remembered.
Week 1–2A one-day working session with the executive team. The four layers go on the wall; every conflict is named, owned and logged. This is the workshop the format is known for.
Week 3The reconciled blueprint is signed as the single reference. Every subsequent initiative is tested against it; every change to it is versioned.
Week 4The blueprint is deliberately one page per business unit. A blueprint that needs an appendix has stopped being a decision instrument and become documentation.
Ahead of ERP and platform selections, where unpriced architectural conflicts become change orders.
Post-acquisition, to reconcile two enterprises into one page before systems integration is scoped.
As the architecture layer of any transformation portfolio — initiatives are sequenced against the blueprint, not around it.
Applied in more than twenty-five engagements since 2024, most visibly in technology selection and integration work:
The Institute stewards the format and revises it after every tenth application review. Changes are versioned; superseded editions remain citable.
Cite as: Markham Institute, “The Enterprise Blueprint”, MKM-F-005, v1.2 (2026).