Chapter 37: Systems Mapping in Practice

Chapter Overview

This chapter bridges the theoretical foundations of systems thinking (Chapter 5) with the practical work of analysis and interpretation. It walks you through specific methods for mapping community systems: causal loop diagrams, stock and flow models, service ecosystems, power structures, stakeholder relationships, and networks. The goal is not to produce perfect diagrams but to develop habits of systems thinking that reveal leverage points, interdependencies, and opportunities for intervention. Every method here has been used in real community mapping work — by planners, advocates, researchers, and communities themselves.

Learning Outcomes

By the end of this chapter, you will be able to:

Apply causal loop diagramming to map feedback loops in community issues
Distinguish stocks from flows and model them in simple systems diagrams
Map service ecosystems to reveal coordination patterns and gaps
Identify and visualize power structures in community decision-making
Construct stakeholder relationship maps for a real initiative
Analyze network maps to identify central actors, clusters, and weak ties
Recognize Meadows-style leverage points in real community systems
Validate systems maps through triangulation and participant feedback

Key Terms

Causal Loop Diagram (CLD): A systems visualization showing how variables influence each other in circular feedback relationships.
Stock: An accumulation or reservoir within a system (e.g., population, trust, housing supply).
Flow: A rate of change that adds to or drains a stock (e.g., births, investment, housing construction).
Service Ecosystem: The network of organizations, resources, referral pathways, and relationships that deliver services to a community.
Power Mapping: A method for identifying who holds decision-making authority, influence, and control over resources in a community system.
Leverage Point: A place in a system where a small intervention can produce large, lasting change.

37.1 From Inventory to System

Community mapping often begins with inventory: counting services, listing assets, documenting needs. This work is essential. You cannot analyze what you have not identified. But inventory alone does not reveal how things connect.

A map showing twenty social service agencies in a neighborhood answers one question: What exists? It does not answer: How do these agencies work together? Where do clients get stuck? What happens when one closes? Who coordinates? Who competes for funding? Where are the bottlenecks?

Systems mapping picks up where inventory ends. It asks: What are the relationships? What are the feedback loops? Where does information flow? Where does power sit? What reinforces current patterns? What could shift them?

The shift from inventory to systems thinking is not just methodological — it is conceptual. Inventory treats elements as independent. Systems thinking treats them as interdependent. A youth center is not just a dot on a map. It is connected to schools, to transit routes, to funding streams, to staff capacity, to youth networks, to municipal policies. Change one element, and ripples spread.

This does not mean inventory is obsolete. Inventory provides the raw material for systems analysis. You cannot map the service ecosystem if you do not know which services exist. You cannot map power structures if you have not identified the decision-makers. Inventory and systems mapping are partners, not rivals.

The work ahead in this chapter is practical. We will walk through six core methods for systems mapping, each grounded in real practice. You do not need specialized software, though it can help. You need pen, paper, a willingness to ask "what connects to what?", and patience for iterative revision. Systems maps are never right on the first draft.

37.2 Causal Loop Diagrams

A causal loop diagram (CLD) is a visual representation of how variables influence each other in feedback loops. It is one of the most accessible and widely used tools in systems thinking, developed primarily through the work of Jay Forrester, Peter Senge, and the system dynamics tradition.

A CLD consists of variables (things that change) connected by arrows (causal links). Each arrow is labeled with a polarity: + (same direction) or – (opposite direction). A + link means that if the cause increases, the effect increases; if the cause decreases, the effect decreases. A – link means that if the cause increases, the effect decreases.

Loops are labeled R (reinforcing) or B (balancing). A reinforcing loop amplifies change — growth begets more growth, or decline begets more decline. A balancing loop resists change, pushing the system toward equilibrium or a goal.

Here is a simple example from community health. Suppose a neighborhood experiences an increase in chronic disease. This increases demand for primary care. But if primary care capacity is fixed, wait times increase. Longer wait times discourage people from seeking preventive care. Less preventive care increases chronic disease. This is a reinforcing loop — a vicious cycle.

