1. Training as a System Intervention

🎯 Learning Outcomes	📍 Guiding Questions
Describe training as an intervention within a broader system Identify key elements of the system your training operates in (actors, resources, constraints, influences)	What system does your training sit within, and who are the key actors? What factors outside your control could affect success?

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 be honest about 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 zero 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 your system is to draw it. Start by placing your training at the centre of a simple diagram. Around it, add every person, organisation, or resource that affects whether it succeeds. Draw lines to show relationships — who depends on whom, what flows where.

Look for three things in particular:

Clusters — where several actors depend on the same resource (a single funder, a shared platform, one key coordinator). These are fragile points.
Gatekeepers — people or institutions that sit between your training and its intended impact. A line manager who won't release staff for training. A policy that prevents learners from applying new methods.
Missing connections — actors who should be linked but aren't. If your training produces skilled graduates but nobody connects them to job opportunities, the chain breaks.

A common trap

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 on climate data analysis for community organisers across three rural districts. The organisers work for local NGOs and have strong relationships with farming communities, but limited experience with data tools.

The team's first instinct is to build a workshop around the data analysis software they use in their own research. 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, via local observation. This existing knowledge is an asset, not a gap to fill. Third, the organisers' managers expect immediate, practical outputs: tools their teams can use in the field next season, not academic skills that pay off over years.

These discoveries change every design decision. The team shifts from teaching their preferred software to building the workshop around offline-capable tools that integrate with the data collection practices organisers already use. They restructure the agenda so organisers contribute their local data as working material — making the training immediately relevant rather than abstract. And they move from an instructor-led format to a co-design model, recognising that the organisers understand their communities far better than the research team does.

The result is a training programme that participants can apply the day they return to work, and that other districts can adapt 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 didn't change — but their design decisions improved dramatically 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.