For Team & Operations Leaders Article · November 2026 ~9 min read

Team Dynamics: How to Read Them and How to Fix Them

Team dynamics are the repeated patterns of interaction between the people on a team, which is why you can read most of them in a single meeting and why they survive a reorganization. This is the reading method I use, the six patterns it turns up most often, and what actually moves each one.

By Jeff Morris, "The High Trust Guy" DreamSmart Behavioral Solutions

What are team dynamics?

Team dynamics are the repeated patterns of interaction between the people on a team: who speaks first, who gets deferred to, how a disagreement gets resolved, who is told what and when, and what happens to a commitment once it has been made. They are patterns rather than events, which is why a single meeting is usually enough to spot them and why they survive a reorganization intact. Dynamics are produced by behavior, not by the org chart, so they can be changed by behavior without changing anybody's reporting line. In a workplace they are the difference between a team that looks right on paper and one that actually moves.

Two consequences follow, and they are the reason this matters to a manager rather than to a researcher. First, dynamics are observable, so you do not need a survey to start. Second, they are stable, so what you see in one meeting is usually what the team does every week. Stability is what makes dynamics worth working on. It is also what makes them frustrating.

Bruce Tuckman's forming, storming, norming and performing sequence, published in 1965, is where most articles on this subject stop. It is a useful description of how a new group settles. It is not a reading method for a team that has been together three years and is quietly slow, which is the team most managers actually have.

Dynamics, culture and personality

Three words get used for each other constantly, and the substitution costs people months.

Culture is what an organization rewards and tolerates, and it is set well above any one team. Dynamics are what a specific group of people repeatedly does with each other. Personality is what an individual brings before anyone else is in the room. A team can sit inside a strong culture and still run poor dynamics, which is the case almost every time a leader tells me the company values are fine but this particular group is stuck.

The direction of the error matters. Blaming culture for a dynamics problem produces a values exercise that changes nothing on Monday. Blaming personality produces a hiring decision, or a quiet campaign against one person, when the pattern would survive their departure. I have watched a team lose its named "difficult" member and reproduce the same conflict with a new participant inside two months, because the pattern was never about the person.

Personality does matter, and the Behavioral SuperPowers® work exists because how a person is wired changes how they show up inside a pattern. But personality is the input. The dynamic is what the group does with it.

The six patterns that show up on most teams

Six patterns account for most of what I get called in to look at. Each one has a tell you can watch for and one behavior that moves it. None of them need a psychologist to spot.

  • The quiet expert. The person with the most relevant knowledge speaks last, or only when asked directly, and their objection surfaces after the decision. The tell is people saying "we should have asked her" more than once a quarter. The behavior that moves it: ask the quiet expert first, before the room forms an opinion they would then have to argue against.
  • The unnamed decision owner. Everyone leaves the meeting believing a decision was made and nobody can say by whom. The tell is a decision that gets made twice. The behavior that moves it: one name written next to the decision before the meeting ends, in a document everyone can see.
  • The recurring re-litigation. The same decision returns every few weeks in a slightly different costume. The tell is a familiar sinking feeling when the agenda arrives. The behavior that moves it: state what would have to change for the decision to be reopened, then hold that line the first time somebody tests it.
  • The protected underperformer. One person's work is routinely absorbed by others and nobody names it, usually because the leader has not. The tell is a teammate who is always slightly overloaded for reasons nobody can quite explain. The behavior that moves it: a direct conversation with the person, rather than a redesign of the workload around them.
  • The single point of information. One person holds the context everyone else needs, and the team has quietly organized itself around asking them. The tell is that a week of their leave stops three workstreams. The behavior that moves it: make one piece of that context written and shared every week until the dependency is gone.
  • The two-person conflict everybody routes around. Two people cannot work together, so the team builds detours, and the detours become the process. The tell is a handoff that goes through a third person for no reason anyone can articulate. The behavior that moves it: name the detour out loud, because in most cases nobody has ever admitted it exists.

Examples of effective team dynamics at work

These are workplace examples, drawn from ordinary working weeks in offices, project teams and distributed groups. Each row takes one moment every team hits, shows the effective version and the ineffective version, and names the behavior that separates them. The separating behavior is the part worth copying, because it is the only column you can act on directly.

SituationEffective patternIneffective patternThe behavior that separates them
A technical judgment callThe person closest to the work is asked first, and their objection lands before the decisionThe senior voice frames it, and the expert raises the flaw afterwards in a private messageAsking in order of proximity to the work, not seniority
An open decision at the end of a meetingOne named owner and a date, written where everyone can see itA shared sense that it was agreed, with no name attachedWriting the owner down before anyone leaves the room
Somebody wants a decision reopenedThe new information is stated, and the decision is either reopened on it or closed againThe topic reappears every few weeks with no new informationNaming what would have to change for it to be reopened
A teammate is missing the barThe manager has the conversation, once, directlyThe work is absorbed by two colleagues and nobody says whyA direct conversation instead of a workload redesign
One person holds all the contextThe context is written down weekly and the dependency shrinksThe team schedules itself around that person's calendarTurning spoken context into shared writing
Two people cannot work togetherThe detour is named out loud and the pair is worked with directlyEvery handoff between them runs through a third personSaying plainly that the detour exists

Worth noticing what is absent from the effective column. Nothing in it requires that people like each other. Effective dynamics are not warmth. They are predictability about who decides, who knows, and what happens when somebody is wrong.

How to read a team in one meeting

