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 |  Architecture Architecture Communication Canvas |  Decision Making Red Teaming |
|---|---|---|---|
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. | The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design. | For strategic decisions with high reach, agreement and gut feeling are often not enough. Red teaming brings deliberate opposition into the situation and tests where a plan breaks under real counterarguments. |
Complexitydifferent | Low | Medium | High |
Timedifferent | 30 min Setup, dann laufend | 60-120 min | 1-4 h |
Participantsdifferent | 1-3 maintaining, briefing for everyone | 2-8 | 3-8 |
Formatdifferent | Async | Workshop + async | Workshop |
Outputdifferent | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Challenge Findings, Risk Register, Mitigation Plan |
Tagsno overlap | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | RiskDecisionSensemaking |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
