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
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
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.When work needs to move between different states or columns, it makes that movement and its handoffs legible. It sorts work by value, risk, and delivery ability. The result is captured as a ROAM Board and an Owner List.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.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.
Complexitydifferent
HighLowMediumLow
Timedifferent
0.5-2 Tage20-40 min initial, dann laufend1-2 h30 min Setup, dann laufend
Participantsdifferent
6-123-154-121-3 maintaining, briefing for everyone
Formatdifferent
WorkshopWorkshop + asyncWorkshopAsync
Outputdifferent
Service Blueprint, Fail Points, Ownership MapROAM Board, Owner ListAlignment Map, Open Issues, Decision QuestionsRAID Log, Status Report Source
Tagsno overlap
Service designOperationsJourneyBlueprint
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
RiskTrackingStakeholdersGovernance
Add more methods