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 A3 Problem Solving | ![]() Architecture Architecture Communication Canvas | ![]() 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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Medium | Medium | Low |
Timedifferent | Mehrere Wochen | 45-90 min | 60-120 min | 1-2 Tage |
Participantsdifferent | 2-6 researchers plus sample | 2-5 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses | A3 Report, Action Plan, Root Cause Analysis | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | OutcomesInnovationResearchQuantitative | LeanProblem solvingCoachingOperations | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |



