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 Time Blocking |  Delivery RAID Log |  Architecture Architecture Communication Canvas |  Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure. | 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. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Low | Low | Medium | Low |
Timedifferent | 15-30 min Planung, laufend | 30 min Setup, dann laufend | 60-120 min | 45-90 min |
Participantsdifferent | 1 | 1-3 maintaining, briefing for everyone | 2-8 | 2-6 |
Formatdifferent | Async | Async | Workshop + async | Workshop + async |
Outputdifferent | Blocked Calendar, Capacity View, Focus Plan | RAID Log, Status Report Source | Communication Canvas, Stakeholder Messages, Architecture Communication Plan | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | PlanningTime managementFocus | RiskTrackingStakeholdersGovernance | ArchitectureCommunicationStakeholdersCanvas | CommunicationStakeholdersDeliveryPlanning |