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 Gemba Walk | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
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. | 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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. |
Complexitydifferent | Medium | Low | Low | Medium |
Timedifferent | 45-90 min | 30-120 min | 1-2 h | 60-120 min |
Participantsdifferent | 2-5 | 2-6 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Observation Notes, Improvement Ideas | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | LeanProblem solvingCoachingOperations | LeanObservationProcessOperations | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |



