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)
A/B Testing workspace showing the question, observations, and next decision.
Growth
A/B Testing
Paper illustration of Stakeholder Salience Model with its method-specific working model.
Facilitation
Stakeholder Salience Model
Stakeholder Mapping
Facilitation
Stakeholder Mapping
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.When two variants compete, discussions quickly decide by taste rather than effect. A/B Testing checks behavior under controlled conditions and separates real improvement from chance or expectation effects.When stakeholders appear to matter very differently, the Stakeholder Salience Model rates their actual priority through power, legitimacy, and urgency. It turns individual contributions into a visible selection. The result is captured as a Salience diagram and a class-based strategy.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.
Complexitydifferent
MediumHighMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-4 Wochen60-90 min60–90 min
Participantsdifferent
Designers, developers as users, and facilitation1-63-62-8
Formatdifferent
Workshop + asyncAsyncWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsExperiment results, Decision log, Learning summarySalience Diagram, Strategy per ClassStakeholder Map, Engagement Plan, Risk Notes
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ExperimentsGrowthAnalyticsValidation
StakeholdersFacilitationAlignmentGovernance
StakeholdersAlignmentFacilitationChange
Add more methods