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
Six paper cards show a person moving from a problem through a service flow to a completed outcome.
UX Design
Storyboarding
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Purposedifferent
When a usage scenario needs to become understandable early, it condenses situations, context, and flow into a legible sequence. It helps check concept ideas before anything gets built.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.
Complexitysame
MediumMedium
Timedifferent
30-90 min1-3 Wochen vom Draft bis zur Entscheidung
Participantsdifferent
1-83-20 Reviewer
Formatdifferent
Workshop + asyncAsync
Outputdifferent
Storyboard, Concept Narrative, Testable AssumptionsRFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets
Tagsno overlap
VisualizationConceptsSequencePrototype
ArchitectureDecisionAsyncGovernance
Add more methods

Often compared together

Methods with strong topical overlap with the current selection, not yet in the comparison.

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 C4 Model with its core stages and visible working result.
Architecture
C4 Model
Paper illustration of Decision Rights Mapping with its method-specific working model.
Decision Making
Decision Rights Mapping