Now add an intervention: the health authority funds more primary care clinics. Capacity increases, wait times fall, more people access preventive care, chronic disease rates drop. This intervention breaks the reinforcing loop and shifts the system toward a healthier equilibrium.

CLDs do not require precise numbers. They are qualitative tools for exploring structure and dynamics. They help you see where feedback operates, where delays exist, and where interventions might matter most.

Common pitfalls: CLDs can become cluttered quickly. Discipline is required to focus on key variables. A CLD with fifty variables is not useful. A CLD with six to ten well-chosen variables, clearly labeled, can illuminate a complex issue. Start simple. Add complexity only as needed.

Another pitfall: mistaking correlation for causation. Just because two variables move together does not mean one causes the other. CLDs should represent genuine causal relationships, supported by evidence or logic. If you are uncertain whether a link is causal, note the uncertainty and validate with data or expert input.

A well-constructed CLD makes system structure visible. It becomes a shared tool for discussion. Community groups can stand around a CLD, point to loops, debate which are strongest, and identify where intervention might shift the pattern. That conversation — grounded in structure, not anecdote — is the real value of the method.

37.3 Stock and Flow Models

Stocks and flows are foundational concepts in system dynamics, articulated clearly by Forrester and popularized by Donella Meadows in Thinking in Systems (2008).

A stock is an accumulation: population, housing units, trust, organizational capacity, pollution in a river, money in a budget. Stocks change slowly. They have inertia. They provide stability and memory to a system.

A flow is a rate of change that adds to or drains a stock: births and deaths (population), construction and demolition (housing), investment and burnout (organizational capacity), emissions and cleanup (pollution), revenue and spending (budget).

The relationship between stocks and flows is fundamental. If inflows exceed outflows, the stock grows. If outflows exceed inflows, the stock shrinks. If they balance, the stock stabilizes.

Stocks are often invisible in everyday discussion. People talk about "housing shortages" without asking: What is the current stock of housing? What is the rate of new construction (inflow)? What is the rate of demolition or conversion (outflow)? What is the rate of household formation (demand)? Without understanding stocks and flows, solutions misfire. A city builds 500 new units annually but loses 600 to demolition and conversion — and wonders why the shortage persists.

Here is a practical example. A community is concerned about the decline of local businesses. You begin by identifying the stock: number of locally owned businesses. Then you map the flows. Inflows: new business startups. Outflows: closures, buyouts by chains, owner retirements. What drives each flow? Startup inflows are influenced by access to capital, mentorship, affordable commercial space. Closure outflows are influenced by rent increases, competition, regulatory burden, economic downturns.

Once you map stocks and flows, you can ask: Where is the leverage? Should we increase inflows (support new startups)? Should we decrease outflows (stabilize rents, provide succession planning for retiring owners)? Should we do both? The stock-and-flow model clarifies the structure of the problem and the range of intervention points.

Stock-and-flow diagrams are visual: rectangles for stocks, arrows for flows, valves on arrows to indicate controllable flows. They can be sketched on paper or built in system dynamics software (e.g., Stella, Vensim). The sketched version is often sufficient for community mapping work. Precision matters less than clarity of structure.

Meadows' insight: stocks act as shock absorbers. A large stock (e.g., a deep reserve fund, a large inventory) allows a system to ride out fluctuations in flows. A small stock (e.g., no savings, tight housing supply) makes the system fragile. When you map community systems, pay attention to stock sizes. Where are the buffers? Where is the fragility?

37.4 Service Ecosystem Mapping

Service ecosystems are the networks of organizations, programs, referral pathways, funding streams, and relationships that deliver health, social, educational, recreational, and economic services to a community.

Mapping a service ecosystem answers questions like: Who provides what? Who collaborates? Who competes? Where do clients move between services? Where do they get stuck? Where are the coordination hubs? Where are the gaps?

A service ecosystem map is both a network map and a systems map. Nodes represent organizations or programs. Edges represent relationships: formal partnerships, referral pathways, shared clients, funding dependencies, information exchange. The map can include attributes: node size representing budget or capacity, edge thickness representing frequency of interaction, color coding by sector (health, housing, employment).

