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
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
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.When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
LowMediumMediumMedium
Timedifferent
15-45 min1-3 Tage2–4 h review as a planning range; preparation and evaluation additional1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-3Internes TeamDesigners, developers as users, and facilitation3-20 Reviewer
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
ADR File, Decision Log, RationalePersona Profiles, Needs Summary, Scenario NotesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
ResearchCustomerSynthesis
ArchitectureEngineeringFeedbackValidationTasks
ArchitectureDecisionAsyncGovernance
Add more methods