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 |  Agile ROAM Board |  Facilitation Stakeholder Mapping |  Delivery RAID Log |
|---|---|---|---|---|
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. | When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List. | When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first. | 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. |
Complexitysame | Low | Low | Low | Low |
Timedifferent | 1-4 h | 20-40 min initial, dann laufend | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-5 | 3-15 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Workshop + async | Async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | ROAM Board, Owner List | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureCommunicationVisualization | RiskAgileTrackingAlignment | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |