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 Landing Page Test.
Product Discovery
Landing Page Test
Paper illustration of an activity-role table with clear RACI assignments and one highlighted accountable role per activity.
Operations
RACI Matrix
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for RAPID
Decision Making
RAPID
Purposedifferent
When a value proposition first needs to be checked for resonance, it condenses the idea onto a focused entry page. It shows whether language and offering carry interest.With unclear responsibilities across several roles or areas, the method creates unambiguous accountability logic. It reduces friction because decision, execution, contribution, and information become separately visible.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.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.
Complexitydifferent
MediumLowMediumMedium
Timedifferent
1-5 Tage45-90 min1-3 Wochen vom Draft bis zur Entscheidung45-90 min
Participantsdifferent
Nutzertraffic2-83-20 Reviewer3-12
Formatdifferent
AsyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Landing Page, Conversion Data, Learning SummaryRACI Matrix, Responsibility Map, Decision NotesRFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsRAPID Role Map, Recommendation, Decision Log
Tagsno overlap
ValidationConversionMarketing
RolesResponsibilityGovernanceOperations
ArchitectureDecisionAsyncGovernance
DecisionRolesGovernance
Add more methods