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 |  Architecture arc42 |
|---|---|---|---|---|
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. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | High | Low | High | Low |
Timedifferent | Mehrere Wochen | 15-45 min | Mehrere Tage bis Wochen | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 1-3 | 2-6 | 1-4 |
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 | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureRationaleDocumentationGovernance | Root causeSafetySystemicIncident | ArchitectureDocumentationCommunication |