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 |  Operations Getting Things Done |  Architecture Architecture Communication Canvas |  Architecture arc42 |
|---|---|---|---|---|
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. | With many open commitments and ideas in daily life, a reliable external storage system emerges. The method relieves the mind so priority and context don't have to compete in memory. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. |
Complexitydifferent | Medium | Medium | Medium | Low |
Timedifferent | Ongoing | 1-2 h Setup, laufend | 60-120 min | 1-2 Tage |
Participantsdifferent | 2-12 | 1 | 2-8 | 1-4 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop + async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Action Lists, Project List, Review Routine | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Architecture Document, Context View, Runtime View, Deployment View |
Tagsno overlap | FlowVisual managementDelivery | ProductivityPlanningTasksExecution | ArchitectureCommunicationStakeholdersCanvas | ArchitectureDocumentationCommunication |