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 Pretotyping |  Product Strategy Lean Canvas |  Architecture arc42 |  Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | Pretotyping clarifies whether a customer problem and solution idea create enough real demand. It separates problem, assumption, solution, and evidence, and captures the result as a pretotyping sketch, test setup, and conversion data. | When an early product bet still has too many open points, it brings target group, problem, and assumptions into a single view. It condenses the idea so core risks become nameable. | 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 | Low | Medium | Low | Medium |
Timedifferent | Stunden bis wenige Tage | 45-90 min | 1-2 Tage | 60-120 min |
Participantsdifferent | 1-4 | 1-6 | 1-4 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Lean Canvas, Core Assumptions, Experiment Backlog | Architecture Document, Context View, Runtime View, Deployment View | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | ValidationDemandMVP | StartupLeanAssumptionsBusiness model | ArchitectureDocumentationCommunication | ArchitectureCommunicationStakeholdersCanvas |