View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Product Discovery Outcome-Driven Innovation |  Architecture Architecture Decision Record |  Operations MORT Analysis |  Operations Family Tree Analysis |
|---|---|---|---|---|
Purposedifferent | Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs. | 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. | For a safety-relevant event or a system with high protection requirements, the method examines where controls failed. It exposes both technical and organizational gaps. | For a series of incidents with a similar pattern, the method arranges individual events as branches of a common origin. It makes visible which conditions keep recurring. |
Complexitydifferent | High | Low | High | Medium |
Timedifferent | Mehrere Wochen | 15-45 min | Mehrere Tage bis Wochen | 2-4 h |
Participantsdifferent | 2-6 researchers plus sample | 1-3 | 2-6 | 2-6 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | ADR File, Decision Log, Rationale | MORT Worksheets, Findings per Branch, Corrective Actions, Systemic Recommendations | Family Tree Diagram, Pattern Notes, Systemic Measures |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureRationaleDocumentationGovernance | Root causeSafetySystemicIncident | Root causePatternsIncidentSystemic |