View methods side by side.
Choose up to four methods. Add them using the search and share the comparison by copying its link.
| Criterion |  Agile Story Splitting |  Systems Thinking Leverage Points |  Domain Modeling Context Map |  Decision Making Force Field Analysis |
|---|---|---|---|---|
Purposedifferent | When a story becomes too large for a clean flow, it breaks scope down along value and risk. It shapes the work into a form that ships earlier and is easier to verify. | Leverage Points show exactly where interventions in a system produce a disproportionate effect. It draws relationships, patterns, and feedback loops. The result is captured as a leverage map and action strategy. | When several contexts need to talk to each other, it makes their relationships and dependencies legible. It helps sort integration pressure and responsibilities across system boundaries. | 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 | Medium | High | Medium | Low |
Timedifferent | 30-60 min | Half day | 1-3 h | 45-90 min |
Participantsdifferent | 2-6 | 3-12 | 2-8 | 3-12 |
Formatdifferent | Workshop + async | Workshop | Workshop + async | Workshop |
Outputdifferent | Smaller Stories, Acceptance Criteria, Split Rationale | Leverage Map, Action Strategy | Context Map, Integration Patterns, Boundary Notes | Force Field Map, Change Levers, Risk Notes |
Tagsno overlap | BacklogIterationDelivery | Systems thinkingChangeStrategy | Domain-Driven DesignBoundariesStrategy | ChangeDecisionStrategy |