The decision problem under the work.
Use this hub when the team is busy, the plan sounds reasonable, and the same business problem still returns. The issue may be who decides, what consequence is accepted, and what authority actually moved.
More work does not fix the wrong decision.
A company can move quickly and still move inside the wrong frame. Decision architecture asks who decides, what is being decided, what cannot be delegated, what changes after the decision, and which consequence the company is really accepting.
Use it before the consultant brief, the new hire, the tool purchase, or the board discussion turns a misnamed problem into a longer project.
A faster machine still wastes money when the wrong person owns the switch.
AI exposes the decision layer.
The tool wave makes weak judgment faster and strong judgment more valuable.
Authority is architecture, not vibes.
A stuck decision often looks personal from the outside. Inside the company, the real issue is usually rights, consent, consequence, and who has to carry the result.
Text version: the real decision sits between four rights. Decide means who carries the call. Consent means who can stop it. Consult means who must be heard. Inform means who must keep moving after the decision lands.
Decision pages should hurt and clarify.
This hub is where warm-up content becomes serious. The owner should feel understood and slightly cornered by reality.
The decision will not move.
The situation is visible, expensive, and strangely resistant to action.
The team calls it execution.
The company treats a direction problem as a performance problem.
A fixer gets hired too soon.
The company asks someone to execute without giving them a decision architecture to execute inside.
Authority hides in the approval path.
People attend the meeting, but the actual decision rights are elsewhere.
Name the layer.
The owner routes to the right next step after the real decision is named.
Start with these three.
If this is your first time on the hub, these are the three pages worth opening first. Each is a different page mode and surfaces a different review.
Decision Architecture Explained
The canonical reference for the category.
Diagnostic pageWhy This Decision Is Stuck
A owner-facing page that names the stall without jumping to a service pitch.
Decision guide pageThe Authority Map
A compact page that shows decide, consent, consult, and inform roles.
Use this hub when the decision has structural consequence.
- Will the decision change control, ownership, authority, capital, governance, or the operating model?
- Does everyone agree something must happen, while disagreeing on what the decision actually is?
- Would execution improve speed while leaving the wrong direction intact?
- Is someone expected to act without the authority needed to carry the result?
- Will the cost of delay compound if the company keeps discussing symptoms?
Authority becomes visible when the real decision is mapped before action starts.
This is where Decision Architecture stops being an abstract category. If a person is expected to carry the result without decision rights, the work is already misdesigned. The map belongs at the point where authority has to be named.
Where the owner routes next.
This hub should connect upward to the Atlas, sideways to role bias, and outward to path pages only after the owner has named the decision layer.
Concept-level questions this layer answers
"What is" questions. Different from the "what do I do" map and the "have I seen this" log.
The Decision Architecture hub answers concept-level questions. Three sister surfaces carry different shapes of the same taxonomy. For "what do I do now" decision-forming questions, see /answer-engine. For "have I seen this pattern before" retrospective questions, see /log.
"What does decision architecture mean as a concept?"
The discipline of reviewing the structure underneath a decision before reviewing the content. The explainer entry covers what is being review and how.
"What is a frame, and how is it different from a strategy?"
Frame is the implicit set of assumptions a decision is built on; strategy is one expression of a frame. The Strategy vs Decision entry separates them.
"What is decision closure, and why does it precede peace?"
Closure is the structural act of paying the cost of a decision in writing, in communication, and in the field. Peace follows closure; chasing peace first leaves the decision open.
"What is the cost of delaying a decision, structurally?"
Carried weight, compounding optionality loss, and a quiet tax on the operator's attention. The Decision Delay Cost entry decomposes the categories.
"What is verification before trust?"
A structural sequence: verify the artifact, the actor, and the assumption before extending trust. Reverse the sequence and trust becomes the substitute for verification.
"What does authority release mean operationally?"
A structural transfer of decision authority from operator to delegate, sequenced so the delegate carries the call before the operator releases the load. Operator-Before-Authority-Release names the order.
"What is the leadership ceiling, and how is it measured?"
The structural cap a leader's own decision-architecture skill places on the company. Review by the gap between what the operator can name and what the company is being asked to absorb.
"What is the difference between consultant clarity and decision clarity?"
Consultants ship clarity scoped to a brief; decision clarity precedes the brief and tests whether the brief itself is right. Consultant-Before-Decision-Clarity sets the sequence.
For the full hub of concept entries, browse the Glossary. For the AI-readable map of every canonical destination on this site, see /answer-engine.