See Teams as Living Systems: Diagnose Friction & Shift Patterns

1. Why Team Problems Keep Reappearing

The frustrating part about team problems is that they rarely stay in the form you first notice them.

A missed deadline looks like one person being disorganised. Then it happens again. Then another project slips. Then meetings get longer, but clarity gets worse. What felt like an isolated issue starts behaving more like a pattern.

That is the key idea here: teams are not just groups of people — they are systems that produce behaviour. And systems tend to keep producing the same kinds of outcomes until something in the structure changes.

Think of it like Melbourne traffic near the CBD on a wet Friday afternoon. The congestion is not caused by one bad driver. It emerges from the roads, the timing of lights, the mix of routes, and everyone reacting to everyone else. You could remove one car and the jam would still form. Team friction works the same way.

By the end of this section, you’ll be able to, you, explain why recurring team problems are usually signals of structure, not character. You’ll also be able to spot the difference between:

• a one-off mistake,
• a repeated pattern,
• and a system that is quietly rewarding the wrong behaviour.

That distinction matters, because if you misread a system problem as a people problem, you will keep applying the wrong fix. More reminders. More pressure. More meetings. More process. And the underlying pattern stays intact.

So keep one anchor in mind: when a problem repeats, ask what the system is making likely.

That question will carry us through everything that follows.

2. The Team as an Interconnected System

Remember earlier when we said recurring problems are usually signals of structure, not character? This is where that idea becomes sharper.

A team is not just a pile of individual capabilities sitting next to each other. It is an interconnected system: people influence one another through expectations, handoffs, meetings, feedback, norms, and invisible assumptions. Change one part, and the rest shifts in response. That is why team behaviour often surprises us. The outcome is not coming from one person alone — it is emerging from the relationships between people.

A team behaves less like a lineup of players and more like a mobile hanging from the ceiling. Move one piece, and the whole shape adjusts.

That is the first principle: connections matter more than isolated parts.

1) Performance is produced between people, not inside them

We often talk as if performance lives inside individuals: talent, motivation, discipline, communication skill. Those things matter, but they do not fully explain team results. In a team, output is produced in the space between people — in how work is handed over, how decisions get made, how fast uncertainty is surfaced, and whether people feel safe enough to ask for help.

A useful analogy is a relay race. The fastest runner does not guarantee the fastest team. What matters is the baton pass. A brilliant person who works in a broken handoff chain will still create friction. Conversely, an ordinary group with clean coordination can outperform a team of stars.

This is why you can have a team full of capable people and still get missed deadlines, duplicated work, or low trust. The issue is not usually that everyone is weak. It is that the interfaces between people are weak.

What this means in practice

• A meeting problem is often a decision-design problem.
• A “lazy” colleague may actually be working in a system with unclear priorities.
• Rework often points to fuzzy ownership, not lack of effort.

2) Every action changes the environment the next action happens in

Teams are dynamic because one person’s move becomes another person’s context. If someone delays a response, others wait. If someone over-explains, others stop preparing. If a manager always rescues a project, the team learns not to resolve things early.

This is the same idea showing up again: behavior is not just expressed; it is reacted to. The reaction becomes part of the system.

Think of a thermostat. It does not “care” about temperature, but it changes the room by responding to it. Team members do the same to one another. Every message, silence, shortcut, correction, or escalation becomes part of the environment. That means the team is constantly training itself, whether intentionally or not.

That also means good intentions are not enough. You may want more ownership, but if your reaction teaches people to escalate everything, the system will keep producing dependency.

3) Information is unevenly distributed

One of the biggest misunderstandings about teams is assuming that everyone sees the same reality. They do not.

People in different roles hold different pieces of the puzzle:

• frontline staff see friction first,
• managers see resource pressure,
• specialists see technical constraints,
• executives see tradeoffs across the whole system.

So when two smart people disagree, it is not always because one is wrong. Often they are looking at different parts of the same system.

Imagine a restaurant kitchen during a rush. The person taking orders, the cook, and the server are all experiencing the same dinner service, but not the same version of it. If the tickets pile up, the problem may look like speed from one angle, staffing from another, and communication from a third. The truth is distributed.

