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
Decision Tree method illustration showing its working structure
Decision Making
Decision Tree
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
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
For decisions with follow-on paths and dependencies, a linear comparison is often not enough. A Decision Tree shows how options branch under conditions and which consequences hang on each branch.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.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
30-90 min1-2 h45-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-63-103-123-20 Reviewer
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncAsync
Outputdifferent
Decision Tree, Option Map, Assumption ListArchitecture Canvas, Goals, Constraints, Quality AttributesRAPID Role Map, Recommendation, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
DecisionTreeOptions
CanvasArchitectureAlignmentWorkshop
DecisionRolesGovernance
ArchitectureDecisionAsyncGovernance
Add more methods