Problem, goal, or decision is described clearly enough to apply the method to a defined scope.
Decision Framing Workshop
Prerequisite
What needs to be finished first
Preparation
What needs to be ready before start
Working board or document for Decision Frame; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.
Facilitator; subject-matter experts from the affected area; an owner for outcome and follow-up; for decisions, a named decider.
Scope, purpose, known facts, relevant constraints, existing options or events, and expected meeting outcome.
60-120 min
Prepare empty Decision Frame template. Make scope and working question visible at the top. Mark each assumption as assumption, never as fact.
Core question
The one question this method answers
Is everyone discussing the same decision with the same options, criteria, and roles?
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Fix scope | 10-20 min | Define purpose, objective, and boundaries. Collect out-of-scope topics on a parking lot. | A narrow scope produces better results than a broad but diffuse sweep. |
2Collect raw material | 20-40 min | Gather and surface facts, events, options, constraints, and assumptions. | Keep facts and interpretations separate. Mark uncertainty instead of smoothing over it. |
3Build structure | 30-60 min | Fill the Decision Frame step by step, clarify relationships between elements, and expose contradictions. | Do not evaluate too early. Stabilize structure first, then draw conclusions. |
4Review and refine | 20-40 min | Mark gaps, weak assumptions, counterexamples, and critical paths. Check outcome for clarity. | If nobody can explain the logic in two minutes, the artifact is not ready yet. |
5Define next steps | 15-20 min | Document decision, experiment, test, action, or follow-up with owner and date. | A strong artifact without next action becomes knowledge work without impact. |
Artifact
What comes out at the end
Decision Frame with purpose, scope, core elements, assumptions, marked gaps, interpretation of the outcome, and next step with owner and date.
Save artifact with date, scope, and participants. For new evidence, create new version or add change note so decision logic stays traceable.
- Miro or FigJam
- Lucidchart or draw.io
- Confluence or Notion
- Google Docs or Sheets
- Markdown in repository
decision-frame-markdown.md
Template for turning an unclear decision into a question, roles, options, and evidence needs.
Decision Frame: Topic
Decision question
What decision needs to be made now?
Context
Why is the decision needed, what happens without it?
Decider and roles
- Decider:
- Input:
- Reviewer:
- Informed:
Options
- ...
- ...
- ...
Criteria
- ...
Constraints
- ...
Evidence needed
What data, tests, or reviews are still missing?
Next step
Owner, date, format.
Example output
Concrete filled scenario, fictional example
decision-framing-workshop-beispiel.md
Concrete filled scenario, fictional example
Decision Framing Workshop - Platform mandate for Q3
Scope: A specific project area is considered, not the entire company. Core question: Is everyone discussing the same decision with the same options, criteria, and roles?
Artifact excerpt:
- Fact 1: Current observation is documented with source.
- Assumption 1: The most important causal relationship is plausible but not yet proven.
- Critical point: One open condition decides whether the preferred direction is viable.
Outcome: Team selects a focused next step with owner and date. Signal: Movement from diffuse debate to a clear decision frame.
Pitfalls
Recognize symptoms and steer against them
Scope drift
New topics are added continuously and the artifact loses focus.
Keep scope visible and park new topics.
Assumptions become facts
Discussion sounds certain, although evidence is missing.
Mark every uncertain statement and define a check.
Premature solution
Team moves to actions after only a few minutes.
First complete the structure, then derive options or actions.
No counter-check
Artifact confirms only a preferred hypothesis.
Explicitly ask for counterexamples, negative branches, or excluded options.
No owner
Result is understandable, but no one advances it further.
Always document next step with owner, date, and success signal.
Stop criteria
Done signals checkable in under a minute
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.