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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
A 5 Whys working surface connects an observable problem with evidenced causes, marked uncertainty and concrete countermeasures with ownership.
Operations
5 Whys
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
Paper illustration for 8D Problem Solving.
Operations
8D Problem Solving
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.For a single, hard-to-explain deviation, the method exposes the causal chain behind the visible symptom. It keeps the cause open until a controllable condition emerges instead of a mere description.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.For an acute quality or delivery problem, the method structures immediate protection and root cause work together. It keeps the situation stable while the actual cause is investigated cleanly.
Complexitydifferent
MediumLowHighHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional15-30 minSeveral meetings plus preparation and analysis; total effort depends on scope1-6 Wochen
Participantsdifferent
Designers, developers as users, and facilitation2-6Evaluation team, architects, and relevant stakeholders4-10
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRoot cause notes, CountermeasuresPrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations8D Report, Containment Plan, Root Cause Evidence, Corrective Action Plan
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
Root causeIncidentLeanProblem solving
ArchitectureQualityRiskTradeoffsStakeholders
QualityProblem solvingRoot cause
Add more methods