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 Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.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.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
45-90 min30 min Setup, dann laufend20-40 min initial, dann laufend1-2 h
Participantsdifferent
3-101-3 maintaining, briefing for everyone3-154-12
Formatdifferent
WorkshopAsyncWorkshop + asyncWorkshop
Outputdifferent
Context canvas, Open questions, Shared context notesRAID Log, Status Report SourceROAM Board, Owner ListAlignment Map, Open Issues, Decision Questions
Tagsno overlap
ContextFramingRequirementsCanvas
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
AlignmentStakeholdersStrategyFacilitation
Add more methods