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 Shape Up | ![]() Facilitation Alignment Mapping | ![]() Facilitation Stakeholder Mapping |
|---|---|---|---|---|
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. | Shape Up helps clarify scope, sequence, and delivery flow. It makes work boundaries and decisions explicit and captures results as pitches, bet-table decisions, and hill charts. | When several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable. | 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. |
Complexitydifferent | Low | Medium | Medium | Low |
Timedifferent | 1-4 h | 6 Wochen Cycle + 2 Wochen Cool-Down | 1-2 h | 60–90 min |
Participantsdifferent | 1-5 | 2-4 pro Pitch | 4-12 | 2-8 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Context Diagram, Container Diagram, Component Diagram | Pitches, Bet-table decisions, Hill charts, Cooldown outcomes | Alignment Map, Open Issues, Decision Questions | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureCommunicationVisualization | PlanningDeliveryAutonomy | AlignmentStakeholdersStrategyFacilitation | StakeholdersAlignmentFacilitationChange |



