View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
Selected:Process MappingArchitecture Inception CanvasSoftware Architecture CanvasAfter-Action Review
| Criterion |  Operations Process Mapping |  Architecture Architecture Inception Canvas |  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. | The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails. | 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 | 1-2 h | 1-2 h | 20-45 min |
Participantsdifferent | 3-10 | 3-8 | 3-10 | 3-12 |
Formatdifferent | Workshop | Workshop | Workshop | Workshop + async |
Outputdifferent | Process Map, Handoff List, Improvement Backlog | Inception Canvas, Risks, Goal List, Open Questions | Architecture Canvas, Goals, Constraints, Quality Attributes | Lessons learned, Action items, Event summary |
Tagsno overlap | ProcessOperationsImprovement | AlignmentArchitectureCanvas | CanvasArchitectureAlignmentWorkshop | LearningOperationsImprovement |