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
ChatOps workspace showing the question, observations, and next decision.
DevOps
ChatOps
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Surveys method illustration showing its working structure
UX Research
Surveys
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Purposedifferent
For operational work in a distributed team, the method links communication with direct system control. It records decisions right where the signal, the context, and the execution come together.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.When a topic needs to be validated broadly and many people can answer the same question, surveys gather structured feedback in a scalable form. Answers become comparable and segmentable instead of remaining merely anecdotal.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.
Complexitydifferent
MediumHighMediumMedium
Timedifferent
OngoingMehrere Wochen3-14 Tage2–4 h review as a planning range; preparation and evaluation additional
Participantsdifferent
2-202-6 researchers plus sample50+Designers, developers as users, and facilitation
Formatdifferent
Workshop + asyncWorkshop + asyncAsyncWorkshop + async
Outputdifferent
Chat Transcript, Action Log, AutomationsDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesSurvey Results, Charts, Segment InsightsPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisions
Tagsno overlap
CollaborationEngineeringIncident
OutcomesInnovationResearchQuantitative
QuantitativeResearchValidation
ArchitectureEngineeringFeedbackValidationTasks
Add more methods