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)
Paper illustration for Fake Door Test
Product Discovery
Fake Door Test
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)
Paper illustration of a Learning Card with four fields for hypothesis, observation, insight, and action.
Product Discovery
Learning Card
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 demand is still unclear, it measures interest in a feature before it is built. It separates real behavior from polite agreement and deliberately keeps build effort small.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.The Learning Card connects traceable test results to a reasoned next action while keeping the limits of the insight visible.
Complexitydifferent
MediumMediumMediumLow
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-5 Tage3–4 h for initial assessment; preparation and deeper analysis additional25-40 min
Participantsdifferent
Designers, developers as users, and facilitationNutzertraffic1 or a small team; particularly suitable for 3–4 people1-5
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsClick Data, Interest Signal, Learning DecisionLean 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 checksLearning Card with evidence and next action
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
ValidationExperimentsDemandDiscovery
ArchitectureQualityRiskAssessmentLean
ExperimentsValidationDiscoveryLearning
Add more methods