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 After-Action Review |  Delivery RAID Log |  Architecture Architecture Communication Canvas |
|---|---|---|---|
Purposedifferent | 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. | Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting. | 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 | Low | Medium |
Timedifferent | 20-45 min | 30 min Setup, dann laufend | 60-120 min |
Participantsdifferent | 3-12 | 1-3 maintaining, briefing for everyone | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async |
Outputdifferent | Lessons learned, Action items, Event summary | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan |
Tagsno overlap | LearningOperationsImprovement | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