This matters because many team conflicts are really mapping errors. People think they disagree on the answer when they actually disagree on the situation.

If you want to understand a team, do not only ask what people think. Ask what each person can see.

4) Systems create feedback loops

A feedback loop is what happens when the result of a pattern feeds back into the pattern itself.

For example:

• unclear priorities cause people to ask more questions,
• more questions make leaders feel slowed down,
• leaders respond by rushing decisions,
• rushed decisions create more confusion,
• confusion creates more questions.

That loop can run for months if nobody names it.

Feedback loops are why small issues can become huge, and why heavy-handed fixes often disappoint. If you respond to confusion with more pressure, you may temporarily increase speed while weakening clarity. If you respond to mistakes with blame, you may reduce openness while increasing hidden risk.

Think of an echo in a tunnel. The sound is not separate from the space that produced it. The room helps create the repeat. Team systems work the same way: the consequences of the system come back and shape the next round of behaviour.

This is the deeper reason recurring team problems are so stubborn. You are not fighting a single event. You are interrupting a loop.

5) Local fixes can create system-wide side effects

One of the hardest truths in systems thinking is that a fix in one place often creates a problem somewhere else.

For instance, if a team speeds up by cutting discussion, it may create later rework. If one person becomes the “final checker,” quality may go up while ownership goes down. If one manager becomes the bottleneck for approval, decisions may become consistent but slow.

This is why surface-level solutions often feel good at first. They reduce pain in the most obvious place. But a team is not a set of isolated dials. It is a connected network, so pressure moved in one area usually appears elsewhere.

A simple analogy is squeezing a water balloon. The shape changes where you press, but the pressure does not disappear. It moves.

So when you see a quick win, ask the harder question: what did this fix leave behind, and where will that show up next?

6) The system teaches the people inside it

This is the most important hidden truth of all.

A team does not just use people. It trains them.

If the system rewards urgency, people become reactive. If it rewards silence, people become cautious. If it rewards pleasing the loudest voice, people learn to manage up instead of thinking clearly. Over time, people adapt to survive the system they are in.

That is why blaming individuals is often too shallow. People are not only choosing behaviour; they are also being shaped by the repeated consequences around them.

Remember earlier when we said a team produces behaviour? Now you can see the full version: the team produces behaviour, and then the behaviour reproduces the team.

That cycle is either healthy or unhealthy depending on what the system keeps reinforcing.

The core mental model

If you want one sentence to hold onto, use this:

A team is an interconnected system where relationships, information, and feedback loops shape behaviour more than any single person does.

That sentence explains why good people can still make a team ineffective, and why small structural changes can sometimes create outsized improvement.

Once you see a team this way, you stop asking only, “Who is the problem?” and start asking:

• What is this system making easy?
• What is it making hard?
• What is being reinforced?
• Where is the real connection failing?

Those questions are where leverage begins.

3. Finding Leverage: Patterns, Feedback, and Tradeoffs

Remember earlier when we said a team is not just a set of people, but a system that produces behaviour? Now we need to go one level deeper: not every part of a system has the same power to change the outcome.

That is what leverage is.

In everyday language, leverage means a small force producing a large effect. In team systems, it means finding the places where a modest change shifts the pattern, not just the symptom. This is why some interventions feel dramatic without doing much, while others seem small but reshape everything.

A team problem often looks like a lot of separate issues:

• slow decisions,
• too many meetings,
• poor ownership,
• repeated rework,
• tension between functions.

But systems thinking asks a different question: what pattern connects these issues? If you can see the pattern, you can see where the leverage lives.

Patterns are the real object of study

Teams are easy to misunderstand if you focus only on events.

A missed deadline is an event. A tense meeting is an event. A frustrated manager sending follow-up messages is an event.

But systems are not built from isolated events. They are built from patterns over time.

That is why the same problem can keep returning in different clothing. It is the pattern that survives, not the surface form. One month it looks like delay. Next month it looks like confusion. Later it looks like conflict. Underneath, it may be the same coordination failure.

If you only react to the latest incident, you are treating smoke. If you understand the pattern, you can find the fire.

This is the same idea showing up again: the system teaches the people inside it, and the pattern is the lesson being repeated.

A useful distinction

