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 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
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Paper illustration for ALPEN Method
Operations
ALPEN Method
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Purposedifferent
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.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.With an overloaded day full of too many tasks, a realistic picture of the day emerges. The method connects estimating, deciding, and buffer thinking so planning fits available energy and time.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
HighMediumLowHigh
Timedifferent
1 Tag bis mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional10-20 min dailyMehrere Wochen
Participantsdifferent
4-10Designers, developers as users, and facilitation12-6 researchers plus sample
Formatdifferent
WorkshopWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDaily Plan, Time Estimates, Review NotesDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses
Tagsno overlap
InnovationPrototypeResearch
ArchitectureEngineeringFeedbackValidationTasks
PlanningTime managementProductivityOperations
OutcomesInnovationResearchQuantitative
Add more methods