View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Value Stream MappingArchitecture Inception CanvasAlignment MappingSoftware Architecture Canvas
| Criterion | ![]() Delivery Value Stream Mapping | ![]() Architecture Architecture Inception Canvas | ![]() Facilitation Alignment Mapping | ![]() Architecture Software Architecture Canvas |
|---|---|---|---|---|
Purposedifferent | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. |
Complexitydifferent | Medium | Low | Medium | Low |
Timedifferent | 1-3 h | 1-2 h | 1-2 h | 1-2 h |
Participantsdifferent | 4-10 | 3-8 | 4-12 | 3-10 |
Formatsame | Workshop | Workshop | Workshop | Workshop |
Outputdifferent | Current-state map, Future-state map, Bottleneck list | Inception Canvas, Risks, Goal List, Open Questions | Alignment Map, Open Issues, Decision Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | LeanFlowWasteDelivery | AlignmentArchitectureCanvas | AlignmentStakeholdersStrategyFacilitation | CanvasArchitectureAlignmentWorkshop |



