Team Systems

A team is a system. What each person does within it is shaped by what the system asks of them — and behavior that looks like an individual problem is frequently a system problem wearing an individual's face.

The person and the structure

Behavior in context

Understanding what someone is doing within a team requires understanding what the team is asking of them: what demands are being placed, what role has been assigned, and how the group responds when they depart from it.

Someone who appears to be underperforming may be functioning exactly as the structure has trained them to. Someone who appears disruptive may be responding accurately to signals the rest of the group is suppressing. Neither reading is available if attention stops at the individual.

Systems produce what they are organized to produce

Reliable outcomes, desired or otherwise

A team that consistently fails to pass along critical information is not broken. It is functioning precisely as its structure, incentives, and history have organized it to function. The outcome is undesirable; the system is intact and working.

The useful question is not who is failing but what the arrangement is organized to produce, and why. Changing the outcome requires changing the arrangement, not only the behavior of the people inside it.

Structures that reliably generate poor outcomes

Role ambiguity — where responsibility is unclear, gaps and duplication follow regardless of the quality of the people involved
Absent psychological safety — where raising problems has carried consequences, concealment becomes the norm, and concealment produces the crises transparency would have prevented
Misaligned incentives — people optimize for what is rewarded; where reward and need diverge, the group delivers what the incentive asked for
Communication bottlenecks — where information passes through too few points, delay and distortion are structural rather than incidental
Concealment modeled from above — where leadership hides its own uncertainty or error, everyone learns that this is the correct response to vulnerability

Shared mental models

What separates high-performing groups from merely functional ones

Research on high-performance teams consistently identifies shared mental models as a critical variable: the degree to which each member holds an accurate picture of how the others process information, what they prioritize, and how they behave under load.

Where these models are strong, people anticipate each other, cover gaps without being asked, and coordinate in a way that looks instinctive. Where they are thin, people are surprised by each other — and in high-consequence settings, surprise produces error.

What this understanding consists of

Cognitive style — who processes quickly and who processes thoroughly; both are valuable, and friction follows when neither understands the other
Stress response — who withdraws, who escalates, who becomes rigid, who becomes inventive; none of these is inherently a problem, and all of them affect everyone else
Role identity — what each person believes they are responsible for, and what they expect of those around them
History within the group — what someone has learned about how this particular group responds to them, and what they have adapted accordingly

Why change is slow

A developmental process, not an event

A group organized around a set of patterns for years has those patterns embedded in everyone's behavior at once. Changing them means changing several people's behavior simultaneously, while each is still responding to the others and to the group's history.

Systems move toward their characteristic state. Any intervention meets that pull, and the work is to account for it rather than to be surprised by it. Change moves through recognizable phases — disruption of existing patterns, a period of instability, gradual consolidation as people begin to trust the new configuration, and eventual integration into the operating baseline.

What presents as resistance is often the group doing what groups do: protecting the stability that has allowed it to function, including where that stability is the thing that needs to change.

How this is handled here

Group context as clinical data

Where a presenting concern is rooted in a group context — the person carrying the identified patient role at home, the professional whose distress is inseparable from the team they sit in, the leader whose account of themselves does not yet include their effect on the people around them — the structure is part of the assessment rather than background to it.

New patients are seen by appointment. No referral required.

Schedule an Appointment →

This page is for educational purposes only and does not constitute clinical advice, diagnosis, or treatment. If you are experiencing a mental health crisis, call or text 988 to reach the Suicide and Crisis Lifeline. In a medical emergency, call 911 or go to the nearest emergency room.