What is decision architecture? Decision architecture is the deliberate design of the complete organisational system through which decisions flow — how they are classified, routed, owned, evidenced, recorded and reviewed — as opposed to improving any single decision or teaching any single technique.
Decision architecture treats decision-making as a system to be designed rather than a skill to be trained. Its components are the decision inventory, a classification scheme that determines how much process each decision warrants, routing and authority rules, evidence standards, documentation requirements, and review cadence. It is the layer at which several well-documented organisational changes operate. Amazon's distinction between one-way-door decisions, which are difficult to reverse and warrant careful analysis, and two-way-door decisions, which are reversible and should generally be made quickly and closer to the team doing the work, is a classification rule embedded in the operating model rather than a technique taught to managers. Bayer's Dynamic Shared Ownership is described by the company as an operating model that reduces management layers, organises people into cross-functional mission-led teams, and moves decisions closer to customers and operational work. Toyota changed governance structures to streamline board and executive decision processes, enable more local decision-making and move on-site information to management more quickly. The common thread is that decision improvement sometimes requires redesigning the organisation rather than training individuals within it.
What Is Decision Architecture?
Decision architecture is the deliberate design of the system decisions flow through — how they are classified, routed, owned, evidenced and reviewed. It treats deciding as something you design, not something you train people in.
Last updated: 2026-07-29
In short
Sometimes the reason decisions are bad is not that people reason poorly. It is that the decision reached the wrong person, four layers from the work, six weeks late, with a template that never asked for the contrary case. Decision architecture is the discipline of fixing that structurally.
Design, not training
Most decision-improvement effort targets individuals: teach managers frameworks, run workshops, circulate a checklist. Architecture targets the system those individuals operate inside — and when the system is the constraint, training cannot reach it.
- •A decision inventory comes first. You cannot design a system for decisions nobody has enumerated.
- •Classification determines process weight. Reversibility, exposure, urgency and regulatory impact decide how much rigour is warranted.
- •Routing decides who sees it. Authority placed far from the work produces slow decisions on stale information.
- •Standards are structural. What a decision brief must contain is an architectural choice, not a personal habit.
- •Review cadence is designed too. When a decision gets revisited should be set at the point it is made.
Three organisations that changed the structure
Each of these is an architectural change rather than a technique — the environment decisions happen in was altered.
One-way and two-way doors — Amazon
A classification rule built into the operating model: consequential, hard-to-reverse decisions get careful analysis; reversible decisions should generally be made quickly and closer to the team doing the work. The principle is matching process weight to the cost of being wrong. Amazon also uses written narratives read at the start of a meeting to force clearer reasoning than slides allow.
Dynamic Shared Ownership — Bayer
Described by Bayer as an operating model rather than a meeting technique: reducing management layers and bureaucracy, organising people into cross-functional mission-led teams, and moving decisions closer to customers and operational work with rapid cycles of decision, action and learning.
Structural change — Toyota
Toyota changed governance structures to streamline board and executive decision processes, enable more local decision-making, and move on-site information to management more quickly. Its longer TQM tradition rests on the same architectural principle: information travels upward while authority travels downward.
The part of the architecture that holds reasoning
An architecture specifies what a decision record must contain. That specification is where most designs quietly fail — because they ask for the outcome and not the argument.
A record shaped like reasoning
Claims, the reasons offered, the objections raised, and which of those went unanswered — a structure, rather than prose that has to be re-read and re-interpreted.
Classification the record can carry
Reversibility and exposure recorded with the decision, so the review cadence and the process weight it received are both auditable later.
Routing that keeps context
When a decision escalates or changes owner, the argument travels with it. Escalation without context is how a well-designed system still produces re-argued decisions.
Review against what was actually assumed
Reviewing a decision honestly requires knowing what it assumed at the time. If the assumptions were recorded as claims, hindsight has something to check itself against.
Architecture decides that reasoning must be captured. The reasoning layer decides whether what gets captured is worth reading.
Explore further
Enterprise decision excellence
The umbrella: how architecture, authority, evidence and culture combine.
Decision governance
Authority and escalation — the component architecture routes through.
Decision effectiveness
Speed and execution — what a good architecture is measured on.
Decision audit trail
The record layer the architecture specifies.
Decision documentation
Capturing decisions so they survive handover and review.
Structured decision making
The per-decision process an architecture standardises.
Frequently asked questions
What is decision architecture?
The deliberate design of the complete organisational system decisions flow through — how they are classified, routed, owned, evidenced, recorded and reviewed. It is a design discipline applied to the organisation rather than a technique applied to a decision.
How is decision architecture different from decision governance?
Governance is one component of architecture. Governance answers who decides and how things escalate; architecture is the wider design that also covers classification, evidence standards, documentation requirements and review cadence, and how those fit together.
What are one-way and two-way door decisions?
Amazon's classification: one-way doors are consequential and difficult to reverse, so they warrant careful analysis; two-way doors are reversible and should generally be made quickly and closer to the team doing the work. The principle is matching process weight to the cost of being wrong.
Do you need to reorganise to improve decisions?
Sometimes, and that is the uncomfortable claim of this discipline. If decisions are slow because authority sits four layers from the work, no amount of framework training reaches the cause. Bayer's Dynamic Shared Ownership and Toyota's governance changes are both structural rather than instructional.
Is decision architecture the same as choice architecture?
No. Choice architecture, from behavioural economics, concerns how options are presented to influence individual choice. Decision architecture concerns how an organisation routes, owns and records decisions. Similar names, different disciplines, and worth keeping apart.
Where do you start with decision architecture?
With an inventory of the important recurring decisions, then a classification scheme for them. Until you know which decisions repeat and what each is worth, routing rules and evidence standards are being designed for a system nobody has described.
References & further reading
Amazon. 2016 Letter to Shareholders.
The one-way-door and two-way-door classification, in Amazon's own words.
View source →Bayer. Dynamic Shared Ownership.
Bayer's description of DSO as an operating model — fewer layers, cross-functional mission teams, decisions closer to the work.
View source →Toyota Motor Corporation. Organizational Changes (75 Years of Toyota).
Governance changes to streamline decision processes and move on-site information to management faster.
View source →Blenko, M. W., Mankins, M. C., & Rogers, P. (2010). Decide & Deliver: 5 Steps to Breakthrough Performance in Your Organization. Harvard Business Review Press.
Organisational decision design and its link to performance.
View source →Design what a decision record contains
An architecture is only as good as what it captures. Make the reasoning — not just the outcome — the thing your system records.
Start free