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 arc42 |  Facilitation Stakeholder Mapping |  Delivery RAID Log |
|---|---|---|---|
Purposedifferent | arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes. | 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 |
Timedifferent | 1-2 Tage | 60–90 min | 30 min Setup, dann laufend |
Participantsdifferent | 1-4 | 2-8 | 1-3 maintaining, briefing for everyone |
Formatdifferent | Workshop + async | Workshop + async | Async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Stakeholder Map, Engagement Plan, Risk Notes | RAID Log, Status Report Source |
Tagsno overlap | ArchitectureDocumentationCommunication | StakeholdersAlignmentFacilitationChange | RiskTrackingStakeholdersGovernance |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
