What needs to be finished first
The problem, goal, or decision is described clearly enough for the method to be applied within a clear scope.
What needs to be ready before start
Workboard or document for Option Frames; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.
Facilitator; domain experts from the affected area; an owner for outcomes and follow-up; for decisions, a named decider.
Scope, trigger, known facts, relevant constraints, existing options or events, and expected workshop outcome.
60-120 min
Prepare an empty Option Frames template. Keep scope and working question at the top. Mark every assumption as an assumption, not as fact.
The one question this method answers
Which actions options are truly comparable, complete, and decision-ready?
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Fix the scope | 10-20 min | Define the occasion, objective, and boundaries under consideration. Collect off-scope topics on a parking lot. | A tight scope produces better results than a complete but diffuse broad overview. |
2Collect rough input | 20-40 min | Gather facts, events, options, constraints, or assumptions and make them visible. | Keep facts and interpretations separate. Mark uncertain points instead of smoothing them out. |
3Build the structure | 30-60 min | Fill Option Frames step by step, clarify relationships between elements, and surface contradictions. | Do not evaluate too early. Stabilize structure first, then draw conclusions. |
4Check and consolidate | 20-40 min | Mark gaps, weak assumptions, counterexamples, and critical paths. Validate output for clarity. | If nobody can explain the logic in two minutes, the artifact is not finished. |
5Define next steps | 15-20 min | Document decision, experiment, test, action, or follow-up with owner and date. | A good artifact without a next action stays as knowledge work without impact. |
What comes out at the end
Option Frames with trigger, scope, core elements, assumptions, flagged gaps, result interpretation, and next step with owner and date.
Save artifact with date, scope, and participants. On new evidence, create a new version or change note so decision logic remains traceable.
Standardized description of action options so they can be compared fairly.
What is the option in one sentence?
What is included, and what is explicitly excluded?
Which goal does this option support?
Which resources, duration, and dependencies does it create?
Which negative consequences or open points remain?
Which prerequisites need to be true?
How do we know this option should be preferred?
Concrete filled scenario, fictional example
Concrete filled scenario, fictional example
Scope: Review one concrete project area, not the whole company. Working question: Which options are truly comparable, complete, and decision-ready?
Excerpt from artifact:
Result: The team chooses a focused next step with owner and date. Signal: Move from rough ideas to decision-ready options.
Recognize symptoms and steer against them
New topics keep getting added and the artifact loses focus.
Keep scope visible and move new topics to the parking lot.
Discussion sounds certain even though evidence is missing.
Mark every uncertain statement and define a check point.
Team starts moving to actions after only a few minutes.
Complete the structure first, then derive options or actions.
Artifact confirms only the favorite hypothesis.
Ask explicitly for counterexamples, negative branches, or excluded options.
Result is understandable, but no one follows it through.
Document every next step with owner, date, and success signal.
Done signals checkable in under a minute
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.