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

Criterion	Architecture Architecture Decision Record	Decision Making Eisenhower Matrix	Delivery RAID Log	Architecture ATAM (Architecture Tradeoff Analysis Method)
Purposedifferent	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.	It separates true priorities from noise so it becomes clear what should be done now, scheduled, delegated, or dropped.	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	Low	Low	Low	High
Timedifferent	15-45 min	15-30 min	30 min Setup, dann laufend	Several meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent	1-3	1-6	1-3 maintaining, briefing for everyone	Evaluation team, architects, and relevant stakeholders
Formatdifferent	Async	Workshop + async	Async	Workshop + async
Outputdifferent	ADR File, Decision Log, Rationale	Eisenhower Matrix, Action List, Delegation Notes	RAID Log, Status Report Source	Prioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap	ArchitectureRationaleDocumentationGovernance	PrioritizationFocusTasks	RiskTrackingStakeholdersGovernance	ArchitectureQualityRiskTradeoffsStakeholders

Add more methods