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
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Design sheets and interface cards connect to jointly written pseudocode with highlighted unresolved questions.
Architecture
ARID (Active Reviews for Intermediate Designs)
Software Architecture Canvas method illustration showing its working structure
Architecture
Software Architecture Canvas
Architecture Communication Canvas method illustration showing its working structure
Architecture
Architecture Communication Canvas
Purposedifferent
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.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.The Software Architecture Canvas reduces a system to the most important architecture decisions, constraints, and interfaces. It is useful when teams need a resilient overall picture quickly.The Architecture Communication Canvas plans architecture communication so the right people receive the right message. The method turns technical complexity into deliberate communication design.
Complexitydifferent
HighMediumLowMedium
Timedifferent
Mehrere Wochen2–4 h review as a planning range; preparation and evaluation additional1-2 h60-120 min
Participantsdifferent
2-6 researchers plus sampleDesigners, developers as users, and facilitation3-102-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesPrioritized development tasks, Jointly produced code or pseudocode, Observed difficulties and open design questions, Proposed design revisionsArchitecture Canvas, Goals, Constraints, Quality AttributesCommunication Canvas, Stakeholder Messages, Architecture Communication Plan
Tagsno overlap
OutcomesInnovationResearchQuantitative
ArchitectureEngineeringFeedbackValidationTasks
CanvasArchitectureAlignmentWorkshop
ArchitectureCommunicationStakeholdersCanvas
Add more methods