Authority · Vocabulary
What Is Decision Architecture?
Most organizations never design how decisions get made. They inherit it - from reporting relationships, approval requirements, and unspoken rules about who is allowed to act on what they know.
Definition
Decision architecture is the intentional design of who decides, at what level, with what information, and within what timeframe - across the decisions that determine organizational performance.
Decision architecture is not an org chart. Org charts document reporting relationships. Decision architecture documents who is actually empowered to make which decisions - and what they need to do so effectively. Most organizations have the former without the latter.
It is also not a RACI matrix, which typically assigns responsibility and accountability labels without addressing the actual decision authority required to act on those labels. An organization can have a perfectly filled-in RACI and still operate with all real decisions traveling to the top of the hierarchy, because the authority required to act at lower levels was never explicitly granted.
The Four Elements of Decision Architecture
Who decides
The explicit identification of the role or individual empowered to make a given class of decisions - not who is consulted, not who is informed, but who makes the call. This is the most commonly absent element in organizations that say they have pushed decision-making down.
At what level
The organizational level at which the decision belongs - based on where the relevant knowledge is, not where the largest title is. Decisions that live too high in the organization are made with less information and slower response times. Both quality and velocity suffer.
With what information
The specific information required to make the decision well - and whether that information is available to the decision-maker when needed, without a request process. Information architecture and decision architecture are interdependent. Poor information access converts authorized decision-makers into de facto escalators.
Within what timeframe
The expected decision cycle for a given class of decisions - and the mechanisms that prevent decisions from stalling when the primary decision-maker is unavailable or when information is incomplete. Decisions without explicit timeframes default to the pace of the most cautious participant.
The Three Failure Modes
Decision concentration
Authority is held too high. The people closest to the work - with the most relevant information - cannot act on what they see. Every decision escalates regardless of its actual risk level. The organization moves at the pace of senior leadership capacity, which is always the bottleneck.
Decision diffusion
Responsibility is distributed widely, but actual authority to act is withheld. Everyone is accountable; no one can decide. The result is decision-by-committee, consensus requirements, and organizational movement that is slower than any individual participant.
Decision ambiguity
Ownership is unclear. When a decision point arrives, work stalls while people try to determine who is actually empowered to make it. The stall is not inaction - it is a transaction cost paid for every significant decision the organization makes.
Decision Architecture and Decision Velocity
Bain and Company research found that organizations with clear decision rights make decisions five times faster than organizations without that clarity - with no additional resources, technology, or headcount. The speed comes from eliminating the ambiguity, escalation loops, and approval overhead that accumulate in organizations that have inherited rather than designed their decision architecture.
In the Four A's of Organizational Readiness™, decision architecture is the primary structural determinant of the Authority dimension. An organization's decision velocity is largely a function of how well its decision architecture is designed - and how consistently that design is honored by the leaders who created it.
Source: Rogers, P. & Blenko, M. (2006). Who Has the D? How Clear Decision Roles Enhance Organizational Performance. Harvard Business Review, 84(1), 52–61. Blenko, Mankins, & Rogers (2010). Decide and Deliver. Bain & Company / Harvard Business Press.
Frequently Asked Questions
What is decision architecture?
The intentional design of who decides, at what level, with what information, and within what timeframe - across the decisions that determine organizational performance.
Why do most organizations lack intentional decision architecture?
They inherit it from the accumulated history of reporting relationships, approval requirements, and cultural norms about deference - which rarely get redesigned when organizational structure changes.
How does decision architecture affect decision velocity?
Organizations with clear decision rights make decisions five times faster than those without - with no additional resources. The speed comes from eliminating the escalation loops and approval overhead of unclear architecture.
From Builders Build
This idea is developed in Part Two: The Four Conditions, Chapter 15, The Third A: Authority.
Diagnose Your Decision Architecture
How fast are your decisions moving?
The Executive Diagnostic identifies whether Authority - including decision architecture clarity - is the primary constraint on your organization's performance.