Complete firstIncident datanot in catalog
Symptoms, relevant time windows, logs, alerts, or observations exist in raw form.
Without: With an unclear scope, the team collects material but cannot derive a robust structure or decision.
RunsheetEngineering
Hypothesis-Driven Troubleshooting
ComplexityMedium
Time30-240 min
Participants1-6
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 a Hypothesis Log; available notes, data, decisions, and assumptions; markers for uncertainty, owner, and next steps.
People / roles
A facilitator; technical experts from the affected area; one owner for outcome and follow-up; a named decider when decisions are required.
Pre-read
Scope, trigger event, known facts, relevant constraints, existing options or incidents, and the desired meeting outcome.
Time needed
60-180 min
Setup
Prepare an empty template for the Hypothesis Log. Make scope and working question visible at the top. Mark each assumption as an assumption, not as a fact.
03
Core question
The one question this method answers
Which hypothesis best explains the symptom, and which test delivers the highest information value?
04
Flow
Marker: Phase
| Step | Duration | Action | Hint |
|---|---|---|---|
1Fix the scope | 10-20 min | Define the trigger event, objective, and boundaries of analysis. Collect off-scope topics in a parking lot. | A narrow scope produces better outcomes than a full but diffuse sweep. |
2Collect raw material | 20-40 min | Gather facts, events, options, constraints, and assumptions and make them visible. | Keep facts and interpretations separate. Mark uncertain points rather than smoothing them over. |
3Build the structure | 30-60 min | Fill the Hypothesis Log step by step, clarify relationships between elements, and make contradictions visible. | Do not evaluate too early. First stabilize the structure, then draw conclusions. |
4Check and compress | 20-40 min | Mark gaps, weak assumptions, counterexamples, and critical paths. Check the result for clarity. | If no one can explain the logic in two minutes, the artifact is not complete yet. |
5Define next steps | 15-20 min | Document decision, experiment, test, measure, or follow-up with owner and date. | A strong artifact without next action remains knowledge work without impact. |
05
Artifact
What comes out at the end
Form
Hypothesis Log with trigger, scope, key elements, assumptions, marked gaps, outcome interpretation, and next step with owner and date.
Versioning / ownership
Store artifact with date, scope, and participants. For new evidence create a new version or change note so decision logic remains traceable.
Tool alternatives
- Miro or FigJam
- Lucidchart or draw.io
- Confluence or Notion
- Google Docs or Sheets
- Markdown in repository
hypothesis-driven-troubleshooting-working-template.md
Compact working template for Hypothesis-Driven Troubleshooting with context, input, output artifacts, and next step.
Hypothesis-Driven Troubleshooting Working Template
Goal
Troubleshooting approach that turns symptoms into testable hypotheses and focused tests.
Context
When and for what do we use this method?
Input
Which data, observations, decisions, or materials are available?
Execution
Short notes along the runsheet.
Output artifacts
- Hypothesis Log:
- Test Plan:
- Evidence Notes:
- Diagnosis Summary:
Assumptions and open questions
- ...
Decision / Next step
Owner, date, and success signal.
06
Example output
Concrete filled scenario, fictional example
hypothesis-driven-troubleshooting-beispiel.md
Concrete filled scenario, fictional example
Hypothesis-Driven Troubleshooting - Slow reports after release
Scope: A specific project area is considered, not the entire company. Working question: Which hypothesis best explains the symptom, and which test delivers the highest information value?
Excerpt from the 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 unresolved condition determines whether the preferred direction is viable.
Result: Team selects a focused next step with owner and date. Signal: Shift from trial-and-error toward directed learning.
07
Pitfalls
Recognize symptoms and steer against them
Trap
Scope drift
Symptom
New topics are repeatedly added and the artifact loses focus.
What to do
Keep scope visible and park new topics as separate follow-up topics.
Trap
Assumptions treated as facts
Symptom
The discussion sounds certain even though evidence is missing.
What to do
Mark every uncertain statement and set a verification checkpoint.
Trap
Premature solutioning
Symptom
Team jumps to actions after only a few minutes.
What to do
Build the structure fully first, then derive options or actions.
Trap
No counter-check
Symptom
The artifact only confirms the favorite hypothesis.
What to do
Ask explicitly for counterexamples, negative branches, or rejected options.
Trap
No owner
Symptom
Result is understandable but no one continues with it.
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 not clear.
There is no raw material or no participants with contextual knowledge.
The method is used to justify a decision already made.
Important assumptions cannot be discussed openly.
No owner is available for outcome 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.