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 Dual-Track Agile | ![]() Business Strategy GAP Analysis | ![]() Architecture Software Architecture Canvas | ![]() Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When uncertainty and delivery run in parallel, it separates learning work from implementation while keeping both connected. It prevents unvalidated ideas from falling directly into the delivery stream. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | 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. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Laufend, Wochen bis Monate | 1-3 h | 1-2 h | 1-2 h |
Participantsdifferent | 4-10 | 2-8 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Discovery Backlog, Delivery Backlog, Experiment-Ergebnisse, Validierte Stories | Gap Matrix, Action Plan, Risk Notes | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | AgileDiscoveryDelivery | StrategyAnalysisPlanning | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation |



