View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Delivery RAID Log |  Operations Process Mapping |  Architecture Architecture Communication Canvas |  Operations After-Action Review |
|---|---|---|---|---|
Purposedifferent | 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. | 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 Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | 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 | Low | Medium | Medium | Low |
Timedifferent | 30 min Setup, dann laufend | 1-3 h | 60-120 min | 20-45 min |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 3-10 | 2-8 | 3-12 |
Formatdifferent | Async | Workshop | Workshop + async | Workshop + async |
Outputdifferent | RAID Log, Status Report Source | Process Map, Handoff List, Improvement Backlog | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Lessons learned, Action items, Event summary |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ProcessOperationsImprovement | ArchitectureCommunicationStakeholdersCanvas | LearningOperationsImprovement |