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 OODA Loop.
Decision Making
OODA Loop
Paper illustration for Cynefin Workshop.
Decision Making
Cynefin Workshop
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
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.In dynamic situations, decisions become outdated faster than they can be prepared. The OODA Loop holds observing, orienting, deciding, and acting together as a recurring rhythm so reaction does not slide into inertia.When problems are unclear, chaotic, or only seemingly familiar, standard recipes fall short. A Cynefin Workshop sorts situations by the nature of their problem and connects them with matching action logic.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung15-60 min je Zyklus60-180 min1-3 h
Participantsdifferent
3-20 Reviewer1-84-201-8
Formatdifferent
AsyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsSituation Assessment, Decision Loop, Action UpdatesCynefin Map, Domain-specific Actions, Sensemaking NotesArgument Map, Evidence Gaps, Decision Rationale
Tags1 shared
ArchitectureDecisionAsyncGovernance
DecisionChangeLearningStrategy
ComplexitySensemakingDecision
SensemakingDecisionRationale
Add more methods