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 |  Decision Making Constraint Analysis |  Architecture Architecture Communication 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 an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | Ongoing | 30-90 min | 60-120 min |
Participantsdifferent | 2-12 | 2-8 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Constraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | FlowVisual managementDelivery | ConstraintsDecisionPlanningOptions | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
