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 for Decision Framing Workshop.
Decision Making
Decision Framing Workshop
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When a decision is poorly framed, even good answers deliver little value. A Decision Framing Workshop sharpens the problem, goal, and boundaries before the actual weighing begins.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.In complex management decisions, clarity is often missing about who recommends, who agrees, and who makes the decision. RAPID creates this assignment and stabilizes decisions across several levels.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
MediumLowMediumMedium
Timedifferent
60-120 min15-45 min45-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
4-101-33-123-20 Reviewer
Formatdifferent
WorkshopAsyncWorkshop + asyncAsync
Outputdifferent
Decision Frame, Decision Question, Criteria List, Evidence PlanADR File, Decision Log, RationaleRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
Decision framingAlignmentCriteriaOptions
ArchitectureRationaleDocumentationGovernance
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
Add more methods