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
Paper illustration of a journey map with four connected phases, several experience lanes and a point marked for closer investigation.
UX Research
Customer Journey Mapping
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Planning Poker.
Agile
Planning Poker
Paper illustration for Bucket System.
Agile
Bucket System
Purposedifferent
When a user journey falls apart across many touchpoints, customer journey mapping makes the experience visible as a coherent arc. Phases, emotions, and breaks become legible enough to prioritize critical moments deliberately.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 estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions.When a large batch of work needs a fast, rough estimate, it sorts items into predefined size buckets. It sorts work by value, risk, and delivery ability. The result is captured as a Bucketed Backlog, Relative Estimates, and Split Candidates.
Complexitydifferent
MediumLowLowMedium
Timedifferent
2-4 h20-40 min initial, dann laufend2-5 min je Item30-90 min
Participantsdifferent
4-103-153-93-12
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
Journey Map, Pain-point List, Opportunity BacklogROAM Board, Owner ListRelative Estimates, Assumption Notes, Split CandidatesBucketed Backlog, Relative Estimates, Split Candidates
Tagsno overlap
JourneyServiceService design
RiskAgileTrackingAlignment
EstimationAgileRelative sizingTeam
EstimationBacklogRelative sizing
Add more methods