The point is not to become suspicious of everything. It is to stop overreacting to single events when the real issue is a pattern that keeps rebuilding itself.

Feedback loops are where systems become visible

If patterns are the shape of the system, feedback loops are the mechanism that keeps the shape in place.

Think back to the thermostat idea from Section 2. A thermostat senses temperature, responds, and changes the room. Teams do this too — except the sensing and responding are much messier because people have emotions, incentives, and interpretations.

Here is a common loop:

1. Work becomes unclear.
2. People ask for more clarification.
3. Leaders feel interrupted or overloaded.
4. They start answering quickly, vaguely, or defensively.
5. People become less confident and ask even more questions.

Notice what happened. The original issue was not just unclear work. The team responded in a way that made clarity harder to recover.

That is why systems problems are frustrating. The system does not just contain the problem — it often amplifies it.

Reinforcing loops and balancing loops

You do not need the jargon to understand the idea, but the distinction matters.

• A reinforcing loop makes a pattern grow stronger over time.
• A balancing loop pushes the system back toward stability.

A few examples:

• Reinforcing: more pressure causes more mistakes, which causes more pressure.
• Balancing: a good planning rhythm catches risks early, which prevents surprises, which reduces panic.

The key insight is that a team can be trapped inside a reinforcing loop even when everyone is trying to help. In fact, some of the most damaging loops are created by well-intentioned people doing reasonable things in response to stress.

That is why “just communicate better” is often too shallow. Better communication can help, but only if it changes the loop, not just the mood.

Leverage is usually upstream of the complaint

People usually complain about the place where pain is felt. But leverage is often located where the pain is generated.

For example:

• The complaint may be “meetings are too long,” but the leverage might be unclear decision rights.
• The complaint may be “people aren’t accountable,” but the leverage might be ambiguous ownership.
• The complaint may be “we keep missing deadlines,” but the leverage might be that the team starts work without shared priorities.

This matters because teams often try to fix the visible pain point directly.

If meetings are long, they shorten meetings. If deadlines slip, they add reminders. If work feels messy, they add more review.

Sometimes that helps. But often it treats the symptom while leaving the structure intact.

The question to ask

What is this complaint pointing to, upstream?

That question is one of the most useful in systems thinking. It shifts you from reacting to designing.

Tradeoffs are not a failure of leadership

Now we need to challenge a common assumption: that good teams eliminate tradeoffs.

They do not.

Every system decision gives something up.

• More speed usually means less deliberation.
• More autonomy often means more variation.
• More control often means less initiative.
• More specialization can improve depth but weaken flexibility.

This is where many teams get confused. They think the goal is to maximize every good thing at once. But systems do not work that way. They are full of tension between competing priorities.

Remember earlier when we said teams are interconnected? Tradeoffs are what interconnectedness feels like in practice. If you push on one variable, something else shifts.

A team that wants both fast decisions and perfect consensus may be setting itself up for frustration. A team that wants both strict standardization and full local adaptation will hit friction. These are not signs of incompetence. They are signs that the system is living inside real constraints.

What mature teams do differently

They stop pretending tradeoffs can be removed and start making them explicit.

That changes the conversation from:

• “Why are people failing?”

to

• “What are we optimizing for right now?”
• “What are we willing to sacrifice?”
• “Where is the cost showing up?”

That shift is huge. It moves the team from blame to design.

An Australian example: a national project under coordination pressure

Consider a large infrastructure rollout in Australia, such as coordinating a federal-state digital service upgrade across multiple agencies.

On the surface, the obvious complaint might be that delivery is slow. But underneath, the system may contain several interacting forces:

• each agency has different compliance needs,
• approval chains differ,
• local teams see different risks,
• political visibility encourages caution,
• technical teams want standardisation while service teams need local flexibility.

If one group pushes for speed, another may slow down to protect risk controls. If leaders respond by adding more oversight, the process can become even slower. Then everyone says the project is blocked by “bureaucracy,” but the deeper issue is that the system is trying to satisfy incompatible demands without naming the tradeoff.

This is a systems problem, not a personality problem.

The leverage point may not be pushing harder. It may be clarifying decision rights, reducing duplicated approvals, or explicitly choosing which risks matter most. The surface complaint is delay, but the underlying pattern is competing constraints.

