View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Systems Thinking Intervention Mapping | ![]() Architecture Request for Comments | ![]() Decision Making Decision Rights Mapping | ![]() Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | Intervention Mapping translates a need for change into a planned, evaluable program. The method connects target group, determinants, actions, and measurement into a traceable chain. | 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 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. | In change initiatives, supporting and restraining forces sit at the table at the same time. Force Field Analysis makes these tensions explicit and shows where change can be pushed forward by strengthening or relieving. |
Complexitydifferent | High | Medium | Medium | Low |
Timedifferent | 1-5 Tage | 1-3 Wochen vom Draft bis zur Entscheidung | 90-180 min | 45-90 min |
Participantsdifferent | 4-12 | 3-20 Reviewer | 4-12 | 3-12 |
Formatdifferent | Workshop + async | Async | Workshop | Workshop |
Outputdifferent | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | RFC document, Reviewer comments, Decision rationale, Follow-up ADR or tickets | Decision Rights Matrix, Agreement | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | ChangeSystems thinkingCapability | ArchitectureDecisionAsyncGovernance | DecisionGovernanceAlignmentResponsibility | ChangeDecisionStrategy |



