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
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
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.The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes.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.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
HighLowMediumHigh
Timedifferent
1 Tag bis mehrere Wochen1-4 h2–4 h review as a planning range; preparation and evaluation additionalMehrere Wochen
Participantsdifferent
4-101-5Designers, developers as users, and facilitation2-6 researchers plus sample
Formatdifferent
WorkshopWorkshop + asyncWorkshop + asyncWorkshop + async
Outputdifferent
Problem Statement, Prototype, Test LearningsContext Diagram, Container Diagram, Component DiagramPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypotheses
Tagsno overlap
InnovationPrototypeResearch
ArchitectureCommunicationVisualization
ArchitectureEngineeringFeedbackValidationTasks
OutcomesInnovationResearchQuantitative
Add more methods