Watch a great team work under real pressure and the first thing you notice is how little they say.

I learned this before I ever coached anyone. For about a decade I was a product instructor for Special Forces medics, and I spent a lot of time watching elite teams operate in conditions that would scatter most groups. Here is what surprised me early on. The best teams were not the loudest. They were the quietest. A look, a word, a small gesture, and three people moved in a way that would have taken another team a paragraph of instructions and a short argument to coordinate. Nobody was explaining. Everybody already knew.

Then I would watch a struggling team, and the struggling team was talking constantly. Clarifying. Confirming. Repeating. Asking what we were doing again. From the outside, the busy team looked more engaged. It was actually doing more work to get less done, because every coordination that a great team had already solved in advance, the struggling team was solving live, out loud, in the middle of the task.

So let me say the thing that runs against almost everything you have been told about teams. The answer to a struggling team is usually not more communication. It is a shared standard that makes most of the communication unnecessary in the first place.

What a shared mental model is

A shared mental model is the picture a team holds in common of what it is doing, how it is doing it, and what "right" looks like, held closely enough that any member can predict what the others will do without asking.

That is the quiet you saw in the good team. It was not telepathy and it was not chemistry. Every person was running the same model. When you and I hold the same picture of the goal, the roles, the sequence, and the standard, I do not need to narrate my next move, because you already expect it. The coordination happened in advance, when we built the shared picture, so it does not have to happen live, in the moment, when there is no time for it.

Contrast that with a team where everyone holds a slightly different picture. Now every handoff needs a conversation, because no one can safely assume anything. That team is not talking a lot because it is engaged. It is talking a lot because it has to. The talk is the tax it pays for never having built the model.

The reframe: talk is a symptom, not the cure

Here is where most organizations get it exactly backwards. A team is struggling, so leadership prescribes more communication. More check-ins. More status meetings. A new channel, a new stand-up, a new weekly sync. The theory is that if information moves more, coordination improves.

Sometimes it helps a little. Usually it adds noise, because the volume of talk was never the problem. The problem was that the team never agreed on the picture, so all that new communication is just more people describing more slightly different pictures to each other. You cannot fix a missing shared model by talking more. You fix it by building the model, and the sign that you have built it is that the talking goes down.

Think about the teams you would actually trust with your life. A surgical team. A flight crew. A rescue team. None of them coordinate by talking more. They coordinate by having trained the same standard so deeply that a few words carry an enormous amount of meaning. When a pilot says a specific phrase, the first officer knows exactly what happens next, because both of them built the same model in advance. That is not less communication because they care less. It is less communication because they built more standard.

What the research says

This is one of the most studied ideas in team science, and it did not come out of a business school. It came out of places where coordination failure kills people.

Eduardo Salas and Janis Cannon-Bowers spent decades studying how teams coordinate under load, much of it for the military. Their model of teamwork identifies shared mental models and closed-loop communication as core coordinating mechanisms that link team behavior to real outcomes. Closed-loop communication is worth a second, because it is the discipline underneath the quiet. The sender sends a message, the receiver confirms they got it, and the sender verifies the confirmation. Three beats, every time, so nothing important is ever assumed. It looks almost mechanical on paper. In practice it is what lets a team stay quiet, because closing the loop once removes the need to keep circling back.

In one study, Renée Stout, Cannon-Bowers, Salas, and Dana Milanovich found that teams that planned together built stronger shared mental models, and those models let them communicate more efficiently under heavy workload while still coordinating well. Read that carefully, because it is the whole argument in one finding. The teams that did the shared work up front needed less communication when the pressure hit, not more. A larger study by Mathieu and colleagues, published in the Journal of Applied Psychology in 2000, confirmed the link directly: the more a team's mental models converged, the better its process and the better its performance.

The standard does not just make a team faster. It makes a team quieter, and the quiet is a feature, because it frees up the attention that a struggling team spends on live coordination.

Two industries that proved it with lives on the line

If you want to know whether shared standards work, look at what happens when an industry adopts them after enough people have died from the lack.

Start with aviation. On December 28, 1978, United Airlines Flight 173 ran out of fuel and crashed near Portland, Oregon, while the crew troubleshot a landing gear problem. The aircraft was mechanically sound. The crew was experienced. The first officer and flight engineer had told the captain the plane was low on fuel, and the captain did not act on it. People died not from a lack of skill but from a failure of coordination inside the cockpit.

After that crash, NASA held a workshop in 1979, and a NASA psychologist named John Lauber coined a term for the fix: crew resource management. Its core was standardization. The training drilled crews in a shared language and required them to confirm instructions and to speak up when something looked wrong. United Airlines launched the first comprehensive program in 1981, and over the following years the rest of the industry followed. By the 1990s, crew resource management had become a global standard. The industry did not fix its accident rate by telling pilots to communicate more in some vague way. It gave them a shared standard so that the few words they did exchange could not be misread.

Then healthcare borrowed it. In 2002, Michael Leonard, Doug Bonacum, and Suzanne Graham at Kaiser Permanente in Colorado adapted a US Navy submarine communication protocol for hospitals and called it SBAR: Situation, Background, Assessment, Recommendation. They built it to bridge a specific gap, the mismatch between how nurses learn to communicate, in long narrative, and how physicians learn to receive, in short bottom-line. Kaiser had traced real communication failures to those differences in personal style. SBAR flattened the differences by giving everyone the same four-part structure, so the facts moved from person to person with fewer mistakes. It worked well enough that the Joint Commission built standardized handoffs into a national patient safety goal.

Notice what both fixes have in common. Neither one asked people to talk more. Both gave people a shared standard so that less talk carried more meaning, and the meaning could not get lost. That is the quiet team, engineered on purpose in places where the cost of the noisy team is measured in lives.

The standard nobody has to enforce

