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
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Paper illustration of Outcome-Driven Innovation with its method-specific working model.
Product Discovery
Outcome-Driven Innovation
Paper illustration for DACI
Decision Making
DACI
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
arc42 structures architecture knowledge so teams can document system, decisions, and risks consistently. The template builds a living understanding of the architecture instead of scattered notes.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.In cross-functional decisions, responsibilities quickly blur between approval, influence, and execution. DACI arranges these roles so decision pressure, contribution, and information stay cleanly separated.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
1-2 TageMehrere Wochen30-60 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-42-6 researchers plus sample2-103-20 Reviewer
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshop + asyncAsync
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewDesired outcome statements, Opportunity landscape, Segmentation by underserved needs, Innovation hypothesesDACI Matrix, Decision Owner, Decision LogRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
ArchitectureDocumentationCommunication
OutcomesInnovationResearchQuantitative
DecisionRolesGovernanceAlignment
ArchitectureDecisionAsyncGovernance
Add more methods