To build a service ecosystem map, start with inventory. List the organizations and programs serving a defined population or issue area (e.g., youth services, housing support, mental health). Then interview providers. Ask: Who do you refer clients to? Who refers to you? Who do you coordinate with? Who funds you? Who do you share data with? Compile the responses into a network dataset: rows listing organization pairs, columns indicating relationship type.

Visualize the network using network analysis software (e.g., Gephi, Cytoscape) or by hand for smaller ecosystems. Look for patterns. Are there central hubs that many organizations connect through? Are there isolated clusters that do not communicate with the broader system? Are there service domains where no coordination exists?

Service ecosystem mapping has practical applications. A funder can use it to identify coordination gaps and invest in backbone organizations. A municipal planner can use it to understand how services cluster geographically and where deserts exist. A coalition can use it to map who is missing from the table and invite them in.

Ethical note: service ecosystem mapping can reveal competition, mistrust, and power imbalances. Organizations may be reluctant to share information if they fear it will be used against them. Build trust before building the map. Clarify how the map will be used and who will see it. Offer to anonymize findings if necessary. The goal is coordination, not exposure.

37.5 Power Mapping

Power is a core dimension of community systems, and yet it is often left off the map. Power determines who makes decisions, who controls resources, who sets agendas, and whose voices are heard or ignored.

Power mapping is a method for making power visible. It asks: Who holds formal authority (elected officials, executives, board chairs)? Who holds informal influence (community leaders, wealthy donors, media figures)? Who controls resources (budgets, land, data)? Who sits at decision-making tables? Who is excluded?

There is no single canonical method for power mapping, but several practitioner traditions offer guidance. One well-documented approach comes from the organizing and advocacy world, including resources like the Beautiful Trouble toolkit. The basic structure is:

Identify the decision or issue. What are you trying to influence? A zoning decision? A budget allocation? A policy change? The map is issue-specific.
List the stakeholders. Who has a stake in this issue? Decision-makers, implementers, advocates, opponents, affected communities.
Assess power. For each stakeholder, evaluate: Do they have formal authority? Do they control resources? Do they have influence over those who hold authority? Do they have mobilization capacity (can they turn out supporters)?
Assess position. Are they supportive, neutral, or opposed to your goal? Are they moveable? What would shift their position?
Map relationships. Who influences whom? Who listens to whom? Are there alliances or rivalries?
Visualize. Common formats include a two-axis grid (power on one axis, support/opposition on the other), a network diagram showing influence relationships, or concentric circles with decision-makers at the center and others radiating outward by proximity to power.

Power mapping is strategic. It helps advocates identify whom to target, what messages to use, and where pressure points exist. It also exposes power imbalances that structural change efforts must address.

In community mapping contexts, power mapping can be combined with other forms of analysis. A service ecosystem map can be overlaid with a power map to show not just who coordinates but who holds funding authority. A stakeholder map can be overlaid with a geographic map to show where powerful actors live or operate.

Caution: power mapping can be politically sensitive. If you are mapping power to support community organizing, you may not want to share the map publicly or with those it critiques. Conversely, if you are mapping power for planning or research, you must handle findings carefully to avoid harming vulnerable actors or reinforcing stigma. Context and purpose determine what is appropriate.

37.6 Stakeholder Mapping in Action

Stakeholder mapping is closely related to power mapping, but its scope is broader. It identifies everyone with a stake in an issue or initiative, not just those with power. Stakeholders include affected residents, service users, community groups, businesses, institutions, government agencies, funders, researchers, advocates, and opponents.

A stakeholder map answers: Who cares? Who is affected? Who has influence? Who must be consulted? Who will support or resist? Who is missing from the conversation?

One widely used format is a stakeholder matrix. Columns include: stakeholder name, role or affiliation, interest in the issue, power or influence, current position (support/neutral/oppose), engagement strategy. Rows list all identified stakeholders. The matrix becomes a planning tool: who do we need to engage, when, and how?

Another format is a visual stakeholder map. Place the issue or initiative at the center. Arrange stakeholders around it, with proximity indicating degree of interest or impact. Use color or symbols to indicate support/opposition, power level, or relationship status.

