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 Product Canvas with its core stages and visible working result.
Product Strategy
Product Canvas
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Architecture Inception Canvas method illustration showing its working structure
Architecture
Architecture Inception Canvas
Purposedifferent
When product goal and feature scope don't yet fit cleanly together, it creates a shared working picture. It connects need, core features, and assumptions into a solid starting point.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.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.The Architecture Inception Canvas bundles the first architecture questions into a compact decision picture. It fits when an initiative is still in motion but still needs clear guardrails.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-2 h20-40 min initial, dann laufend30 min Setup, dann laufend1-2 h
Participantsdifferent
2-83-151-3 maintaining, briefing for everyone3-8
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop
Outputdifferent
Product Canvas, Product Assumptions, Scope NotesROAM Board, Owner ListRAID Log, Status Report SourceInception Canvas, Risks, Goal List, Open Questions
Tagsno overlap
CanvasDiscoveryScope
RiskAgileTrackingAlignment
RiskTrackingStakeholdersGovernance
AlignmentArchitectureCanvas
Add more methods