View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery Communication Plan |  Engineering Kanban |  Architecture Software Architecture Canvas |  Facilitation Alignment Mapping |
|---|---|---|---|---|
Purposedifferent | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. | 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 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 | Low | Medium | Low | Medium |
Timedifferent | 45-90 min | Ongoing | 1-2 h | 1-2 h |
Participantsdifferent | 2-6 | 2-12 | 3-10 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop |
Outputdifferent | Communication Plan, Channel Matrix, Message Cadence | Kanban board, WIP policies, Flow metrics | Architecture Canvas, Goals, Constraints, Quality Attributes | Alignment Map, Open Issues, Decision Questions |
Tagsno overlap | CommunicationStakeholdersDeliveryPlanning | FlowVisual managementDelivery | CanvasArchitectureAlignmentWorkshop | AlignmentStakeholdersStrategyFacilitation |