01
Teams document processes without distinguishing tasks from judgments.
practice · Decision Design knowledge system
Decision Design Practice
Decision Design practice converts ambiguous judgment flows into explicit authority maps, boundaries, escalation rules, Decision Logs, and reviewable operating artifacts.
Why this topic matters
Principles such as human oversight and accountability only change outcomes when teams can locate decision points, allocate authority, encode exceptions, and preserve evidence in daily operations.
Problem structure
02
Authority is assigned by title rather than by decision, condition, and mandate.
03
Escalation, override, and records are designed after incidents instead of before deployment.
Core concepts
The practice starts with Judgment Architecture, operationalizes it through Decision Boundaries, and keeps it accountable through Decision Logs and periodic boundary review.
Judgment Architecture
Judgment Architecture is the institutional arrangement through which judgment authority is allocated, exercised, transferred, recorded, and reviewed.
Decision Boundary
A Decision Boundary is an authority structure that specifies where delegated judgment ends and another legitimate authority must decide.
Decision Logs
Decision Logs are accountability infrastructure connecting judgment, authority, evidence, execution, and outcome across a decision lifecycle.
Featured analysis and guidance
AI Agents Don't Eliminate Decisions
How agent workflows expose missing decision ownership and auditability.
After Risk Mapping, What Gets Designed?
A practical bridge from risk identification to authority design.
Can Japan's Government Turn AI Into Delivery Power?
A public-sector example of proposal, review, and final authority.