Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Selected:Argument Mapping Request for Comments Team Topologies Interaction Modes Decision Rights Mapping

Criterion	Decision Making Argument Mapping	Architecture Request for Comments	Team Design Team Topologies Interaction Modes	Decision Making Decision Rights Mapping
Purposedifferent	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.	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.	When several teams collaborate repeatedly, it describes the right interaction mode for each interface between them. It clarifies responsibility, interaction, and load between teams. The result is captured as an interaction heat map and pairwise agreements.	In organizations with many stakeholders, it often blurs who actually decides and who is merely consulted. It separates options, evaluation criteria, and open risks. The result is captured as a Decision Rights matrix and an agreement.
Complexitysame	Medium	Medium	Medium	Medium
Timedifferent	1-3 h	1-3 Wochen vom Draft bis zur Entscheidung	Half day	90-180 min
Participantsdifferent	1-8	3-20 Reviewer	Team-Leads plus Architecture	4-12
Formatdifferent	Workshop + async	Async	Workshop	Workshop
Outputdifferent	Argument Map, Evidence Gaps, Decision Rationale	RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets	Interaction Heat Map, Agreements per Pair	Decision Rights Matrix, Agreement
Tagsno overlap	SensemakingDecisionRationale	ArchitectureDecisionAsyncGovernance	TeamAlignmentCollaborationOrganization	DecisionGovernanceAlignmentResponsibility

Add more methods