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
Paper illustration of Request for Comments (RFC) with its method-specific working model.
Architecture
Request for Comments
Paper illustration for Time Blocking
Operations
Time Blocking
Paper illustration for Argument Mapping
Decision Making
Argument Mapping
Paper illustration for Constraint Analysis.
Decision Making
Constraint Analysis
Purposedifferent
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.With a calendar that grows on request, the method makes available time explicit again. It combines appointments, focus work, and buffer into a more realistic day structure.When statements, evidence, and counterarguments get mixed up, a debate quickly loses its structure. Argument Mapping breaks a thesis down into its reasoning and makes visible what it really rests on.When an initiative stalls, the limit often lies not in the idea but in hard or soft boundary conditions. Constraint Analysis separates these limits and shows which of them can actually be shaped.
Complexitydifferent
MediumLowMediumLow
Timedifferent
1-3 Wochen vom Draft bis zur Entscheidung15-30 min Planung, laufend1-3 h30-90 min
Participantsdifferent
3-20 Reviewer11-82-8
Formatdifferent
AsyncAsyncWorkshop + asyncWorkshop + async
Outputdifferent
RFC document, Reviewer comments, Decision rationale, Follow-up ADR or ticketsBlocked Calendar, Capacity View, Focus PlanArgument Map, Evidence Gaps, Decision RationaleConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
ArchitectureDecisionAsyncGovernance
PlanningTime managementFocus
SensemakingDecisionRationale
ConstraintsDecisionPlanningOptions
Add more methods