Complete firstDecision Framing Workshop
Problem, goal, or decision is described enough that the method can be applied to a clear scope.
Without: Without clear scope, the team collects material but cannot derive a reliable structure or decision.
RunsheetDecision Making
Trade-off Analysis
ComplexityMedium
Time45-120 min
Participants2-8
FormatWorkshop + async
MaturityEstablished
01
Prerequisite
What needs to be finished first
02
Preparation
What needs to be ready before start
Materials
Working board or document for trade-off matrix; existing notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.
People / roles
Facilitator; domain experts from the affected area; one owner for result and follow-up; named decider for decisions.
Pre-read
Scope, trigger, known facts, relevant constraints, previous options or events, and desired result of the session.
Time needed
60-120 min
Setup
Prepare an empty trade-off matrix template. Make scope and working question visible at the top. Mark every assumption as assumption, not as fact.
03
Core question
The one question this method answers
Which option accepts which disadvantages, and which compromise best fits the decision criteria?
04
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Fix scope | 10-20 min | Define trigger, goal, and boundaries of the view. Collect non-fitting topics in a parking lot. | A narrow scope creates better results than a complete but diffuse sweep. |
2Collect raw material | 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 over. |
3Build structure | 30-60 min | Fill the trade-off matrix step by step, clarify relationships between elements, and make contradictions visible. | Do not evaluate too early. Stabilize structure first, then draw conclusions. |
4Check and condense | 20-40 min | Mark gaps, weak assumptions, counterexamples, and critical paths. Check result for comprehensibility. | If nobody can explain the logic in two minutes, the artifact is not finished. |
5Define next steps | 15-20 min | Document decision, experiment, test, measure, or follow-up with owner and date. | A good artifact without next action remains knowledge work without effect. |
05
Artifact
What comes out at the end
Form
Trade-off matrix with trigger, scope, central elements, assumptions, marked gaps, result interpretation, and next step with owner and date.
Versioning / ownership
Store artifact with date, scope, and participants. On new evidence, create a new version or change note so decision logic stays traceable.
Tool alternatives
- Miro or FigJam
- Lucidchart or draw.io
- Confluence or Notion
- Google Docs or Sheets
- Markdown in the repository
trade-off-matrix-markdown.md
Markdown matrix for comparing options across competing criteria and accepted trade-offs.
Trade-off Matrix: Decision
| Criterion | Weight | Option A | Option B | Option C |
|---|---|---|---|---|
| Benefit | 30 | |||
| Cost | 20 | |||
| Risk | 20 | |||
| Time-to-Learn | 15 | |||
| Reversibility | 15 |
Accepted trade-offs
- Option A accepts:
- Option B accepts:
- Option C accepts:
Recommendation
Which option is recommended and why?
Sensitivity
Which small change in weighting or assumption would flip the recommendation?
06
Example output
Concrete filled scenario, fictional example
trade-off-analysis-beispiel.md
Concrete filled scenario, fictional example
Trade-off Analysis - Build vs. Buy for Billing
Scope: One concrete project area is reviewed, not the entire company. Working question: Which option accepts which disadvantages, and which compromise best fits the decision criteria?
Excerpt from artifact:
- Fact 1: Current observation is documented and sourced.
- Assumption 1: The most important causal relationship is plausible but not yet proven.
- Critical point: One open condition determines whether the preferred direction is viable.
Result: The team chooses a focused next step with owner and date. Signal: From options to accepted disadvantages.
07
Pitfalls
Recognize symptoms and steer against them
Trap
Scope drifts
Symptom
More and more topics are added and the artifact loses focus.
What to do
Keep scope visible and move new topics to the parking lot.
Trap
Assumptions become facts
Symptom
Discussion sounds certain although evidence is missing.
What to do
Mark every uncertain statement and define a check point.
Trap
Solution too early
Symptom
Team jumps into measures after a few minutes.
What to do
Complete the structure first, then derive options or measures.
Trap
No countercheck
Symptom
Artifact only confirms the favorite hypothesis.
What to do
Explicitly ask for counterexamples, negative branches, or excluded options.
Trap
No owner
Symptom
Result is understandable, but nobody follows it up.
What to do
Always document the next step with owner, date, and success signal.
08
Stop criteria
Done signals checkable in under a minute
Trigger or scope is unclear.
There is no raw material or no participants with context knowledge.
Method is used to legitimize an already made decision.
Important assumptions may not be discussed openly.
No owner available for result or follow-up.
Finished the runsheet?
Go to the profile for purpose, similar methods, and sources or continue to the next method in the catalog.