View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion | ![]() Product Strategy Impact Mapping | ![]() Decision Making Force Field Analysis | ![]() Architecture C4 Model | ![]() Delivery Communication Plan |
|---|---|---|---|---|
Purposedifferent | When a goal needs to be connected to several possible paths, it shows chains of impact instead of feature lists. It connects business goal, behavior change, and measures. | 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. | The C4 Model makes a system legible across several resolution levels, from context down to code. It suits situations where different audiences need to understand the same architecture from different altitudes. | When many people need to be informed in parallel and messages would otherwise arrive unevenly or too late, a Communication Plan orders communication reliably. Channels, audiences, and cadences interlock so important information doesn't get lost. |
Complexitydifferent | Medium | Low | Low | Low |
Timedifferent | 45-90 min | 45-90 min | 1-4 h | 45-90 min |
Participantsdifferent | 3-8 | 3-12 | 1-5 | 2-6 |
Formatdifferent | Workshop | Workshop | Workshop + async | Workshop + async |
Outputdifferent | Impact Map, Outcome Hypotheses, Delivery Options | Force Field Map, Change Levers, Risk Notes | Context Diagram, Container Diagram, Component Diagram | Communication Plan, Channel Matrix, Message Cadence |
Tagsno overlap | OutcomesStrategyBehaviorPlanning | ChangeDecisionStrategy | ArchitectureCommunicationVisualization | CommunicationStakeholdersDeliveryPlanning |



