You've Talked About the Work More Than You've Done the Work — And That's a Problem

Somewhere between the Monday morning alignment chat, the Tuesday pre-brief Slack thread, and the Wednesday "quick sync before the sync," something slipped through the cracks. The actual work.

It sounds absurd when you say it out loud. But walk through a typical week on a mid-sized US team right now and you'll find a peculiar pattern: the conversations about doing things have started to crowd out the doing of things. There's a prep chat before the meeting. A debrief after the meeting that somehow becomes the setup for the next meeting. A group message thread where everyone "aligns" before anyone's even opened the document.

At some point, communication stopped being a tool and started being the job itself.

How We Got Here

This didn't happen out of malice or laziness. It happened because coordination genuinely matters — and most teams learned that lesson the hard way after a few painful miscommunications. One badly scoped project, one stakeholder blindsided by a decision, one launch that went sideways because two departments weren't on the same page, and suddenly everyone is determined to over-index on alignment.

The instinct is understandable. The execution is where things fall apart.

Psychologists who study group behavior have a name for this tendency: process inflation. When teams feel uncertain — about scope, about authority, about whether their work will land well — they compensate by adding more communication steps. Each added layer feels productive in the moment. It signals care, diligence, and collaboration. What it actually does is delay the point at which anyone has to make a real decision or produce a real output.

In a messaging-heavy environment, process inflation is turbo-charged. It's cheap and easy to fire off a "hey, should we loop in Sarah before Thursday's call?" message. It takes about fifteen seconds. But that message triggers a thread. The thread needs a resolution. The resolution probably involves a calendar invite. And now you've added ninety minutes to the week before anyone's touched the actual deliverable.

The Three Layers Nobody Talks About

Most teams are aware of their official meeting overhead — the recurring standups, the sprint reviews, the all-hands calls. What they don't audit are the informal communication layers that have grown up around those official touchpoints.

Layer one: The pre-brief. This is the message or quick call that happens before a meeting to make sure everyone shows up "prepared." In theory, it replaces the awkward silence while people catch up inside the meeting. In practice, it often duplicates the agenda entirely, meaning the meeting itself becomes a formality — a performance of a decision that was already made in a DM chain.

Layer two: The alignment check. This is the "just wanted to make sure we're all on the same page" message that circulates after a decision has theoretically been reached. It's not a bad impulse — miscommunication is real and costly. But when alignment checks become reflexive rather than purposeful, they signal something deeper: the team doesn't actually trust its own decision-making process enough to let decisions stick.

Layer three: The post-meeting thread. The call ends. The Slack channel lights up. People share what they really think, flag the things they didn't say out loud, and sometimes reverse the conclusions that were just reached. This layer is the most insidious because it feels like healthy informal communication — and sometimes it is — but it regularly becomes a shadow decision-making process that undermines the official one.

Stack all three layers on top of each other and you've built a communication architecture that takes more time and energy than the work it's supposedly supporting.

Why Smart People Keep Doing This

Here's the uncomfortable truth: over-communication often benefits individuals even when it costs teams.

If you send the pre-brief, you look organized. If you run the alignment check, you look thorough. If you kick off the post-meeting thread, you look engaged. Each individual action is socially rewarded, even as the collective result is a team running in place.

There's also a cover-your-bases dynamic at play. In organizations where blame travels fast and credit moves slow, adding communication layers is a form of risk management. If a project goes wrong, you want a paper trail showing you flagged concerns, looped in stakeholders, and checked for alignment. The messaging platform becomes less a collaboration tool and more a documentation system for distributed accountability.

None of this is cynical behavior — it's rational behavior inside a broken system. The fix isn't to shame people out of over-communicating. It's to build team norms that make doing the work feel safer than talking about the work.

A Framework for Cutting the Layers

The goal here isn't to gut communication. It's to make it earn its place on the calendar.

Run the "what changes?" test. Before scheduling any pre-meeting chat or sending any alignment message, ask: what decision or output changes as a result of this communication? If the honest answer is "nothing — we're just making sure everyone feels included," that's a signal to find a lighter-weight way to achieve that goal. A shared doc with context notes often does the job a thirty-minute call was doing.

Assign communication ownership. One of the reasons pre-briefs multiply is that nobody explicitly owns the responsibility of making sure a meeting is useful. When that ownership is distributed, everyone hedges by doing a little pre-communication of their own. Designating a single person to prep and circulate context before a meeting — and trusting that it's enough — cuts the redundancy significantly.

Create a "cool-down" norm for post-meeting threads. Not every reaction to a meeting needs to become a new conversation. Teams can experiment with a simple norm: hold non-urgent reactions for twenty-four hours before posting. You'll find that a lot of what felt urgent in the moment resolves itself, and the threads that do materialize tend to be more substantive.

Audit your channel structure. Sprawling group messaging setups are a breeding ground for redundant communication because it's never clear where a conversation is supposed to live. When people aren't sure which channel to use, they use all of them — and the same information gets shared three times in three places. A leaner, more intentional channel structure forces clarity about where communication is supposed to happen and why.

The Actual Goal of Team Communication

Here's the reframe that tends to shift things: communication isn't the output. It's the infrastructure that supports output. Roads are useful, but you don't build roads to build roads.

The best-functioning teams treat messaging and meetings as means to an end — and they're ruthless about evaluating whether a given communication moment is actually moving something forward. They're not cold or dismissive about it. They still make room for relationship-building, casual conversation, and genuine check-ins. But they've drawn a clear line between communication that serves the work and communication that replaces the work.

That line is worth drawing on your team, too. Because right now, somewhere in your message history, there's a thread that consumed four hours of collective attention — and the decision it was supposed to inform still hasn't been made.

That's not a collaboration problem. That's a communication problem. And it's one your team is absolutely capable of solving.