View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Engineering Kanban |  Facilitation Alignment Mapping |  Architecture Software Architecture Canvas |
|---|---|---|---|
Purposedifferent | When work sits in too many parallel streams, throughput suffers and no one sees the bottlenecks. Kanban makes the flow of work visible and limits overload so a system becomes calmer and more predictable. | 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 | Medium | Low |
Timedifferent | Ongoing | 1-2 h | 1-2 h |
Participantsdifferent | 2-12 | 4-12 | 3-10 |
Formatdifferent | Workshop + async | Workshop | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Alignment Map, Open Issues, Decision Questions | Architecture Canvas, Goals, Constraints, Quality Attributes |
Tagsno overlap | FlowVisual managementDelivery | AlignmentStakeholdersStrategyFacilitation | CanvasArchitectureAlignmentWorkshop |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
