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 |  Architecture Architecture Communication Canvas |  Facilitation Alignment Mapping |
|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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. |
Complexitysame | Medium | Medium | Medium |
Timedifferent | Ongoing | 60-120 min | 1-2 h |
Participantsdifferent | 2-12 | 2-8 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | FlowVisual managementDelivery | ArchitectureCommunicationStakeholdersCanvas | AlignmentStakeholdersStrategyFacilitation |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
