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:RAID Log Rich Picture ATAM (Architecture Tradeoff Analysis Method)Architecture Decision Record

Criterion	Delivery RAID Log	Systems Thinking Rich Picture	Architecture ATAM (Architecture Tradeoff Analysis Method)	Architecture Architecture Decision Record
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.	A Rich Picture brings an unclear situation onto a shared drawing. It captures actors, tensions, information flows, and blind spots before the team jumps to solutions too early.	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.	An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.
Complexitydifferent	Low	Low	High	Low
Timedifferent	30 min Setup, dann laufend	30-90 min	Several meetings plus preparation and analysis; total effort depends on scope	15-45 min
Participantsdifferent	1-3 maintaining, briefing for everyone	2-10	Evaluation team, architects, and relevant stakeholders	1-3
Formatdifferent	Async	Workshop	Workshop + async	Async
Outputdifferent	RAID Log, Status Report Source	Rich Picture, Problem Framing Notes	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations	ADR File, Decision Log, Rationale
Tagsno overlap	RiskTrackingStakeholdersGovernance	Systems thinkingSoft systemsFramingVisualization	ArchitectureQualityRiskTradeoffsStakeholders	ArchitectureRationaleDocumentationGovernance

Add more methods