Stakeholder mapping is iterative. The first draft is always incomplete. As you engage stakeholders, you learn about others. As you analyze relationships, you discover hidden alliances or tensions. The map evolves.

A case example: A municipality is developing a new parks master plan. The planner begins stakeholder mapping. Obvious stakeholders include parks staff, the recreation department, neighborhood associations, environmental groups, youth organizations, seniors' groups, sports leagues, accessibility advocates, and elected officials. Less obvious but equally important: people who currently do not use parks (Why not? What barriers exist?), unhoused residents who rely on parks for shelter, dog owners, gardeners, artists, and cultural groups who use parks for festivals.

By mapping stakeholders comprehensively, the planner ensures the engagement process reaches beyond the usual voices. The map also reveals power dynamics: some stakeholders have formal seats at the table (e.g., advisory committees), others must organize to be heard. The planner can then design engagement strategies to balance power — not just open houses that favor those with time and transportation, but door-knocking, pop-up consultations, and supported participation for marginalized groups.

Stakeholder mapping is also useful for evaluating participation after the fact. Who showed up? Who did not? Whose voices shaped the outcome? Where were the gaps? This retrospective analysis informs future engagement and builds accountability.

37.7 Network Maps

Network maps visualize relationships between actors: people, organizations, communities, or places. In community mapping, network analysis helps answer: Who is connected? Who is central? Who is isolated? Where are the strong ties? Where are the bridging ties? How does information or resources flow?

A network consists of nodes (actors) and edges (relationships). Edges can be directed (A refers to B, but not vice versa) or undirected (A and B collaborate mutually). Edges can be weighted (frequency, strength, resource flow).

Network analysis offers several key metrics:

Degree centrality: How many connections does a node have? High-degree nodes are hubs — well-connected, visible, often influential.

Betweenness centrality: How often does a node sit on the shortest path between other nodes? High-betweenness nodes are brokers or bridges. They connect otherwise separate clusters. Their removal fragments the network.

Closeness centrality: How quickly can a node reach all others? High-closeness nodes are efficient spreaders of information.

Clustering coefficient: How interconnected are a node's neighbors? High clustering indicates tight-knit communities. Low clustering indicates bridging roles.

Network maps reveal structure that is invisible in lists or spreadsheets. A service provider might think they are well-connected, but a network map shows they only connect within their sector — missing cross-sector collaboration opportunities. A community organizer might assume certain leaders are influential, but network analysis reveals different people hold bridging positions.

A practical application: mapping referral pathways in a community's social services. Each organization is a node. An edge exists if one refers clients to the other. Analyze the network. Are there central organizations that many others refer to (potential bottlenecks)? Are there isolated organizations that do not refer or receive referrals (integration opportunities)? Are there clusters that operate independently, suggesting siloed sectors?

Another application: mapping social networks within a neighborhood. Survey residents: Who do you talk to? Who do you trust? Who would you turn to in a crisis? Build a network from the responses. Analyze centrality to identify informal leaders. Analyze clustering to identify tightly knit subgroups. Analyze bridges to find people who connect across subgroups — valuable for spreading information or mobilizing collective action.

Ethical note: network data is sensitive. Revealing who is connected to whom can expose vulnerabilities, alliances, or tensions. Anonymize findings when appropriate. Do not publish individual-level network maps without consent. Aggregate and summarize when possible. The goal is insight, not surveillance.

37.8 Identifying Leverage Points

Donella Meadows, in her 1999 essay "Leverage Points: Places to Intervene in a System," identified twelve places where interventions can shift system behavior. Ordered from least to most effective, they range from tweaking parameters (e.g., adjusting tax rates) to changing paradigms (e.g., shifting from growth-centered to wellbeing-centered goals).

This section focuses on applying Meadows' framework to real community mapping work. We will explore three leverage points that community practitioners encounter frequently.

Leverage Point 9: The strength of negative feedback loops (balancing loops).

