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 Ideal Days |  Systems Thinking Systems Mapping |  Knowledge Modeling Knowledge Mapping |  Systems Thinking Intervention Mapping |
|---|---|---|---|---|
Purposedifferent | 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. | 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. | Knowledge Mapping makes knowledge, gaps, and transfer paths visible across a field. It fits when expertise should not just exist but also be findable and transferable. | 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. |
Complexitydifferent | Low | Medium | Medium | High |
Timedifferent | 15-60 min | 1-3 h | 1-3 h | 1-5 Tage |
Participantsdifferent | 2-9 | 3-12 | 3-12 | 4-12 |
Formatdifferent | Workshop + async | Workshop + async | Workshop | Workshop + async |
Outputdifferent | Ideal Day Estimates, Assumption Notes, Capacity Caveats | System Map, Dependencies, Leverage Points | Knowledge Map, Critical Knowledge Areas, Transfer Plan | Logic Model, Change Objectives, Intervention Components, Evaluation Plan |
Tagsno overlap | EstimationEffortAgile | Systems thinkingMappingBoundariesChange | KnowledgeMappingRisk | ChangeSystems thinkingCapability |