"

11 Methodology Guide

Methodology guide

Systems thinking is not just a set of ideas — it is a method for understanding complexity. Whether you’re analyzing a bureaucratic process, a legal framework, a healthcare institution, or even a classroom dynamic, this chapter will help you apply systems thinking in practice. It provides a step-by-step guide and a checklist you can use when breaking down any real-world system.

Let’s walk through it.

  1. Identify the System and Its Boundaries

Start by asking: What system am I looking at? Every system has boundaries, even if they are fuzzy. These boundaries define what is included and what lies outside — the environment that influences the system but is not part of it.

Example: If you’re analyzing a university registration system, the system may include students, faculty, course offerings, and the software used to manage it. But external funding or national education policy may lie outside the system, while still shaping it.

  1. List the Components (Parts) of the System

Once you define the system, identify its key components. Components can be:

  • Human (e.g., teachers, bureaucrats, patients)
  • Technological (e.g., scheduling platforms, payment systems)
  • Institutional (e.g., laws, norms, policies)
  • Material (e.g., buildings, machines, documents)

Make a rough map of these parts and how they are interconnected.

  1. Ask: What Are the Roles of Each Component?

Not all components are equally important. Systems thinking requires you to understand what each part does — its function.

Some components serve as feedback points (adjusting the system based on results), others are drivers (setting direction), and some are obligatory passage points — crucial links the system cannot operate without.

Example: In a public health system, the appointment booking software might not be glamorous, but if it crashes, the entire system stalls. That makes it a critical node.

  1. Identify Leverage Points and Bottlenecks

Next, examine where small changes might cause large effects — these are leverage points. They are places where intervention could shift the whole system. Conversely, locate bottlenecks — places where flow is restricted or where the system is overly dependent on a single component.

Example: If one committee must approve every decision in an organization, that committee may be a bottleneck. If norms around informal collaboration are key to success, that cultural element may be a leverage point.

  1. Trace Feedback Loops and Delays

Many systems contain feedback loops. These can be:

  • Reinforcing (positive feedback) — causing growth or escalation
  • Balancing (negative feedback) — keeping the system stable

Ask: What signals or results loop back into the system and cause adjustment? Are there delays between cause and effect?

Example: A policy to reduce hospital wait times may take months to produce visible change. Understanding that delay helps avoid misjudging the system’s performance.

  1. Analyze Purpose and Alignment

A system may state one goal and function toward another. Ask:

  • What is the declared purpose of the system?
  • What is its actual behavior?
  • Are the two aligned?

Example: A university may say its goal is “student success,” but if most budget is tied to research output, the actual behavior of the system may not align with its stated goal.

  1. Evaluate Outcomes and Possibilities for Change

Finally, use systems thinking to ask:

  • What outcomes does this system currently produce?
  • Are these outcomes intended or unintended?
  • What parts of the system could be changed to improve it?
  • Would changing one part cause ripple effects elsewhere?

Example: Redesigning a welfare application form might seem minor — but if it reduces confusion, it could ease workload downstream and improve service delivery overall.

✅ System Analysis Checklist

Use this as a quick reference each time you analyze a system:

Step Question
1. Define the System What are the system’s boundaries? What lies inside vs. outside?
2. Identify Components What are the key human, technological, institutional, or material parts?
3. Understand Roles What role does each component play? Are any crucial or optional?
4. Spot Bottlenecks What parts restrict flow or dominate control?
5. Locate Feedback Where does information loop back? Are there delays?
6. Clarify Purpose What is the system trying to do — and what is it actually doing?
7. Examine Outcomes Are outcomes aligned with goals? Where might change be most effective?

 

Systems thinking is about seeing beyond the obvious. Instead of focusing on isolated events, it teaches us to look at structures, relationships, and patterns. This chapter gives you a repeatable method to begin that analysis — use it often, and your ability to think systemically will deepen over time.

License

Icon for the Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License

Systems Thinking Copyright © 2025 by Southern Alberta Institute of Technology is licensed under a Creative Commons Attribution-NonCommercial-ShareAlike 4.0 International License, except where otherwise noted.