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 paper-based illustration representing WSJF with its core stages and visible working result.
Agile
WSJF
Paper illustration of a calm four-quadrant Assumption Map with hypothesis cards and emphasis on important assumptions with little evidence.
Product Discovery
Assumption Mapping
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
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 many tasks compete for the same capacity, it orders work by economic impact. It makes time lost, benefit, and effort comparable together.When assumptions still sit unordered in the room, it weighs uncertainty against leverage. It makes visible which hypotheses should be checked first.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional45-90 min45-60 min3–4 h for initial assessment; preparation and deeper analysis additional
Participantsdifferent
Designers, developers as users, and facilitation3-102-81 or a small team; particularly suitable for 3–4 people
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsRanked Backlog, Cost-of-Delay AssumptionsAssumption map, Test backlog, Risk rankingLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checks
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
LeanEconomicsSequencePrioritization
AssumptionsRiskExperimentsValidation
ArchitectureQualityRiskAssessmentLean
Add more methods