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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper illustration of the Force Field Analysis working structure.
Decision Making
Force Field Analysis
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
ARID examines how well developers can work with a technical design. It focuses on a part of the system that can still be revised, between the architecture overview and the detailed specification.GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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 stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumMediumLowLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 h45-90 min30-90 min
Participantsdifferent
Designers, developers as users, and facilitation2-83-122-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsGap Matrix, Action Plan, Risk NotesForce Field Map, Change Levers, Risk NotesConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
StrategyAnalysisPlanning
ChangeDecisionStrategy
ConstraintsDecisionPlanningOptions
Add more methods