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 |  Operations Root Cause Analysis |  Architecture arc42 |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | When a problem keeps recurring and the cause stays unclear, the method exposes the underlying mechanism. It separates symptom, guess, and robust explanation from one another. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | High | Medium | Low | Medium |
Timedifferent | Mehrere Wochen | 1-4 h | 1-2 Tage | 60-120 min |
Participantsdifferent | 2-6 researchers plus sample | 3-8 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | Problem Statement, Cause Hypotheses, Confirmed Causes, Action Plan | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | OutcomesInnovationResearchQuantitative | Root causeProblem solvingQualityIncident | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |