View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Hypothesis-Driven Troubleshooting |  Architecture Software Architecture Canvas |  Facilitation Decision Jam |  Facilitation Alignment Mapping |
|---|---|---|---|---|
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. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | 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. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 30-240 min | 1-2 h | 60-90 min | 1-2 h |
Participantsdifferent | 1-6 | 3-10 | 4-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop |
Outputdifferent | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | Architecture Canvas, Goals, Constraints, Quality Attributes | Problem Cluster, Prioritized Challenge, Experiment | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | TroubleshootingProblem solvingDiagnosis | CanvasArchitectureAlignmentWorkshop | FacilitationDecisionProblem solvingWorkshop | AlignmentStakeholdersStrategyFacilitation |