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.

Selected:ROAM BoardDesign ThinkingRAID LogATAM (Architecture Tradeoff Analysis Method)
Criterion
Paper board with the four ROAM fields Resolved, Owned, Accepted, and Mitigated.
Agile
ROAM Board
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent
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.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.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.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
LowHighLowHigh
Timedifferent
20-40 min initial, dann laufend1 Tag bis mehrere Wochen30 min Setup, dann laufendSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
3-154-101-3 maintaining, briefing for everyoneEvaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncWorkshopAsyncWorkshop + async
Outputdifferent
ROAM Board, Owner ListProblem Statement, Prototype, Test LearningsRAID Log, Status Report SourcePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
RiskAgileTrackingAlignment
InnovationPrototypeResearch
RiskTrackingStakeholdersGovernance
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods