View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Operations A3 Problem Solving |  Operations Visual Management |  Engineering Kanban |
|---|---|---|---|
Purposedifferent | For a complex deviation with several people involved, the method bundles problem, analysis, and decision onto one page. It creates a shared working space where causes, countermeasures, and follow-up fit together. | With high tempo and many parallel topics, the method makes status, deviations, and priorities visible at a glance. It reduces search effort and prevents what matters from getting lost in daily work. | 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. |
Complexitydifferent | Medium | Low | Medium |
Timedifferent | 45-90 min | Ongoing | Ongoing |
Participantsdifferent | 2-5 | 1-20 | 2-12 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Visual Board, Status Indicators, Exception Cues | Kanban board, WIP policies, Flow metrics |
Tagsno overlap | LeanProblem solvingCoachingOperations | SignalsOperationsVisual management | FlowVisual managementDelivery |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