Here is the distinction that took me years in the field to really understand. There is a difference between a rule and a standard, and it is the difference between a team that needs supervision and a team that runs itself.

A rule is something imposed from outside that requires enforcement. Someone has to watch, catch violations, and apply a consequence. The moment the enforcement stops, the behavior drifts, because the rule never lived inside the people. It lived in the person watching them.

A standard is different. A standard is a shared picture of what "right" looks like that the team holds for itself. Nobody has to enforce it, because everyone already carries it and everyone expects it of each other. In the teams I worked with, the standard was not on a poster and no supervisor policed it. Everyone simply knew what the standard was, held themselves to it, and quietly held each other to it. You did not meet the standard because someone was watching. You met it because the person next to you was also meeting it, and letting them down was unthinkable.

That is the target for any team leader who wants the quiet. You are not trying to write better rules. You are trying to build a shared standard so genuine that the team maintains it without you in the room. When you get there, two things happen at once. The coordination gets quiet, because everyone can predict everyone else. And the enforcement burden disappears, because the team holds the line itself. That is what people are actually looking at when they admire a team that seems to run on its own. They are looking at an internalized standard.

How to build the quiet: a practice

You do not get a shared standard by announcing one. You build it, deliberately, and here is the sequence that works.

Define what "right" actually looks like, in the concrete. Not values. Not adjectives. The specific, observable picture of a job done to standard. If two members would describe strong work differently, you do not have a shared standard yet, you have a shared word. Get specific enough that the picture is the same in every head.

Plan together before the pressure, not during it. The research is blunt about this: teams that plan together build stronger shared models and then need less communication when the workload spikes. The planning is where you install the model. Skip it and you will pay for the coordination later, live, at the worst possible time.

Build the shared language. Give the recurring situations short, precise names that mean the same thing to everyone. When a term carries an agreed meaning, one word replaces a paragraph, and the paragraph is where misreads live. This is exactly what crew resource management and SBAR did.

Close the loop, every time. Adopt the discipline of confirmation. A message sent, received, confirmed, and verified. It feels slightly formal at first. Within weeks it becomes the thing that lets you stop double-checking, because you know the loop always closes.

Then get out of the way and watch the volume. Once the standard is real, your job is to protect it, not narrate it. And you will have a live gauge for whether it took: the talking. If coordination is getting quieter, the model is working. If the team is still talking constantly, the standard has not landed yet, and the fix is to sharpen the picture, not to add another meeting.

Common mistakes

Mistaking activity for alignment. A team that communicates constantly looks engaged and can be deeply misaligned. Volume of talk is not a measure of coordination. Often it is a measure of its absence. Watch what the talk is doing. If it is re-clarifying things that should already be settled, that is a missing standard, not a healthy culture.

Prescribing more meetings for a coordination problem. When a team is not coordinating, the reflex is to add a sync. If the problem is a missing shared model, another meeting just generates more competing pictures. Build the standard first. The right number of meetings drops out of that, and it is usually lower.

Confusing a shared standard with rigid scripts. The goal is a shared picture, not a robotic one. A real standard tells a team what "right" looks like and still lets them adapt to a situation you did not foresee. Aviation and medicine did not remove judgment. They gave judgment a common floor to work from.

Writing the standard instead of building it. A standard on a wall is a rule waiting for an enforcer. A standard in people is something they carry and defend on their own. You do not get the second one by publishing a document. You get it by defining "right" together, practicing it, and holding it until it becomes theirs.

Frequently asked questions

Isn't communication a good thing on teams?

Good communication is essential. More communication is not the same thing, and the two get confused constantly. The best teams communicate with remarkable precision, which usually means they talk less, because a shared standard lets a few words carry a lot. The goal is not maximum talk. It is maximum shared understanding with minimum overhead, and past a point, more talk actively works against that.

How is a shared standard different from just having good documentation?

Documentation lives on a page. A shared standard lives in people. You can hand a team a perfect process document and still watch them coordinate badly, because no one internalized the picture. The document is a starting point at best. The standard only exists once every member can predict what the others will do without looking anything up.

We added stand-ups and check-ins and things did not improve. Why?

Almost certainly because the problem was a missing shared model, and more meetings do not build one. They just create more venues for people to discover they were picturing different things. The fix is upstream: define what "right" looks like concretely, plan together, and build a shared language. Do that and the coordination gets quieter, and you will likely need fewer of the meetings you added.

Does this apply to creative or knowledge teams, or only to high-stakes operational ones?

It applies anywhere work is interdependent. The aviation and medical examples are vivid because the cost of failure is a life, but the mechanism is the same for a product team or a deal team. Wherever people have to hand off to each other, a shared picture of the goal, the roles, and the standard reduces the coordination tax. The stakes change. The physics of coordination do not.

Won't standardizing communication make my team robotic?

Only if you standardize the wrong layer. You are not scripting what people think. You are giving them a common floor for how they coordinate, which frees up attention for the judgment that actually needs a human. Crews and surgical teams are not robotic. The shared standard is exactly what lets them improvise safely when something unexpected shows up, because the basics are handled and their full attention is available for the surprise.

Back to the quiet

The quiet team I watched all those years ago was not made of quiet people. Put them at dinner and they were as loud as anyone. The quiet showed up only when they worked, and it showed up because they had done the loud work earlier, in the planning and the training and the arguing about what "right" looked like, until the picture was the same in every head.

That is the part most organizations skip. They want the quiet without doing the loud work that earns it, so they reach for the only lever they know, which is more communication, and they get a louder team that coordinates worse. The teams worth admiring did the opposite. They front-loaded the noise into building a shared standard, and then they got to be quiet when it counted.

You do not talk your way to a great team. You build the shared picture, and then the team gets quiet, because it finally has nothing left to explain.