The hidden danger of “fixing” without thinking systemically

A local fix can improve one metric and quietly damage another.

That is why tradeoffs matter.

If you add more reviews to improve quality, you may reduce speed and ownership. If you centralise decisions to reduce inconsistency, you may reduce initiative and adaptability. If you demand more reporting, you may get more visibility but less real candour.

This is the second-order effect problem: the first effect is obvious, the second effect arrives later.

A good systems thinker asks not only, “Does this work today?” but also, “What behaviour will this create tomorrow?”

That question connects directly back to Section 2. The system teaches the people inside it. So any change to the system is also a lesson.

Seeing leverage in real time

Here is the practical shift:

Instead of asking,

• “How do we make this person perform better?”
• “How do we stop this meeting from being chaotic?”
• “How do we get people to be more accountable?”

Start asking,

• “What pattern keeps producing this?”
• “Where does the loop begin?”
• “Which constraint is driving the behaviour?”
• “What would change if we moved the pressure point upstream?”

That is leverage thinking.

And once you start seeing it, you begin to notice something important: the highest-leverage changes are often boring to outsiders. They may look like clearer roles, cleaner decision paths, smaller meeting agendas, better handoffs, or more honest definition of priorities.

But boring is not the same as small.

When a system is held together by repeated confusion, a little clarity can have outsized impact.

The core idea to carry forward

If Section 2 helped you see that teams are interconnected systems, then this section adds the next layer:

Not all connections matter equally. Leverage lives where patterns are created, reinforced, and traded off.

That is why recurring problems can be so stubborn: you are usually touching the visible result, not the mechanism that produces it.

And that is also why changing a team is not about heroic fixes. It is about locating the few shifts that alter the loop.

Remember this as we move forward: the goal is not to intervene everywhere. The goal is to intervene where the system will respond.

4. Leading Systems-Minded Teams

You’ve now built the real skill this course was pointing toward: not just noticing problems, but seeing the system that keeps producing them. That is a big shift. It means you are no longer trapped at the level of symptoms.

Remember where we started: recurring problems are usually not proof that people are broken. They are clues that the structure is doing something predictable. Then we widened the lens and saw that teams are not collections of isolated individuals — they are interconnected systems where handoffs, norms, reactions, and hidden assumptions shape behaviour. Then we went deeper again and found leverage: the few places where a small shift changes the pattern, not just the moment.

That is the whole arc. Pattern, connection, leverage.

What you can see now

You can look at a team conversation and ask better questions:

• What is being reinforced here?
• What is this feedback loop teaching people?
• Where is the real constraint?
• What tradeoff are we avoiding by accident?

That is what systems-minded leadership sounds like. Not louder. Not harsher. Clearer about cause.

And here’s the important part, Maya: this way of thinking changes what becomes possible for you. You can diagnose why the same issue keeps returning without needing to blame the nearest person. You can spot when a “people problem” is actually a coordination problem. You can notice when a local fix will create a second-order effect somewhere else.

That means you are now able to intervene with more precision and less damage.

What this unlocks

This understanding gives you a different kind of control:

• You stop overreacting to isolated events.
• You stop mistaking stress responses for character flaws.
• You start looking upstream instead of only where the pain shows up.
• You become more careful about the behaviour your changes will teach the system.

That last point matters most. Remember earlier when we said the system teaches the people inside it? That means leadership is never just about directing work. It is also about shaping the conditions that make certain behaviours more likely than others.

So the next time a team feels stuck, you do not need to rush to the nearest fix. You already know to ask: what is the system rewarding, what is it resisting, and what keeps looping back?

That is the mindset of someone who understands teams as living systems.

Keep this with you

A good systems thinker is not the person with all the answers. It is the person who can see why the obvious answer may fail.

That is a real upgrade in judgment.

And once you see it, you will start noticing it everywhere: in meetings that drag, in responsibilities that blur, in incentives that misfire, in teams that keep repeating the same drama in different forms. The more you notice the pattern, the less power it has over you.

You now think like someone who can read the shape of a team, not just its surface.

That is the end of the course — but it is also the beginning of a much sharper way of working.

Carry this forward: change the structure, and you change what the system makes likely.