View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Innovation Lean Startup |  Product Discovery Pretotyping |  Architecture Architecture Communication Canvas |  Architecture arc42 |
|---|---|---|---|---|
Purposedifferent | For uncertain business assumptions, the method forces the idea into contact with real market reactions early. It separates wishful picture, assumption, and observable behavior, so that learning becomes faster than planning. This translates uncertainty into measurable insight. | 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. | 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 | Medium | Low | Medium | Low |
Timedifferent | Wochen bis Monate je Lernzyklus | Stunden bis wenige Tage | 60-120 min | 1-2 Tage |
Participantsdifferent | 2-8 | 1-4 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | LeanStartupValidationMVP | ValidationDemandMVP | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |