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 A3 Problem Solving |  DevOps Blameless Postmortem |  Delivery Value Stream Mapping |
|---|---|---|---|---|
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. | 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. | After an incident with damage or a near miss, the method creates a sober field for learning without assigning blame. It directs attention to the course of events, conditions, and effective countermeasures. | When delivery work dissolves into wait times, handoffs, and hidden effort, Value Stream Mapping makes the actual flow visible. The method exposes bottlenecks, idle time, and feedback loops so lead time and improvement levers become tangible. |
Complexitysame | Medium | Medium | Medium | Medium |
Timedifferent | Ongoing | 45-90 min | 30-90 min | 1-3 h |
Participantsdifferent | 2-12 | 2-5 | 3-12 | 4-10 |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Workshop |
Outputdifferent | Kanban board, WIP policies, Flow metrics | A3 Report, Action Plan, Root Cause Analysis | Postmortem Doc, Action Items, Timeline | Current-state map, Future-state map, Bottleneck list |
Tagsno overlap | FlowVisual managementDelivery | LeanProblem solvingCoachingOperations | Site Reliability EngineeringIncidentLearningReliability | LeanFlowWasteDelivery |