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 Impact Filter
Decision Making
Impact Filter
Paper illustration for RAPID
Decision Making
RAPID
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
With new ideas or requests, the conversation often turns to solutions too early and to effect too little. An Impact Filter forces the initiative into an effect perspective and checks whether it creates a relevant difference.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.arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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
LowMediumLowMedium
Timedifferent
20-45 min45-90 min1-2 Tage1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-63-121-43-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Impact Filter, Success Criteria, Next StepRAPID Role Map, Recommendation, Decision LogArchitecture Document, Context View, Runtime View, Deployment ViewRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ImpactOutcomesFramingDecision
DecisionRolesGovernance
ArchitectureDocumentationCommunication
ArchitectureDecisionAsyncGovernance
Add more methods