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
Paper illustration of RAID Log with a method-specific labelled workspace.
Delivery
RAID Log
Views and Beyond method illustration showing its working structure
Architecture
Views and Beyond
Paper illustration: scenarios and architectural decisions are connected to identified risks.
Architecture
ATAM (Architecture Tradeoff Analysis Method)
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.Helps clarify scope, sequence, and delivery flow in concrete terms. It makes work, boundaries, and order steerable. The result is captured as a RAID Log and a source for status reporting.Views and Beyond organizes architecture into several views so no single diagram has to do everything at once. This makes it possible to choose the representation that fits the stakeholder's question.ATAM helps teams weigh architecture decisions when quality goals compete. The team considers business goals, stakeholder expectations, and technical decisions together. The evaluation shows which risks need further investigation.
Complexitydifferent
HighLowMediumHigh
Timedifferent
Mehrere Wochen30 min Setup, dann laufend1-3 TageSeveral meetings plus preparation and analysis; total effort depends on scope
Participantsdifferent
2-6 researchers plus sample1-3 maintaining, briefing for everyone1-4Evaluation team, architects, and relevant stakeholders
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Desired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesRAID Log, Status Report SourceArchitecture Views, Cross-view Notes, RationalePrioritized quality scenarios in a utility tree, Architecture risks with reasoning and assumptions, Sensitivity and trade-off points, Findings report with open investigations
Tagsno overlap
OutcomesInnovationResearchQuantitative
RiskTrackingStakeholdersGovernance
DocumentationStakeholdersArchitecture
ArchitectureQualityRiskTradeoffsStakeholders
Add more methods