System map
What
A diagram that shows how different factors and forces affect a given system. This is unlike journey maps or service blueprints, which visualize specific services.
Why
Mapping complex patterns can help us build consensus and identify opportunities. Maps can also be used to onboard new team members and inform product decisions.
How to do it
- Choose a sketching app or gather pen and paper.
- Identify the problem you want to focus on and the specific questions you want to visualize in a system. For example, what health food options currently exist in a community?
- Identify the people affected by this problem. Invite them to engage in the following steps.
- Identify data sources to create your system map. Your sources may come from engaging with people most affected by the problem, looking at secondary data, or conducting other qualitative research.
- Draw arrows between the different parts of your system to identify how they’re connected.
- Reflect on specific areas to examine more closely. What questions come up? What gaps do you see?
- Share the map with others and invite them to add to it. Include people affected by the problem, key stakeholders, and subject matter experts.
- Update the map as you learn more about the problem.
Additional resources
- The VA Community Playbook, pages 12 and 13, The Department of Veterans Affairs
- Example systems map, gov.uk
- An introductory systems thinking toolkit for civil servants, gov.uk
- A brief overview of systems mapping, gov.uk
Considerations for use in government
No PRA implications. Even when users are present, the PRA explicitly exempts direct observation and non-standardized conversation, 5 CFR 1320.3(h)3. If you are not working with government employees, you will need to observe standard precautions for archiving personally identifiable information.