methodatlas
Compare

View methods side by side.

Choose up to four methods. Add them using the search and share the comparison by copying its link.

Criterion
Paper illustration for Intervention Mapping.
Systems Thinking
Intervention Mapping
Four paper stations connect system purpose, quality goals, risk cards and focused investigation with a target and gap profile.
Architecture
LASR (Lightweight Approach for Software Reviews)
Paper illustration for Knowledge Mapping.
Knowledge Modeling
Knowledge Mapping
Systems Mapping method illustration showing its working structure
Systems Thinking
Systems Mapping
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.LASR helps development teams identify where their software falls short of important quality goals and which improvements to consider. A small group with existing system knowledge can make an initial assessment and investigate open questions in more detail.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.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.
Complexitydifferent
HighMediumMediumMedium
Timedifferent
1-5 Tage3–4 h for initial assessment; preparation and deeper analysis additional1-3 h1-3 h
Participantsdifferent
4-121 or a small team; particularly suitable for 3–4 people3-123-12
Formatdifferent
Workshop + asyncWorkshop + asyncWorkshopWorkshop + async
Outputdifferent
Logic Model, Change Objectives, Intervention Components, Evaluation PlanLean Mission Statement describing the software’s purpose, Prioritized quality goals and evaluation criteria, Risks and estimated gaps against quality goals, More closely examined findings and open checksKnowledge Map, Critical Knowledge Areas, Transfer PlanSystem Map, Dependencies, Leverage Points
Tagsno overlap
ChangeSystems thinkingCapability
ArchitectureQualityRiskAssessmentLean
KnowledgeMappingRisk
Systems thinkingMappingBoundariesChange
Add more methods