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 arc42 |  Operations 5 Whys |  Operations A3 Problem Solving |
|---|---|---|---|---|
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. | 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. | For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description. | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Mehrere Wochen | 1-2 Tage | 15-30 min | 45-90 min |
Participantsdifferent | 2-6 researchers plus sample | 1-4 | 2-6 | 2-5 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Architecture Document, Context View, Runtime View, Deployment View | Root cause notes, Countermeasures | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving | LeanProblem solvingCoachingOperations |