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 of the McKinsey 7S Framework with seven connected fields
Business Strategy
McKinsey 7S
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Paper illustration for Alignment Mapping.
Facilitation
Alignment 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.McKinsey 7S checks whether Strategy, Structure, Systems, Shared Values, Skills, Style, and Staff fit together. Organizational misalignments become visible across multiple levers as a result.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 several people work toward one goal but hold different mental maps, Alignment Mapping makes the discrepancies visible. It arranges goals, assumptions, and priorities so shared direction becomes verifiable.
Complexitysame
MediumMediumMediumMedium
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung2-4 h15-60 min je Zyklus1-2 h
Participantsdifferent
3-20 Reviewer3-121-84-12
Formatdifferent
AsyncWorkshopWorkshop + asyncWorkshop
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets7S Assessment, Alignment Gaps, Change ActionsSituation Assessment, Decision Loop, Action UpdatesAlignment Map, Open Issues, Decision Questions
Tagsno overlap
ArchitectureDecisionAsyncGovernance
OrganizationStrategyAlignmentChange
DecisionChangeLearningStrategy
AlignmentStakeholdersStrategyFacilitation
Add more methods