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 |  Business Strategy GAP Analysis |  Operations Weekly Review |  Operations Getting Things Done |
|---|---|---|---|---|
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. | GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing. | In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable. | 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. |
Complexitydifferent | Medium | Medium | Low | Medium |
Timedifferent | Ongoing | 1-3 h | 30-60 min | 1-2 h Setup, laufend |
Participantsdifferent | 2-12 | 2-8 | 1 | 1 |
Formatdifferent | Workshop + async | Workshop + async | Async | Async |
Outputdifferent | Kanban board, WIP policies, Flow metrics | Gap Matrix, Action Plan, Risk Notes | Updated Task System, Weekly Focus, Next Actions | Action Lists, Project List, Review Routine |
Tagsno overlap | FlowVisual managementDelivery | StrategyAnalysisPlanning | ProductivityExecutionPlanning | ProductivityPlanningTasksExecution |