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)
Scenario Planning method illustration showing its working structure
Business Strategy
Scenario Planning
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.Scenario Planning opens the view to several plausible futures instead of a single forecast. The method protects strategies from depending on too narrow an expected path.
Complexitydifferent
MediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional0.5-2 Tage
Participantsdifferent
Designers, developers as users, and facilitation4-12
Formatdifferent
Workshop + asyncWorkshop
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsScenario Set, Strategic Implications, Robust Options
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
StrategyUncertaintyPlanning
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
Paper notes move from an inbox to action, project and calendar collections.
Operations
Getting Things Done
Paper illustration of a branching impact map with a Why goal at the root, actor circles, How behavior changes and What options.
Product Strategy
Impact Mapping
Paper illustration for Risk Storming.
Architecture
Risk Storming