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 Risk Storming | ![]() Business Strategy Value Chain Analysis | ![]() Product Strategy Lean Canvas |
|---|---|---|---|
Purposedifferent | Helps clarify architecture context, options, and consequences in concrete terms. It organizes technical context, alternatives, and consequences. The result is captured as an Annotated Diagram, a Prioritized Risk List, and an Action Backlog. | Value Chain Analysis shows where value is created, costs accrue, and differentiation becomes possible along the process. It compares strengths, risks, market logic, and courses of action. The result is captured as a value-chain map and lever list. | 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 | High | Medium |
Timedifferent | 60-90 min | Half day | 45-90 min |
Participantsdifferent | 4-12 | 3-8 | 1-6 |
Formatdifferent | Workshop | Workshop | Workshop + async |
Outputdifferent | Annotated Diagram, Prioritized Risk List, Action Backlog | Value Chain Map, Lever List | Lean Canvas, Core Assumptions, Experiment Backlog |
Tagsno overlap | RiskArchitectureWorkshopValidation | StrategyBusiness modelDiagnosisAnalysis | StartupLeanAssumptionsBusiness model |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.






