1. Training as a System Intervention
| 🎯 Learning Outcomes | 📍 Guiding Questions |
|---|---|
|
|
Picture a workshop you've attended — or one you've run. Now zoom out. Who funded it? What happened before participants arrived? What happened after they left? Did the environment they returned to support or undermine what they learned? And most importantly, did it make a difference?
This lesson is about that bigger picture. Before you design content, activities, or assessments, you need to understand the system your training lives in — and consider what training alone can and cannot change.
Why this matters¶
It's tempting to start designing training by asking "What should I teach?" That question feels productive, but it skips something important: understanding the conditions that will determine whether your training actually leads to change.
Training doesn't happen in a vacuum. It happens inside organisations, communities, and funding structures. Participants arrive with existing knowledge, constraints on their time, and environments that may or may not support what they learn. A perfectly designed workshop can have limited lasting impact if the system around it works against the change you're hoping for.
The real question
Not "What should I teach?" but "What change is possible in this system — and how can training contribute?"
When you understand the system first, you make better design decisions: what to include, what to leave out, how ambitious to be, and where to invest your limited time.
Understanding your training as part of a system¶
Training as an intervention
Training is a deliberate action intended to contribute to change — but it only works in relation to the wider system around it.
Training can introduce new knowledge, build skills, create space for practice, or shift how people think about a problem. But whether any of that leads to lasting change depends on factors beyond the training itself: whether learners have time to apply what they learn, whether their institutions support new approaches, whether funding continues, whether the right people are in the room.
This is what it means to think about training as an intervention in a system rather than a standalone event. A system, in this context, simply means the web of people, resources, relationships, constraints, and influences that surround your training — where "influences" means the external forces you don't control but need to account for, like policy changes, institutional incentives, or cultural norms. You don't control this system — but you need to understand it well enough to design something that can work within it.
Mapping your system¶
The best way to understand what will shape your training is to make it visible. Start by sketching your training in the centre of a page. Around it, add the people, organisations, and resources that will influence whether it works in practice. Draw simple lines to show relationships — who supports what, where decisions are made, what needs to be in place.
This doesn’t need to be formal. A rough sketch is enough.
As you map, look for patterns such as:
- Clusters — where several things rely on the same person, resource, or system (for example, one funder, one platform, or one coordinator). These are often points of dependency risk.
- Gatekeepers — people or structures that can enable or block what happens next (for example, a line manager who controls time, or a policy that limits what can be applied).
- Gaps — where something important is missing or not connected (for example, training builds skills, but there is no pathway to use them).
This kind of mapping helps you see early where your training is likely to hold, where it may struggle, and where small adjustments could make a significant difference.
A common pitfall
It's easy to map only the people directly involved in delivery — trainers, learners, maybe a funder. But the actors who most affect long-term impact are often further out: the managers learners report to, the communities they serve, the policies they work under. Push your map beyond the obvious.
A worked example: climate data training¶
A team at an environmental research institute is asked to design training to help community organisers make better use of weather and crop information in their work across three rural districts. The organisers work for local NGOs and have strong relationships with farming communities, but limited experience with formal data tools.
The team’s first instinct is to build a workshop around the data analysis software they use in their own research — assuming the need is primarily technical. But when they map the system, they discover several things that reshape their design.
First, internet access across the three districts is unreliable. Two of the three locations have no consistent connectivity, which rules out cloud-based tools. Second, the community organisers already collect weather and crop data informally — in notebooks, through conversations, and through local observation. This existing knowledge is an asset, not a gap to fill. Third, the organisers’ managers expect immediate, practical outputs: approaches their teams can use in the field next season, not skills that may only become useful over time.
These discoveries change every design decision. The team shifts from teaching their preferred software to working with offline-capable tools that fit into existing practices. They restructure the workshop so organisers bring their own data and use it as the basis for activities — making the training immediately relevant rather than abstract. They also move from an instructor-led format to a more collaborative approach, recognising that the organisers understand their contexts far better than the research team does.
The result is a training programme that participants can apply as soon as they return to their work, and that can be adapted in other districts without depending on the original team.
Notice what made this work: not better content, but better understanding of the system. The team’s expertise in climate data did not change — but their design decisions improved significantly once they understood the constraints, resources, and relationships around the training.
In practice¶
You've seen how system mapping works to reveal the conditions your training operates in. It's time to apply this to your own context.
👉 Activity 1: System Map — Map the actors, resources, constraints, relationships, and influences that surround your training. This gives you the foundation for every design decision that follows.
Key takeaways¶
Key takeaway
Training works within systems. Its success depends on context — not only content. Map the system before you design the training.
Before you move on¶
You should now have:
- a system map showing the actors, resources, constraints, relationships, and influences around your training
- at least one cluster, gatekeeper, or missing connection you hadn't previously considered
This is a living document
Your system map will evolve as you work through the rest of this workbook — especially when you analyse your learners in Lesson 3 and revisit constraints in Lesson 6. Rework it whenever your thinking shifts.
Further reading (optional)¶
- Meadows, D. (2008) — Thinking in Systems: A Primer
- Supports: systems thinking and understanding training as part of a broader system
- Why it matters: provides practical tools for mapping actors, constraints, and system dynamics — directly applicable to the system mapping method in this lesson
- Source: https://research.fit.edu/media/site-specific/researchfitedu/coast-climate-adaptation-library/climate-communications/psychology-amp-behavior/Meadows-2008.-Thinking-in-Systems.pdf