Balancing loops stabilize systems by correcting deviations from a goal. Strengthening them can prevent harmful runaway dynamics. Example: A community experiences rising rents. Renters leave, weakening social cohesion and local businesses. A balancing loop could be rent stabilization policy, which limits rent increases and keeps residents in place. Strengthening this loop (enforcing the policy, closing loopholes, indexing allowable increases to inflation rather than market rates) stabilizes the community.

To identify this leverage point in practice, map the feedback loops in your community issue. Where are the balancing loops? Are they strong enough to counteract destabilizing trends? What would strengthen them?

Leverage Point 6: The structure of information flows (who has access to what information).

Information asymmetries create power imbalances and poor decisions. If landlords know market rents but tenants do not, tenants negotiate from weakness. If a municipality tracks service use by neighborhood but does not publish it, equity gaps persist unchallenged.

Mapping information flows reveals leverage. Who collects data? Who analyzes it? Who sees the results? Who is excluded? Interventions include: open data policies, community data trusts, participatory monitoring, public dashboards, and transparency requirements.

A case example: A health authority tracks emergency room visits by postal code but does not share the data. Community advocates request it, map it, and discover that certain neighborhoods have disproportionately high ER use for conditions that should be managed in primary care. The map reveals a primary care access gap. The health authority responds by opening a clinic. The leverage point was information access — once the pattern became visible, action followed.

Leverage Point 2: The goals of the system.

This is near the top of Meadows' hierarchy because changing what a system optimizes for changes everything downstream. If a municipal government optimizes for property tax revenue growth, it prioritizes high-value development, often at the expense of affordable housing and community stability. If it shifts to optimizing for resident wellbeing, housing affordability, or carbon reduction, different decisions follow.

Community mapping can surface goal conflicts. A service ecosystem map might show that every organization is chasing the same funding stream, leading to competition rather than collaboration. The leverage point is not better coordination — it is changing the funder's goals (e.g., from rewarding individual program outcomes to rewarding collective impact).

To apply this leverage point, ask: What is this system trying to achieve? Whose goals dominate? Are those goals explicit or implicit? What would happen if the goal changed?

Systems mapping does not automatically reveal leverage points, but it makes them findable. Once you see the structure — the loops, the stocks, the information flows, the power concentrations — you can ask Meadows' question: Where could a small shift create large change?

37.9 Validating Systems Maps

Systems maps are models, not reality. They simplify. They make assumptions. They reflect the mapmaker's perspective and the limits of available data. Validation is essential.

Validation asks: Does this map reflect how the system actually behaves? Do the people who live and work in this system recognize it? Where is it accurate? Where is it incomplete or wrong?

Triangulation is the first validation strategy. Compare the systems map against multiple sources: quantitative data, qualitative interviews, administrative records, participant observation, literature. If the map shows a reinforcing loop between housing insecurity and health decline, check: Do health records confirm that unhoused people have worse health outcomes? Do interviews with service providers describe the same dynamic? Does research literature support the causal link?

Participatory validation is the second strategy. Share the map with stakeholders — service providers, community members, decision-makers — and ask: Does this make sense? What's missing? What's wrong? This process often reveals invisible actors, uncounted relationships, or misunderstood dynamics. A stakeholder might say, "You show Organization X as central, but they haven't been active in two years — Organization Y is the real hub now." Adjust the map accordingly.

Behavioral testing is the third strategy. Does the systems map explain past behavior? If it shows a balancing loop that should stabilize population, but population has been declining for a decade, something is missing. If it shows a reinforcing loop that should drive growth, but growth has stalled, the loop may be weaker than assumed or blocked by an unmodeled constraint. Use historical data to test whether the map's structure predicts observed patterns.

Scenario testing is the fourth strategy. Use the systems map to predict what would happen under different interventions. If we strengthen this loop, what changes? If we add capacity here, what happens downstream? Then, where possible, compare predictions to real outcomes or expert judgment. This does not require running simulations (though system dynamics software allows this). Informal scenario testing — walking through the map's logic with stakeholders — is valuable.

Validation is iterative. The first map is a hypothesis. Validation reveals gaps. You revise. You validate again. The map improves. It never becomes perfect, but it becomes useful.

