View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Business Strategy Strategy Execution Loop |  Operations Gemba Walk |  Architecture arc42 |  Operations A3 Problem Solving |
|---|---|---|---|---|
Purposedifferent | The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning. | 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. | 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. | 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. |
Complexitydifferent | High | Low | Low | Medium |
Timedifferent | Initial 3-6 h, then monthly or quarterly reviews | 30-120 min | 1-2 Tage | 45-90 min |
Participantsdifferent | 5-12 | 2-6 | 1-4 | 2-5 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Execution Loop, Review Cadence, Strategic Learning Log | Observation Notes, Improvement Ideas | Architecture Document, Context View, Runtime View, Deployment View | A3 Report, Action Plan, Root Cause Analysis |
Tagsno overlap | ExecutionCadenceLearningGovernance | LeanObservationProcessOperations | ArchitectureDocumentationCommunication | LeanProblem solvingCoachingOperations |