View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture Architecture Decision Record | ![]() Innovation Lean Startup | ![]() Architecture C4 Model | ![]() Product Strategy Lean Canvas |
|---|---|---|---|---|
Purposedifferent | An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable. | 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. | 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. | 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. |
Complexitydifferent | Low | Medium | Low | Medium |
Timedifferent | 15-45 min | Wochen bis Monate je Lernzyklus | 1-4 h | 45-90 min |
Participantsdifferent | 1-3 | 2-8 | 1-5 | 1-6 |
Formatdifferent | Async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | ADR File, Decision Log, Rationale | Hypothesis list, MVPs, Learning reports, Pivot or persevere decision | Context Diagram, Container Diagram, Component Diagram | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | ArchitectureRationaleDocumentationGovernance | LeanStartupValidationMVP | ArchitectureCommunicationVisualization | StartupLeanAssumptionsBusiness model |