One caution: do not confuse validation with consensus. Stakeholders may disagree about how the system works. One might say, "The real bottleneck is funding." Another might say, "No, it's coordination." Both might be partly right. The systems map should reflect this complexity, not flatten it into false agreement. Document disagreements. Note uncertainties. A map that acknowledges what it does not know is more credible than one that pretends certainty.

37.10 Synthesis and Implications

This chapter has moved from theory to practice, introducing six core methods for systems mapping: causal loop diagrams, stock and flow models, service ecosystem mapping, power mapping, stakeholder mapping, and network analysis. Each method serves different purposes, but all share a common logic: they make relationships, feedback, and structure visible.

Three key insights to carry forward:

First, systems mapping is a habit of mind, not just a set of tools. The diagrams matter, but the real value is in the thinking: asking "what connects to what?", looking for feedback loops, identifying stocks and flows, questioning where power sits, and recognizing that community challenges are not isolated problems but symptoms of system structure. Once you develop this habit, you see systems everywhere — even when you are not drawing maps.

Second, systems maps are hypotheses, not facts. They are models built from incomplete information, shaped by the mapmaker's perspective, and subject to revision. The discipline of systems mapping is not in producing perfect diagrams but in testing, refining, and validating them through triangulation, participation, and evidence. A systems map that acknowledges uncertainty and invites critique is stronger than one that claims false precision.

Third, systems mapping without action is just analysis. The purpose of mapping systems is to find leverage — places where intervention can shift patterns, break harmful loops, and open new possibilities. Donella Meadows' leverage points framework reminds us that not all interventions are equally powerful. Tweaking a parameter is easier than restructuring information flows, but information flows are more powerful. Changing a system's goals is hardest — and most transformative.

The methods in this chapter are tools, not formulas. Apply them flexibly. A causal loop diagram might be hand-drawn on a whiteboard in a community workshop. A service ecosystem map might be built in network software or sketched as a concept map. A power map might be a private planning document or a public transparency tool, depending on context. Adapt the method to fit the community, the issue, and the purpose.

Systems mapping integrates with other forms of community mapping. You begin with inventory: identifying assets, services, risks, needs. You add spatial analysis: where things are, who they reach, what patterns emerge geographically. Then you add systems analysis: how things connect, what feedback operates, where power sits, what leverage exists. Together, these layers create a comprehensive understanding — the foundation for evidence-based action.

Two practical implications for your work:

Start small. Do not try to map the entire community system at once. Pick one issue (e.g., youth mental health access, local food security, housing instability) and map the system around it. Focus on key actors, major feedback loops, and critical relationships. Once the map is useful, you can expand it.

Iterate with stakeholders. Do not map in isolation. Build the map collaboratively, test it with people who know the system, and revise based on their input. A systems map built by an outsider may be technically correct but miss the lived reality. A systems map built with insiders has credibility and practical value.

Finally, remember that systems mapping is not neutral. Every map makes choices about what to include, how to frame relationships, and whose perspective to center. Power mapping, especially, can reveal uncomfortable truths about who holds influence and who is excluded. Ethical practice requires transparency about your methods, humility about your limitations, and accountability to the communities you map.

37.11 Causal Loop Workshop

Purpose: This workshop helps you apply causal loop diagramming to a real community issue, practice identifying feedback loops, and explore where interventions might shift system behavior.

Materials Needed:

Large sheets of paper or whiteboard
Markers (multiple colors helpful)
Sticky notes (optional, for brainstorming variables)
Reference: Donella Meadows, Thinking in Systems (2008), Chapter 1 (available online or in libraries)

Steps:

