View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Engineering Hypothesis-Driven Troubleshooting | ![]() Business Strategy 5-Minuten VC-Check |
|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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 5-Minute VC Check clarifies opportunities and strategic options at the earliest idea stage. It compares problem quality, customer willingness to pay, alternatives, differentiation, and market potential, and captures the result as a VC-check note, go/sharpen/park decision, and risk list. |
Complexitydifferent | Low | Medium | Low |
Timedifferent | 15-45 min | 30-240 min | 5-15 min |
Participantsdifferent | 1-3 | 1-6 | 1-5 |
Formatdifferent | Async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis Log, Test Plan, Evidence Notes, Diagnosis Summary | VC-check note, Go/sharpen/park decision, Risk and assumption list, Next validation step |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | TroubleshootingProblem solvingDiagnosis | StartupValidationCompetition |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






