Participatory Systems Mapping
A method in which stakeholders discuss factors and connections to map a system, organizing different perspectives, possible interventions and questions for evaluation. [1]
- Difficulty
- Advanced
- Cost
- Medium
- Duration
- Planning example, not a universal standard duration: half a day–2 days, including design, workshop and synthesis
How it works at a glance
Define the purpose and scope, then map changing factors and causal links with affected people and those knowledgeable about field practice and policy. Participant selection shapes which perspectives appear. [1]
Discussion of links and differing views are themselves learning opportunities. Maps are not necessarily empirically demonstrated causal models, so distinguish evidence from hypotheses and turn important links into research questions for updating. [1]
- Define the map's focus
- Identify factors
- Connect causal links
- Examine loops and leverage points
- Develop evaluation questions
- Update the map
When to use it and when it is unsuitable
When to use it
- When complex community issues or policies do not have a single linear outcome pathway
- When stakeholder perspectives differ and a shared understanding of the problem structure is needed
- When including unintended effects, external factors and interactions in evaluation design
- When examining a wider system before developing a logic model or theory of change
When it is unsuitable
- For short, simple programs with clear input-to-outcome pathways
- When strong conflict or power differences prevent open discussion in the same forum
Participants, roles, and deliverables
Participants and roles
Participants representing affected people, field practice, relevant organizations and policy, with a facilitator. Adjust numbers for diverse perspectives and ease of dialogue.
Main deliverables
- Systems map
- Important loops and intervention points
- Candidate evaluation questions
Implementation steps
- Define the map's focusDecide which system to map, its boundaries and the time horizon.
- Identify factorsInvite participants to identify a broad range of factors related to change, including outcomes, behavior, institutions, resources, psychology and environment.
- Connect causal linksDraw links showing how factor A increases or decreases factor B. Mark weakly supported links as hypotheses.
- Examine loops and leverage pointsIdentify reinforcing and balancing loops, bottlenecks and factors where influences concentrate. Distinguish readily changeable factors from structural ones.
- Develop evaluation questionsSet questions and indicators to check whether important links and loops actually operate.
- Update the mapReflect evaluation and monitoring evidence and revise hypothetical links. Do not treat the map as a fixed deliverable.
Strengths and limitations
Strengths
- Incorporates complex interactions and unintended effects into evaluation design.
- Makes stakeholders' tacit knowledge visible and develops shared understanding.
- Derives candidate evaluation questions and indicators from system structure.
- Useful for adaptive operation when combined with developmental evaluation or theory of change.
Limitations
- Maps are hypotheses based on participant perceptions, not reality itself.
- Weak facilitation can bias maps toward the loudest participants.
- Excessively complex maps become unusable in practice.
Common pitfalls
- Making attractive diagrams the goal without developing evaluation questions
- Adding so many factors that it becomes unclear where to focus
- Ignoring power differences and preventing honest discussion
Conditions of use and evidence
- Specify boundaries and participants, retain differing views and keep the map open to updating. [1]
Select questions from a chain of absences
A fictional illustrative workshop record considering participation in learning support.
Scroll horizontally to view the table
| Connections between factors | Participant hypothesis | Next check |
|---|---|---|
| Travel burden → participation frequency | Higher burden reduces participation. | Interviews about reasons for absence |
| Participation frequency → sense of security | Continued participation makes asking questions feel safe. | Personal accounts and observation |
| Sense of security → participation frequency | Feeling safe supports continued participation. | Participation records over time |
Common errors in judgment
Calling map arrows established causal relationships
How to revise
Distinguish links based on hypotheses, lived accounts and records.
ReasonParticipant perceptions alone cannot establish causal effects.
Assuming representatives alone cover everyone's perspectives
How to revise
Identify missing perspectives and add participants or interviews.
ReasonThe map's scope depends on participants' experiences.
References and checked sections
- How to design a Participatory Systems Mapping processAlexandra Penn/Pete Barbrook-Johnson · 2022
- Section consulted
- System definition/boundary; Choosing Stakeholders; Mapping Process; Analysis Design
- How it relates to the text
- Specify boundaries and participants, retain differing views and keep the map open to updating.
Editorial and checking information
How to cite this page
Change history
- — Checked sources for definitions and applicability conditions, and added fictional examples, reasons for judgments and examples for every worksheet field. Revised unverified claims about history and adoption. Also reviewed existing procedures and cautions, and adjusted fixed participant counts and thresholds and generalizations about institutions.


