methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Hypothesis-Driven Troubleshooting.
Engineering
Hypothesis-Driven Troubleshooting
Paper illustration of an assumption matrix with prioritized test cards
Decision Making
Assumption Surfacing
Paper illustration for Concierge MVP
Product Discovery
Concierge MVP
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
Purposedifferent
When systems fail unexpectedly, spontaneous attempts often produce more noise than insight. Hypothesis-driven Troubleshooting translates symptoms into testable assumptions and makes troubleshooting learnable.Plans often contain assumptions that were never openly stated and remain dangerous precisely because of that. Assumption Surfacing makes these silent premises visible and prioritizes which of them carry the initiative or could sink it.When an idea can first fail or grow through genuine hands-on support, it relies on manual work instead of automation. It shows whether user value holds up even under manual execution.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.
Complexitydifferent
MediumLowMediumLow
Timedifferent
30-240 min45-90 min1-4 Wochen60-90 min
Participantsdifferent
1-62-83-10 Kunden4-10
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Hypothesis Log, Test Plan, Evidence Notes, Diagnosis SummaryAssumption List, Critical Assumptions, Learning PlanConcierge Learnings, Service Blueprint, MVP RisksProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
TroubleshootingProblem solvingDiagnosis
AssumptionsRiskDecisionDiscovery
MVPValidationServiceDiscovery
FacilitationDecisionProblem solvingWorkshop
Add more methods