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 Strategy Execution Loop with its method-specific working model.
Business Strategy
Strategy Execution Loop
Paper illustration for Failure Mode and Effects Analysis
Operations
Failure Mode and Effects Analysis
Paper fishbone diagram with a measurable effect at the head and six labeled cause branches.
Operations
Fishbone Diagram
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.The Strategy Execution Loop helps avoid treating strategy as a one-off document. It makes visible how strategic decisions are turned into objectives, initiatives, operational work, measurement, and learning.For a process, product, or service with noticeable failure risks, the method assesses possible failure modes in advance. It directs attention to combinations of occurrence, effect, and detectability.When a problem has several possible contributing factors, the method sorts causes by cause areas. It prevents an initial hunch from blocking the view of other plausible drivers.
Complexitydifferent
LowHighHighLow
Timedifferent
1-2 TageInitial 3-6 h, then monthly or quarterly reviews2-6 h30-60 min
Participantsdifferent
1-45-123-102-8
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop
Outputdifferent
Architecture Document, Context View, Runtime View, Deployment ViewExecution Loop, Review Cadence, Strategic Learning LogFMEA Table, Risk Priority, Mitigation ActionsFishbone Diagram, Cause Categories, Investigation Backlog
Tagsno overlap
ArchitectureDocumentationCommunication
ExecutionCadenceLearningGovernance
RiskQualityOperationsRoot cause
Root causeQualityOperations
Add more methods