View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Architecture C4 Model | ![]() Delivery RAID Log | ![]() Delivery Communication Plan | ![]() Facilitation Power Interest Grid |
|---|---|---|---|---|
Purposedifferent | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | 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. | 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. | When many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 30 min Setup, dann laufend | 45-90 min | 30-60 min |
Participantsdifferent | 1-5 | 1-3 maintaining, briefing for everyone | 2-6 | 2-8 |
Formatdifferent | Workshop + async | Async | Workshop + async | Workshop |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | RAID Log, Status Report Source | Communication Plan, Channel Matrix, Message Cadence | Power Interest Grid, Strategy per Stakeholder |
Tagsno overlap | ArchitectureCommunicationVisualization | RiskTrackingStakeholdersGovernance | CommunicationStakeholdersDeliveryPlanning | StakeholdersFacilitationAlignmentPlanning |



