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 Alignment Mapping | ![]() Business Strategy Business Model Stress Test | ![]() 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. | 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. | A Business Model Stress Test checks how well a business model holds up under pressure and headwinds. It compares strengths, risks, market logic, and courses of action. The result is captured as a stress-test report and action plan per scenario. | 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 | High | Low |
Timedifferent | 1-2 Tage | 1-2 h | Half day | 60–90 min |
Participantsdifferent | 1-4 | 4-12 | 3-8 | 2-8 |
Formatdifferent | Workshop + async | Workshop | Workshop | Workshop + async |
Outputdifferent | Architecture Document, Context View, Runtime View, Deployment View | Alignment Map, Open Issues, Decision Questions | Stress Test Report, Action Plan per Scenario | Stakeholder Map, Engagement Plan, Risk Notes |
Tagsno overlap | ArchitectureDocumentationCommunication | AlignmentStakeholdersStrategyFacilitation | StrategyBusiness modelRiskDiagnosis | StakeholdersAlignmentFacilitationChange |



