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 |  Business Strategy Balanced Scorecard |  Facilitation Stakeholder Mapping |
|---|---|---|---|
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. | Balanced Scorecard translates strategy into a few interconnected perspectives and metrics. It holds impact, steering, and learning together in daily work instead of narrowing strategy down to financial figures. | 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 | High | Low |
Timedifferent | 1-2 Tage | Halber Tag bis mehrere Wochen | 60–90 min |
Participantsdifferent | 1-4 | 4-12 | 2-8 |
Formatsame | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Balanced Scorecard, Strategic Measures, Initiative Map | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | StrategyMetricsExecution | StakeholdersAlignmentFacilitationChange |
Often compared together
Methods with strong topical overlap with the current selection, not yet in the comparison.
