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 Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration for RAPID
Decision Making
RAPID
Purposedifferent
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.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.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.
Complexitysame
MediumMediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung1-3 Tage45-90 min
Participantsdifferent
3-20 Reviewer1-43-12
Formatdifferent
AsyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsArchitecture Views, Cross-view Notes, RationaleRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
ArchitectureDecisionAsyncGovernance
DocumentationStakeholdersArchitecture
DecisionRolesGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas