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.

Selected:ARID (Active Reviews for Intermediate Designs)Design ThinkingPersonasOutcome-Driven Innovation
Criterion
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
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.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.Outcome-Driven Innovation clarifies customer problems, solution opportunities, and evidence. It separates jobs, desired outcomes, importance, satisfaction, and opportunity, and captures results as desired outcome statements, an opportunity landscape, and segments by underserved needs.
Complexitydifferent
MediumHighMediumHigh
Timedifferent
2–4 h review as a planning range; preparation and evaluation additional1 Tag bis mehrere Wochen1-3 TageMehrere Wochen
Participantsdifferent
Designers, developers as users, and facilitation4-10Internes Team2-6 researchers plus sample
Formatdifferent
Workshop + asyncWorkshopWorkshop + asyncWorkshop + async
Outputdifferent
Prioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsProblem Statement, Prototype, Test LearningsPersona Profiles, Needs Summary, Scenario NotesDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses
Tagsno overlap
ArchitectureEngineeringFeedbackValidationTasks
InnovationPrototypeResearch
ResearchCustomerSynthesis
OutcomesInnovationResearchQuantitative
Add more methods