Systems Mapping

Issues maps present key (ecosystem) issues affecting the complex problem. These are often the first or second system map to be developed in the lab process. You may sometimes hear people refer to them as 'brain dump' maps.

Issues maps help to:

Identify key issues, contributing issues, and drivers in the system
Surface how partners and stakeholders prioritize issues, and their assumptions of what is important
Surface potential gaps of understanding
Form preliminary mental models of grouping issues in the system
Identify potential points of focused research and ways to frame the problem/challenge

Tips for Issues Mapping:

Start with a well-defined scope that is understood by everyone participating in the issues mapping, e.g. keeping in mind scope of constituencies, geography, time etc.
Use an externalities or trends framework to help stimulate ideas, e.g. STEEPV (Social, Technological, Environmental, Economic, Political, Values), PESTLE (Political, Ecological, Socio-Cultural, Technological, Economic, Legal), or VUCA (Volatility, Uncertainty, Complexity and Ambiguity)
Focus on generating useful questions not solutions
Focus on uncovering shared understanding and surfacing disagreement, not right or wrong answers

Instructions: How to conduct an issues map

1) Identify the challenge statement Write down the challenge statement for your complex problem in the centre of a worksheet/flipchart. Try to be concise, but not too narrow in your description (defining the right problem scope is important in not going too broad or too narrow).

You can refer to the 'Challenge Statements' section to assist you with this process.

2) Identify key issues Brainstorm and describe the key issues that affect/contribute to that challenge. Make it concise. 3) Identify potential drivers Discuss what the drivers are behind each key issue. Write each driver down on the map. 4) Team discussion Discuss the relationships between key issues and drivers with your team, by drawing lines and linkages between them. Drivers can be linked to multiple issues. Identify any possible sub-issues that contribute to your problem but are not on the map yet. Write them down on the map and connect them with key issues and/or drivers. Try to be clear on how certain you are about the relationships and linkages, how strong (and resistant to change) they are.

Mind maps can help us identify key ideas, and organize them. They help us see a group of ideas in a hierarchy that also shows their relationships with one another. This is a useful visual tool for brainstorming and validating understanding of the system. Preliminary issues maps are often created or discussed as mind maps.

For more information on mind mapping you can visit:

Actor maps show which individuals and/or organizations are key players in the space, how they influence the problem and one another. They are often the second type of system map a lab will develop.

Actor maps help us answer the questions of who has influence on the problem, who is impacted by the problem, what changes to which influences might help solve the problem.

Actor maps provide data for stakeholder mapping. Stakeholder maps help us answer the questions of who is important to the success of solving the problem, how and when we need to engage them. For more information on stakeholder mapping click the link below:

You may sometimes see actor maps and stakeholder maps mentioned interchangeably. Strictly speaking, they have different purposes and answer different questions.

See the FSG Guide to Actor Mapping for steps in developing an actor map:

A system journey map shows how different users and stakeholders experience the system through multiple possible pathways. System journey maps help to:

Uncover and build shared mental models about how and why users perceive and experience a system differently, where the system's objectives are supported, and where they are not.
Surface key assumptions, potential gaps of understanding and uncertainties about user and stakeholder behaviours.
Identify opportunities for further investigation into gain creators, pain relievers, barriers or gaps.

A user journey map shows the experience of a user through one particular pathway of using a service or product. These maps are rich in information, showing multiple dimensions of the user experience at each touchpoint on the journey. You can read more about user journey maps in the Design Research section:

Value chain maps focus on where and how value is created, extracted and destroyed in the system. They also:

Identify key actors, conditions and issues
Model how the actors, conditions and issues, and their connections affect the value chain
Surface key assumptions, potential gaps of understanding and uncertainties
Identify potential points of intervention and levers of change

See more about Value Chains in the link below:

Or here, on Global Value Chains:

Causal loop diagrams focus on explicating the feedback loops (positive and negative) that lead to system behavior or functioning.

For more on causal loop diagrams, visit:

Stock and flow diagrams model the causal structures that produce behaviors, or the system dynamics. They are the foundations of simulating or modeling systems.