View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:ABC AnalysisA3 Problem SolvingSoftware Architecture CanvasArchitecture Communication Canvas
| Criterion | ![]() Operations ABC Analysis | ![]() Operations A3 Problem Solving | ![]() Architecture Software Architecture Canvas | ![]() Architecture Architecture Communication Canvas |
|---|---|---|---|---|
Purposedifferent | With many similar objects of differing economic significance, the method prioritizes effort by effect. It separates what needs regular steering from what rarely needs attention. | 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. | 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 | Low | Medium | Low | Medium |
Timedifferent | 30-60 min | 45-90 min | 1-2 h | 60-120 min |
Participantsdifferent | 1-5 | 2-5 | 3-10 | 2-8 |
Formatdifferent | Async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | ABC Classification, Focus Rules, Control List | A3 Report, Action Plan, Root Cause Analysis | Architecture Canvas, Goals, Constraints, Quality Attributes | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | PrioritizationOperationsPortfolio | LeanProblem solvingCoachingOperations | CanvasArchitectureAlignmentWorkshop | ArchitectureCommunicationStakeholdersCanvas |



