The University of Manchester · FACULTY OF MANAGEMENT

FBTE34511 Chap.3 Systems Thinking and Mapping

- one subject, every graph, every model, every mark
7 Chapters4-page Bible
Our own words - no uploaded lecturer files
Updated for this semester
Chapter 3 of 8 · FBTE34511

Systems Thinking and Mapping

Systems Thinking and Mapping moves analysis beyond a linear chain of stages. A systems map identifies actors, materials, information, money, authority, decisions and feedback inside a stated boundary. It helps explain why an outcome persists, where unintended consequences appear and which intervention may have leverage. The chapter emphasises labelled flows and causal mechanisms.

A circular layout is not automatically a feedback loop, and a visible node is not automatically the best leverage point. The map should be accompanied by prose that explains decisive relationships, identifies one loop and shows how the visual changes the recommendation.

In this chapter

What this chapter covers

  • 01

    System boundaries

  • 02

    Actors and roles

  • 03

    Material flows

  • 04

    Information flows

  • 05

    Feedback loops

  • 06

    Unintended consequences

  • 07

    Leverage points

Worked example · free

Map a protective-equipment return system

Q [4 marks]. Returns are low across sites, stores and a recovery partner. Identify the feedback failure and a leverage point. The displayed marks are an original AskSia practice allocation, not a University marking scheme.
Solid arrows trace the material route through supplier, operator, user and recovery, while the dashed return of condition data creates a feedback path for futurSolid arrows trace the material route through supplier, operator, user and recovery, while the dashed return of condition data creates a feedback path for future decisions.SupplierOperatorUserRecoverycondition datasolid: materialdashed: information
Solid arrows trace the material route through supplier, operator, user and recovery, while the dashed return of condition data creates a feedback path for future decisions.
  • 1Map procurement, issue, use, return, sorting and remanufacture.
  • 1Separate garment, guidance, rejection and incentive flows.
  • 1Show how missing rejection evidence repeats unsuitable specifications.
  • 1Return reason codes to procurement and change the local routing metric.
The first leverage point is the feedback and incentive relationship, not additional storage capacity.
Sia tip — Label every arrow with what moves and who can interrupt it.
Glossary

Key terms

System boundary
The justified limit that determines which actors, flows and time horizon the map includes.
Reinforcing loop
A feedback relationship that amplifies the direction of change through repeated effects.
Balancing loop
A feedback relationship that resists change or pushes the system toward a limit.
FAQ

Systems Thinking and Mapping FAQ

How is a systems map different from a process map?

A process map usually shows a sequence of activities. A systems map can include several types of flow, authority, incentives, feedback and actors outside the formal process, allowing it to explain persistence and unintended effects.

How do I identify a leverage point?

Look for a relationship, rule, incentive or information flow that reproduces the problem and can feasibly change. Test whether the intervention alters the mechanism rather than merely absorbing its symptoms.

How much of the map should the prose explain?

Explain the boundary, two or three decisive relationships, one feedback mechanism and the leverage point. Avoid narrating every arrow. The prose should tell the reader what the visual demonstrates and why it changes the recommendation.

How do I know whether a node belongs in the map?

Run a removal test: ask which explanatory claim would fail if the node disappeared. If none does, simplify the visual or move the detail into prose. Then trace a route from the proposed intervention to every claimed outcome. Each connection needs an actor, enabling condition and observable change. Where the route breaks, record a dependency or evidence question for the roadmap instead of drawing a stronger arrow.

These tests preserve causal honesty, improve readability and distinguish a useful systems explanation from a comprehensive but undecipherable inventory.

Study strategy

Assessment move

Start from the framed problem and write the outcome the map must explain. List actors and mark what each controls, receives and decides. Draw material, information, money and authority with distinct labels. Add delays and exception routes. Search for an outcome that returns to influence a later input, then state whether it reinforces or balances change.

Choose a leverage point only after tracing how the intervention travels around the map. Finish by checking displaced burden and missing actors. Redraw the map until another reader can understand the causal story without a spoken explanation. Work first on paper so software does not tempt you to prioritise symmetry over causality. Place the focal outcome on one side and ask what immediate decisions create it.

For each decision, add the actor, information used and constraint. Continue backwards until the boundary reaches evidence already introduced in the context section. Then follow outputs forward to recovery, residual material and learning. Use a legend that distinguishes physical, informational, financial and authority flows.

Label verbs on arrows, because an unlabeled connection hides whether one actor sends, approves, pays, verifies or disposes. Add delay markers where data or material arrives too late to influence the relevant choice. To find feedback, look for an outcome that changes a future decision: rejection can reduce confidence, low confidence can increase disposal and disposal can reduce the evidence needed for redesign.

Write that loop as a sentence before drawing the return arrow. Test the leverage point by imagining the intervention succeeds locally. Follow its effect across the rest of the map and identify capacity limits, new work and displaced risk. If the change only stores, sorts or reports more output without altering the relationship producing it, call it a symptom response.

Mark uncertain arrows with a different style and list the observation, record or interview needed to verify them. In the report, use the map caption to state its boundary and purpose. The surrounding prose should explain the decisive loop, leverage point and responsibility implication. End with the question that user or stakeholder research must answer next.

This keeps the map connected to evidence gathering rather than presenting it as a finished representation of reality.

Working through Systems Thinking and Mapping in FBTE34511? Sia is AskSia’s AI Management tutor — ask any FBTE34511 Systems Thinking and Mapping question and get a clear, step-by-step explanation grounded in how FBTE34511 is taught and assessed. Read this chapter free, then take your hardest questions to Sia.

A+Everything unlocked
Unlocks this Bible + all 41 of your subjects at The University of Manchester, plus 1,000+ more Bibles across the AskSia library.
Sia - your FBTE34511 tutor, unlimited, worked the way the exam marks it
The full 4-page Bible + practice bank with worked solutions
Chrome extension - sync your LMS so Sia knows your deadlines
Bilingual EN / Chinese on every Bible and every Sia answer
$0.99 Trial
30-day money-back · cancel in one tap · how it works