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 |  Architecture C4 Model |  Innovation Lean Startup |  Architecture arc42 |
|---|---|---|---|---|
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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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 | Low | Low | Medium | Low |
Timedifferent | Stunden bis wenige Tage | 1-4 h | Wochen bis Monate je Lernzyklus | 1-2 Tage |
Participantsdifferent | 1-4 | 1-5 | 2-8 | 1-4 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Pretotyping sketch, Test setup, Conversion data, Go or no-go decision | Context Diagram, Container Diagram, Component Diagram | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | ValidationDemandMVP | ArchitectureCommunicationVisualization | LeanStartupValidationMVP | ArchitectureDocumentationCommunication |