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 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
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for Alignment Mapping.
Facilitation
Alignment Mapping
Purposedifferent
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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
LowLowMediumMedium
Timedifferent
30 min Setup, dann laufend20-40 min initial, dann laufend1-3 Tage1-2 h
Participantsdifferent
1-3 maintaining, briefing for everyone3-151-44-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncWorkshop
Outputdifferent
RAID Log, Status Report SourceROAM Board, Owner ListArchitecture Views, Cross-view Notes, RationaleAlignment Map, Open Issues, Decision Questions
Tagsno overlap
RiskTrackingStakeholdersGovernance
RiskAgileTrackingAlignment
DocumentationStakeholdersArchitecture
AlignmentStakeholdersStrategyFacilitation
Add more methods