Choose a community issue. Pick a real issue from a community you know: e.g., declining local businesses, youth disengagement, food insecurity, housing instability, social isolation among seniors, lack of childcare access. Be specific.
Identify key variables. Brainstorm the factors that influence this issue. Write each on a sticky note or directly on the board. Aim for 8-12 variables. Examples for food insecurity: household income, cost of food, distance to grocery stores, transportation access, nutrition knowledge, community gardens, food bank use, health outcomes.
Draw causal links. Connect variables with arrows. For each arrow, label it + (same direction) or – (opposite direction). Example: "Household income" → (+) → "Food purchasing power." If income increases, purchasing power increases. "Distance to grocery stores" → (–) → "Food access." If distance increases, access decreases.
Identify feedback loops. Trace circular paths. Mark them R (reinforcing) or B (balancing). Example reinforcing loop: Low income → less food → poor health → reduced work capacity → lower income (R). Example balancing loop: Food insecurity → increased food bank use → improved nutrition → reduced food insecurity (B).
Label the loops. Give each loop a short name that captures its dynamic. Example: "Poverty-Health Spiral (R)," "Food Bank Stabilization (B)."
Analyze the structure. Step back and look at the diagram. Which loops are strongest? Which reinforce the problem? Which counteract it? Are there delays (e.g., health impacts of poor nutrition may take years to appear)? Note them on the diagram with a small "delay" symbol (parallel lines on the arrow).
Identify leverage points. Where could an intervention weaken a harmful reinforcing loop or strengthen a helpful balancing loop? Discuss with your group. Example: Subsidizing transit could reduce distance-to-grocery-store barrier, strengthening access. Increasing minimum wage could break the poverty-health spiral. Community gardens could reduce reliance on distant stores.
Test your diagram with a stakeholder. If possible, show your CLD to someone who lives or works in the community (e.g., a resident, service provider, or community organizer). Ask: Does this make sense? What's missing? What's wrong? Revise based on their input.
Reflect in writing. Write a 2-3 page reflection addressing:
- What feedback loops did you identify?
- Which loop seems most powerful in driving the problem?
- What leverage points did you find? Which seem most feasible?
- What did you learn from validating the diagram with a stakeholder?
- What are the limits of this diagram? What does it not capture?

Deliverable: A causal loop diagram (photographed or digitized) and a 2-3 page reflection.

Time Estimate: 90-120 minutes for the workshop; 30-45 minutes for stakeholder validation; 60 minutes for the written reflection.

Safety and Ethics Notes: If your CLD involves sensitive topics (e.g., poverty, health, discrimination), handle the conversation and the diagram with care. Do not name individuals. If sharing the diagram publicly or with stakeholders, anonymize or generalize as needed. Ensure that the framing respects the dignity of those experiencing the issue — avoid deficit language or blame.

Key Takeaways

Systems mapping makes relationships, feedback loops, and structure visible — revealing leverage points that inventory alone cannot show.
Causal loop diagrams map feedback dynamics; stock and flow models map accumulation and change; service ecosystem maps reveal coordination patterns.
Power mapping and stakeholder mapping identify who holds influence, who is affected, and who is excluded from decision-making.
Network analysis quantifies connectivity, centrality, and clustering — helping locate hubs, brokers, and isolated actors.
Donella Meadows' leverage points framework guides intervention design, emphasizing that some places in a system offer far more potential for change than others.
Systems maps are hypotheses, not truth — validate them through triangulation, participatory feedback, and behavioral testing.

Plain-Language Summary

This chapter teaches you how to map the connections in a community, not just the things. It's not enough to know what services exist — you need to know how they work together, where the gaps are, and who has power.

You learn six practical methods. Causal loop diagrams show how problems feed on themselves (like how poverty makes health worse, which makes it harder to work, which deepens poverty). Stock and flow models track what builds up over time and what drains away (like housing stock or community trust). Service ecosystem maps show which organizations coordinate and which work in silos. Power maps show who makes decisions and who is left out. Stakeholder maps show everyone with a stake in an issue. Network maps show who is connected and who is isolated.

The goal is to find leverage points — places where a small change can make a big difference. Not every intervention is equally powerful. Changing a budget line is easier than changing who controls information. Changing goals is hardest but most transformative.

These maps are tools for action, not just analysis. You draw them with the community, test them with people who know the system, and use them to guide decisions. They are never perfect, but they help you see patterns you would otherwise miss — and that is when real change becomes possible.

End of Chapter 37.

Chapter 37. Systems Mapping in Practice