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
Gap Analysis method illustration showing its working structure
Business Strategy
GAP Analysis
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 Product Vision Board with its method-specific working model.
Product Strategy
Product Vision Board
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
GAP Analysis compares the current state with a target picture and makes the distance manageable. It becomes useful when, ahead of new initiatives, it must become clear which capabilities, processes, or resources are missing.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.When a product needs a shared direction, it connects target audience, benefit, and business picture in a clear vision. It makes the envisioned future legible for the team.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.
Complexitydifferent
MediumLowLowLow
Timedifferent
1-3 h15-45 min1-2 h1-2 Tage
Participantsdifferent
2-81-32-81-4
Formatdifferent
Workshop + asyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
Gap Matrix, Action Plan, Risk NotesADR File, Decision Log, RationaleProduct Vision Board, Vision Statement, Assumptions and Validation QuestionsArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
StrategyAnalysisPlanning
ArchitectureRationaleDocumentationGovernance
VisionCanvasStrategyAlignment
ArchitectureDocumentationCommunication
Add more methods