Module 1: Components of Systems — Lesson 1
This lesson is just one part in our series on Systems Thinking. Each lesson reads on its own, but builds on earlier lessons. An index of all previous lessons appears at the bottom of this page.
Most people who set out to understand a system end up cataloguing its parts. They list the people, the tools, the policies, and the equipment. Then they stop, convinced they’ve done the work. They haven’t. A list of parts describes what a system contains. It says nothing about how it behaves.
Three components define every system: elements, interconnections, and purpose. Remove any one of them and what remains is no longer a system. Understanding each one — and the relationship between them — is the foundation of systems thinking.
What You’ll Learn
- Why elements are the least important component in a system
- How interconnections, not parts, determine behavior
- The difference between stated purpose and revealed purpose
- How to distinguish a system from a collection
- A five-minute exercise for mapping any system clearly
What Are Elements in a System?
Elements are the identifiable, physical components of a system: people, roles, tools, policies, and equipment. They define what the system is capable of — what is possible — but they do not determine what actually happens.
In a coffee shop, the elements are the baristas, the beans, the grinders, the point-of-sale system, and the tables. Each one can be counted, described, and replaced. That tangibility makes elements easy to see — which is why most systems analyses stop there.
As a general rule, if your description of a system reads like a shopping list, you’re still at the element layer.
Elements matter. They set the ceiling on what a system can do. But changing the elements — adding equipment, hiring new people, upgrading tools — rarely changes how a system behaves. Behavior comes from somewhere else.
Key takeaway: Elements define possibility. They do not explain behavior.
What Are Interconnections in a System?
Interconnections are the flows and rules that govern how elements relate: who hands what to whom, when decisions get made, the conditions that trigger action, where delays accumulate, and how feedback returns to the beginning. This is where system behavior originates.
In that same coffee shop, interconnections include how orders move from the POS to the bar, how tickets set the sequencing of drinks, how the “remake if wait exceeds six minutes” rule governs recovery, how delivery schedules determine inventory levels, and how low-stock alerts trigger reordering. Change any of those relationships and the operation changes — without adding a single new element.
The most reliable approach is to study interconnections before proposing solutions. Most operational problems that appear to be resource problems are actually relationship problems. The parts are sufficient; the flows are broken.
Interconnections are also harder to see than elements, which is why they tend to get overlooked. They live in processes, norms, timing rules, and informal agreements rather than in physical objects.
Key takeaway: Interconnections determine behavior. When a system isn’t working as intended, look to the relationships before replacing the parts.
What Is the Purpose of a System?
Purpose is the outcome a system consistently tends toward — the aim you infer from where time, money, and attention actually go, not from what the system claims to be doing. Slogans state intent. Behavior reveals purpose.
A coffee shop that posts “delight every guest” but staffs for rush-hour throughput and measures success by drinks per hour has a revealed purpose of speed. That’s not necessarily wrong. But naming the actual purpose — rather than the stated one — makes deliberate design possible.
The most common mistake in systems analysis is treating the stated purpose as the real one. When the two diverge, every intervention aimed at the stated purpose will fail, because the system is already optimized for something else.
| Stated Purpose | Revealed Purpose | |
|---|---|---|
| How it’s found | Mission statements, slogans, strategy decks | Where budget, time, and measurement go |
| What it reflects | Aspiration | Actual optimization |
| What to do with it | Treat as a design goal | Treat as the current operating reality |
The distance between stated purpose and revealed purpose is where most organizational friction lives. Closing that gap is often the most powerful lever available.
Key takeaway: If stated purpose and revealed purpose are the same, the system is aligned. If they differ, the system is working against its own stated goals — and adding elements won’t fix it.
What Is the Difference Between a Collection and a System?
A collection has elements but lacks the interconnections and shared purpose that produce coordinated behavior. A toolbox is a collection. A workshop organized to produce furniture is a system.
The distinction matters because collections and systems require different interventions. Adding tools to a toolbox changes the collection but doesn’t change how work gets done. Changing the workflow — who uses which tool, in what sequence, toward what end — changes the output.
| Collection | System | |
|---|---|---|
| Elements | Present | Present |
| Interconnections | Weak or absent | Structured and deliberate |
| Purpose | None | Defined (stated or revealed) |
| Coordinated behavior | Does not emerge | Emerges from the structure |
| Example | A pile of ingredients | A recipe being executed |
If the elements in your analysis interact according to rules and produce a consistent outcome, you’re describing a system. If they simply coexist without governing relationships, you’re describing a collection — and the leverage is in building the interconnections, not accumulating more parts.
How Do You Map Any System in One Sentence?
A structured one-sentence description forces clarity about all three components at once. The format is: “In [context], the elements are [nouns], connected by [key flows and rules], in order to [purpose].”
In an employee onboarding process, that reads: “In our onboarding, the elements are recruiters, hiring managers, the HRIS, and training modules, connected by candidate handoffs and access-provision rules, in order to seat productive employees by day ten.”
That single sentence does three things simultaneously. It names what exists, how it relates, and what it’s supposed to accomplish. If any component is difficult to articulate, that’s a signal — not just a writing problem.
How to Map Any System in Five Minutes
This exercise surfaces the gap between stated and revealed purpose faster than most diagnostic processes.
- Name the system with a verb phrase. “How we turn interest into revenue.” “How we move a candidate from application to offer.” Verb phrases force you to describe what the system does, not just what it contains.
- List seven to ten elements. Nouns only. Resist describing what they do — that belongs in the next step.
- Sketch two or three key interconnections. How does information move? How do materials transfer? Where do decisions get made, and what triggers them? Mark any delays.
- Write two purpose statements. One for the purpose you state. One for the purpose behavior reveals. Look at where time and measurement go.
- Choose one relationship to tune. The gap between your two purpose statements points to a specific interconnection that’s misaligned. Adjust that relationship before adding new elements.
As a general rule, if you can’t complete step four in under two minutes, the system’s purpose is either undefined or contested — and that’s the problem worth solving.
Conclusion
A system is three things in relationship: elements that define possibility, interconnections that produce behavior, and purpose that sets direction. Most analyses stop at the first. Most interventions target the first. Most results disappoint.
The elements are the easiest component to change and the least likely to change how a system behaves. The interconnections are harder to see and far more powerful to adjust. The purpose — particularly the gap between what’s stated and what behavior reveals — is where the real diagnostic work happens.
When in doubt: tune the relationships before adding parts, and name the actual purpose before defending the stated one.
Course Index
- Module 0: Introduction to Systems Thinking
- Module 1: Components of Systems
- Module 2: Feedback Loops and Causality
- Module 3: Mental Models and Paradigms
- Module 4: Leverage Points and Change
- Module 5: Systems Archetypes
- Module 6: Applying Systems Thinking to Your World
