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 Systems Mapping |  Agile Ideal Days |  Systems Thinking Intervention Mapping |  Agile Planning Poker |
|---|---|---|---|---|
Purposedifferent | Systems Mapping arranges elements, relationships, and boundaries so a complex field becomes legible at a glance. The overview stabilizes the overall picture before detail work or steering begins. | When effort needs to be thought of as real working time, it offers a simple common denominator for comparison. It sorts work by value, risk, and delivery ability. The result is captured as Ideal Day Estimates, Assumption Notes, and Capacity Caveats. | 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. | When estimates within the team diverge too much, it puts differing expectations on a common test bench. It separates rough complexity from unspoken assumptions. |
Complexitydifferent | Medium | Low | High | Low |
Timedifferent | 1-3 h | 15-60 min | 1-5 Tage | 2-5 min je Item |
Participantsdifferent | 3-12 | 2-9 | 4-12 | 3-9 |
Formatsame | Workshop + async | Workshop + async | Workshop + async | Workshop + async |
Outputdifferent | System Map, Dependencies, Leverage Points | Ideal Day Estimates, Assumption Notes, Capacity Caveats | Logic Model, Change Objectives, Intervention Components, Evaluation Plan | Relative Estimates, Assumption Notes, Split Candidates |
Tagsno overlap | Systems thinkingMappingBoundariesChange | EstimationEffortAgile | ChangeSystems thinkingCapability | EstimationAgileRelative sizingTeam |