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 Weekly Review.
Operations
Weekly Review
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.In a week with many open loops, the method creates distance from operational noise. It organizes commitments, calendar, and projects so the next week becomes workable.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 Entscheidung30-60 min1-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 ticketsUpdated Task System, Weekly Focus, Next ActionsArgument Map, Evidence Gaps, Decision RationaleConstraint List, Hard/Soft Classification, Option Impact Notes, Decision Boundaries
Tagsno overlap
ArchitectureDecisionAsyncGovernance
ProductivityExecutionPlanning
SensemakingDecisionRationale
ConstraintsDecisionPlanningOptions
Add more methods