STEP 1 — Understand the problem
First, focus on the observed symptom and context before discussing solutions.
A tool for locating organizational power and potential veto power around architecture decisions.
Helps when power, concern and veto potential shape the course of a decision.
These steps lead from observing a symptom to a grounded intervention.
Describe the symptom
Collect observations
Formulate hypotheses
Analyze system dynamics
Derive interventions
First, focus on the observed symptom and context before discussing solutions.
Move from individual observations to the deeper dynamics, boundaries, and roles involved.
Now derive measures that address structure, rules or information flows.
This checklist is not a second form. It is a completeness check. If something is missing, add the information in the text fields above.
Use the export functions for workshop documentation and jump directly into related archetypes or interventions when diagnosis turns into action.