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
Paper illustration for 1-2-4-All.
Facilitation
1-2-4-All
Paper illustration for RAPID
Decision Making
RAPID
Paper illustration of the Lightning Decision Jam working structure.
Facilitation
Decision Jam
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.When many people in a group too rarely get to speak, 1-2-4-All distributes thinking time more fairly. The format builds participation step by step and makes quiet or still-unformed thoughts usable faster.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.When a decision is stuck, Decision Jam loosens the knot through structured separation of problem, idea, and selection. The format creates movement without jumping prematurely at the first seemingly elegant answer.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung10-20 min45-90 min60-90 min
Participantsdifferent
3-20 Reviewer4-100+3-124-10
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsIdea List, Shared Insights, Emergent ThemesRAPID Role Map, Recommendation, Decision LogProblem Cluster, Prioritized Challenge, Experiment
Tagsno overlap
ArchitectureDecisionAsyncGovernance
FacilitationInclusionIdeation
DecisionRolesGovernance
FacilitationDecisionProblem solvingWorkshop
Add more methods