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 Process Mapping |  Operations Gemba Walk |  Architecture Software Architecture Canvas |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | With a confusing workflow that has many handoffs, the method makes the actual process visible. It shows where work is passed on, delayed, or duplicated, so improvement targets the right spots. | When there is uncertainty about the real course of a process, the method brings observation to the place where work happens. It combines perception, follow-up questions, and process knowledge so decisions rest on actual workflows instead of assumptions. | The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly. | After missions or project phases with unclear outcomes, the method makes visible what actually happened and what can be learned from it. It separates course, effect, and causes so experience turns into solid improvement. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 1-3 h | 30-120 min | 1-2 h | 20-45 min |
Participantsdifferent | 3-10 | 2-6 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Observation Notes, Improvement Ideas | Architecture Canvas, Goals, Constraints, Quality Attributes | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | LeanObservationProcessOperations | CanvasArchitectureAlignmentWorkshop | LearningOperationsImprovement |