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 Context Canvas with its core stages and visible working result.
Product Discovery
Context Canvas
Paper illustration of many question cards around one challenge
Facilitation
Question Burst
Paper illustration of two considered options leading to a decision record with a marked status and visible consequences.
Architecture
Architecture Decision Record
A paper-based illustration representing arc42 with its core stages and visible working result.
Architecture
arc42
Purposedifferent
When an environment of users, systems, and constraints is hard to grasp, it puts the context compactly on the table. It creates a clear reading of influence, boundary, and dependency.When a problem gets covered up too quickly with answers, Question Burst puts the better question at the center. The format opens the thinking space before the group commits to an interpretation.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.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.
Complexitysame
LowLowLowLow
Timedifferent
45-90 min15-30 min15-45 min1-2 Tage
Participantsdifferent
3-102-81-31-4
Formatdifferent
WorkshopWorkshopAsyncWorkshop + async
Outputdifferent
Context canvas, Open questions, Shared context notesQuestion List, Reframed Challenge, Learning PromptsADR File, Decision Log, RationaleArchitecture Document, Context View, Runtime View, Deployment View
Tagsno overlap
ContextFramingRequirementsCanvas
QuestionsReframingFacilitationSensemaking
ArchitectureRationaleDocumentationGovernance
ArchitectureDocumentationCommunication
Add more methods