methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
A paper-based illustration representing Service Blueprint with its core stages and visible working result.
UX Design
Service Blueprinting
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Power-Interest Grid with a method-specific labelled workspace.
Facilitation
Power Interest Grid
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When a service experience is spread across several touchpoints, it brings frontstage and backstage together. It shows where user contact and internal responsibility must fit.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 many stakeholders compete for attention at once, the Power Interest Grid sorts them by influence and stake. It turns individual contributions into a visible selection. The result is captured as a Power Interest Grid and a stakeholder-specific strategy.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.
Complexitydifferent
HighLowLowMedium
Timedifferent
0.5-2 Tage1-2 Tage30-60 min1-2 h
Participantsdifferent
6-121-42-84-12
Formatdifferent
WorkshopWorkshop + asyncWorkshopWorkshop
Outputdifferent
Service Blueprint, Fail Points, Ownership MapArchitecture Document, Context View, Runtime View, Deployment ViewPower Interest Grid, Strategy per StakeholderAlignment Map, Open Issues, Decision Questions
Tagsno overlap
Service designOperationsJourneyBlueprint
ArchitectureDocumentationCommunication
StakeholdersFacilitationAlignmentPlanning
AlignmentStakeholdersStrategyFacilitation
Add more methods