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 |  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. | 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. | 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 | Low | Low | Medium |
Timedifferent | Mehrere Wochen | 1-2 Tage | 15-30 min | 60-120 min |
Participantsdifferent | 2-6 researchers plus sample | 1-4 | 2-6 | 2-8 |
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 | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | OutcomesInnovationResearchQuantitative | ArchitectureDocumentationCommunication | Root causeIncidentLeanProblem solving | ArchitectureCommunicationStakeholdersCanvas |