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 two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
A paper-based illustration representing C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
An ADR permanently records an architecture decision with context, trade-offs, and consequence. It creates continuity for later changes because the decision path stays traceable.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.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.An RFC clarifies architecture context, options, and consequences. It structures technical context, alternatives, tradeoffs, open questions, and review feedback, and captures the result as an RFC document, reviewer comments, and a decision rationale.
Complexitydifferent
LowHighLowMedium
Timedifferent
15-45 minMehrere Wochen1-4 h1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-32-6 researchers plus sample1-53-20 Reviewer
Formatdifferent
AsyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
ADR File, Decision Log, RationaleDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesContext Diagram, Container Diagram, Component DiagramRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ArchitectureRationaleDocumentationGovernance
OutcomesInnovationResearchQuantitative
ArchitectureCommunicationVisualization
ArchitectureDecisionAsyncGovernance
Add more methods