View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:A3 Problem SolvingKaizen EventSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion | ![]() Operations A3 Problem Solving | ![]() Operations Kaizen Event | ![]() 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. | For a tightly scoped process segment with noticeable waste, the method bundles shared energy for change. It suits situations that call for fast learning loops and visible adjustments. | 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 | Medium | Low | Medium |
Timedifferent | 45-90 min | 0.5-5 Tage | 1-2 h | 60-120 min |
Participantsdifferent | 2-5 | 4-10 | 3-10 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | A3 Report, Action Plan, Root Cause Analysis | Kaizen Charter, Waste List, Improvement Experiments, Standard Work Update | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | LeanProblem solvingCoachingOperations | LeanContinuous improvementOperations | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |



