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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Stakeholder Mapping
Facilitation
Stakeholder Mapping
Paper illustration for OODA Loop.
Decision Making
OODA Loop
Purposedifferent
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.In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving.When an initiative depends on many people, interests, and power dynamics, Stakeholder Mapping systematically orders the environment. It shows who influences, who is affected, and where relationship management or safeguarding matters first.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.
Complexitydifferent
LowLowLowMedium
Timedifferent
1-2 Tage45-90 min60–90 min15-60 min je Zyklus
Participantsdifferent
1-43-122-81-8
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewForce Field Map, Change Levers, Risk NotesStakeholder Map, Engagement Plan, Risk NotesSituation Assessment, Decision Loop, Action Updates
Tagsno overlap
ArchitectureDocumentationCommunication
ChangeDecisionStrategy
StakeholdersAlignmentFacilitationChange
DecisionChangeLearningStrategy
Add more methods