Loading content
Decision Boards are visual tools for systematically capturing, prioritizing, and tracking organizational decisions. They structure options, responsibilities, and evaluation criteria on a shared board. The concept increases transparency, repeatability and traceability of decisions across product and architecture domains. Suitable for teams and domains.
Use this profile to understand the building block briefly, place it in the model, and switch to the 360° assessment when needed.
Theoretical construct: explains a term, principle, or mental model.
What you need to understand to reason about a domain.
Decision Boards are visual boards where teams capture, prioritize, and track organizational decisions together.
The concept sits within decision research, group decision making, and multiple-criteria decision analysis. It responds to a familiar problem of bounded attention and distributed information: when alternatives, criteria, and dependencies are scattered across meetings, emails, or tickets, comparisons become hard to make. A shared board makes options, owners, and reasons visible and keeps decisions traceable.
Think of a Decision Board as a decision flow with fixed fields: options on the left, then criteria, risks, and open questions; status, owners, and next steps on the right. The board pushes the team to surface implicit assumptions, bind decisions to criteria, and keep the path from “proposed” to “decided” visible.
Several possible courses of action are laid out side by side so they can be compared.
Defined measures explain why one option fits better than another.
Responsibilities show who prepares, approves, or implements a decision.
The decision, its rationale, and follow-up actions remain findable and reviewable in one place.
Cognitive and informational limits make external structure necessary so decisions do not rely only on memory or room dynamics.
Decision Boards are useful in architecture and product decisions when multiple stakeholders, repeated trade-offs, or high downstream costs call for transparency. They are especially helpful before approvals, in governance forums, or for complex trade-offs. Their value depends on using criteria consistently and keeping entries current; otherwise the board degrades into a visible to-do list.
Where this building block is located in the topic model.
Explore how this building block connects to concepts, methods, technologies, and tools.
These sources establish the term and its professional meaning.
All direct connections of the current building block in a compact text view.
This classification shows where the building block typically matters, how demanding it is, and what kind of impact it has in the model.
The level within the organization (enterprise, domain, team) at which the AssetBlock is applied.