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 of a JTBD interview notebook with a decision timeline, forces of change and a concise job hypothesis.
Product Discovery
Jobs to Be Done
Design Thinking as a learning loop: an observation notebook, a focused problem statement, different idea sketches, a cardboard prototype and user-test notes. Feedback leads to new understanding.
Innovation
Design Thinking
Paper illustration of two user profile cards with a goal, behavior evidence, and an open research question.
UX Research
Personas
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 switching motives and progress are unclear, it reconstructs the situation from real customer circumstances. It shows why a switch happens and what kind of progress is being sought.For complex user problems with an uncertain cause, the method connects observation, interpretation, and experiment into a learning cycle. It keeps the focus on real needs and avoids premature solution language. This produces robust decisions for product and service.When target groups stay too vague and teams talk about the same people differently, personas create a shared, solid picture of usage. Condensed profiles make needs, contexts, and differences tangible enough for decisions.
Complexitydifferent
MediumMediumHighMedium
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1-3 Wochen1 Tag bis mehrere Wochen1-3 Tage
Participantsdifferent
Designers, developers as users, and facilitation5-12 Interviews4-10Internes Team
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsJob Stories, Outcome Statements, Opportunity ListProblem Statement, Prototype, Test LearningsPersona Profiles, Needs Summary, Scenario Notes
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
CustomerOutcomesNeeds
InnovationPrototypeResearch
ResearchCustomerSynthesis
Add more methods