You can read most of this in sixty minutes if you watch the right four moments and resist the urge to participate.

  • Who speaks first, and who speaks last. The first speaker tells you who the room defers to. The last speaker, especially when they are the most knowledgeable person present, tells you whether expertise is reaching the decision or trailing it.
  • Who gets interrupted, and who does the interrupting. This reads as a personal habit and behaves like a team-level pattern. The same person gets cut off week after week, by several different colleagues, which means it is the room's rule rather than one person's manners. Watch whether the same person absorbs them every time.
  • What happens at the first disagreement. The first disagreement is the highest-information moment in any meeting. Does it get worked, deferred, or smoothed over by the most senior person in the room.
  • Who closes the loop. At the end, somebody either states what was decided and who owns it, or nobody does. If nobody does, you have already seen the pattern you came to find.

One meeting gives you a hypothesis, not a conclusion. Watch a second one before you act, because the first meeting after a new manager joins is never a normal meeting.

Why a reorganization does not change dynamics

Structure changes who reports to whom. It does not change what two people do when one of them is late.

Behnam Tabrizi's 2015 study in Harvard Business Review looked at 95 cross-functional teams across 25 large corporations and found nearly 75% were dysfunctional on at least three of five criteria: meeting a planned budget, staying on schedule, adhering to specifications, meeting customer expectations, and staying aligned with the company's goals. Those teams were not short on structure. They had charters, sponsors and reporting lines, and the dysfunction sat in the interactions between the people the structure had assembled.

This is the same conclusion I reach in Cross Functional Team Collaboration, where the structural fixes and the behavioral fixes are set side by side. The short version: structure removes obstacles, behavior produces trust, and a reorganization that only does the first tends to reproduce the old pattern inside the new boxes within a quarter.

There is a useful test to run before any restructure. Name one dynamic from the list above that the new structure will change, and name the behavior that will change it. If you cannot do both, you are moving the same pattern to a new address.

How to change one pattern

One at a time. A team can absorb one deliberate change to how it works, and an attempt at three usually produces none.

  • Name it plainly, once. "We make decisions twice and I want that to stop" does more work than a workshop. The naming has to be specific enough that people recognize last Tuesday in it.
  • Change one behavior, and make it yours first. Pick the single behavior from the list above that moves the pattern, and do it yourself in the next meeting, visibly, before you ask anyone else to.
  • Make the change visible. A decision log everyone can see beats an agreement everyone remembers differently. Visible is not the same as ceremonial, and one shared document is usually enough.
  • Re-check at six weeks. Long enough that the novelty has worn off, short enough to correct. Six weeks is also roughly when the old pattern will try to come back, usually during the first genuinely bad week.

If the pattern has not moved by then, the usual reason is that the new behavior was practiced in calm weeks and abandoned in the week it mattered. That is worth knowing too, and it is a more useful finding than a stalled score.

Where dynamics become measurable

Observation is fast and it is contestable. Two competent managers can watch the same team and disagree, and without a shared instrument the argument gets settled by seniority instead of by evidence.

The TrustFlow™ methodology scores the behavior underneath the pattern: twelve specific trust behaviors, the 12 Cs of Trust, in four quadrants. Foundations (Character, Courage, Commitment), Essentials (Connection, Communication, Caring), the Work (Clarify, Collaboration, Coaching) and Results (Consistency, Competence, Closeout). Each is rated 1 to 5 by the people who actually work together, then rolled up into a Team TrustFlow Index (TTFI) from 1.00 to 5.00: 1.00 to 2.49 Constrained Trust, 2.50 to 3.74 Developing Trust, 3.75 to 5.00 Sustained TrustFlow.

What a score adds to observation is three things. A baseline you can re-measure. A quadrant profile that points at a cause rather than a symptom. And a way for a team to see itself without any one person having to make the accusation out loud. The unnamed decision owner and the recurring re-litigation both surface as a weak Work quadrant. The protected underperformer surfaces in Results, usually in Closeout.

The case for measuring this rather than sensing it is reasonably strong. De Jong, Dirks and Gillespie's meta-analysis of 112 independent studies covering 7,763 teams found intrateam trust related to team performance at an above-average effect size, and the relationship held after controlling for prior performance and for trust in leadership (Journal of Applied Psychology, 2016). The full method is in How to Measure Trust.

Frequently asked questions

What are team dynamics?

Team dynamics are the repeated patterns of interaction between the people on a team: who speaks first, who gets deferred to, how a disagreement gets handled, who knows what and when, and what happens to a commitment after it is made. They are patterns rather than one-off events, which is why they can usually be observed in a single meeting and why they persist through a reorganization.

What are examples of good team dynamics?

In a workplace, good dynamics look like this: the person closest to the work is asked first, every open decision leaves the meeting with one named owner, a decision is reopened only when new information arrives, underperformance is addressed directly rather than absorbed by colleagues, context is written down instead of held in one person's head, and a conflict between two people is named rather than routed around.

What causes poor team dynamics?

Mostly small things that were never addressed and were allowed to repeat: decisions with no owner, an objection that arrives after the meeting, work quietly absorbed on someone's behalf, a dependency on one person's memory. Each becomes a habit and then a norm. Structure and personality get blamed far more often than they deserve, which is why restructures and departures so often leave the pattern intact.

Can you change team dynamics without changing the team?

Yes, and it is usually the only change that works. Dynamics are produced by repeated behavior, so they respond to a changed behavior practiced consistently by the most visible person on the team. Name one pattern, change one behavior, make the change visible in a shared document, and re-check at six weeks. Changing the people without changing the behavior tends to reproduce the same pattern with new participants.

Is team dynamics the same as team culture?

No. Culture is what an organization rewards and tolerates, and it is set above the level of any single team. Dynamics are what one specific group of people repeatedly does with each other. A team can sit inside a healthy culture and still run poor dynamics, which is why a company-wide values exercise rarely changes how one stuck team operates on Monday morning.

You can read it.
You can also score it.

The Team TrustFlow Index turns the pattern you noticed in one meeting into twelve scored behaviors you can move deliberately.