How Do Improve Communication Without More Meetings?

You probably don't need another meeting.

Seriously.

Most of the communication problems I see inside businesses aren't because people refuse to communicate. They're because the business makes communication unnecessarily fucking hard.

People are working in silos on work that crosses departments. Nobody can see the status of something without asking. Roles overlap enough that nobody is completely sure who owns what. Next steps get discussed in a meeting but never captured anywhere.

Then something gets missed and everybody starts pointing fingers.

“Why didn't you tell me?”

“I thought you knew.”

“I thought she was handling it.”

“Nobody told me that changed.”

“I was waiting on them.”

And suddenly we're having another conversation about how everyone needs to communicate better.

Okay.

But how?

If People Have to Ask for a Status Update, You Have a Visibility Problem

This is one of the first things I'd look at.

How does someone know where a piece of work stands right now?

Can they see it?

Or do they have to ask someone?

Because if Sales has to message Operations to find out whether a new client has been onboarded, Operations has to ask Accounting whether an invoice went out, and the owner has to ask everybody where the hell a project stands, you've built communication into the basic mechanics of getting information.

That creates a shit ton of unnecessary conversation.

And worse, it means everyone is operating with a different amount of information.

Good systems create visibility.

I should be able to see that something is waiting on the customer.

I should be able to see that Susan owns the next step.

I should be able to see that the proposal was approved but onboarding hasn't started.

I shouldn't need to hunt Susan down and ask her.

Visibility eliminates communication that never needed to happen in the first place.

Cross-Department Work Can't Live in Department Silos

This is where communication gets really messy.

Sales has its process.

Operations has its process.

Accounting has its process.

Admin is somehow floating between all three trying to keep everyone from killing each other.

But the customer doesn't move through departments.

They move through the business.

The work Sales starts eventually becomes work Operations needs. Something Operations does eventually triggers something Accounting needs. Information collected in one place matters somewhere else.

If every department is managing its piece independently, the handoffs between them become completely dependent on people communicating perfectly.

And people do not communicate perfectly.

They get busy.

They assume.

They forget.

They thought someone else already told you.

They mentioned it in a meeting three days ago while you were answering an email and apparently that was supposed to become part of your permanent memory.

That's not a communication strategy.

Cross-department workflows need to show how the work moves through the whole business, not just what each department does once it lands on their desk.

Otherwise, the cracks between departments become the place everything falls into.

Helping Someone Doesn't Mean You Own Their Job

Blurred roles make this even worse.

Someone gets busy, so another person jumps in.

Good.

That's what healthy teams do.

But somewhere along the way, helping can quietly become ownership.

And admins get absolutely murdered by this.

Admin supports Sales, so somehow they're responsible when Sales doesn't follow up.

Admin helps Operations, so somehow they're responsible for knowing the status of every project.

Admin schedules something for the owner, so apparently they're now responsible for making sure the owner remembers every commitment they made.

No.

Supporting someone else's work does not transfer ownership of that work.

And I promise you, Karen isn't secretly plotting to take over Steve's job.

She's probably picking up the slack because the thing needed to get done.

The problem isn't that people are “stepping on each other's toes.”

The problem is that nobody can clearly see whose toes these are supposed to be.

You need visibility into responsibility.

Who owns the outcome?

Who is supporting?

Who needs to be informed?

Who makes the decision?

And when someone helps temporarily, ownership shouldn't silently move with the task.

That's how good employees end up overloaded while other people slowly stop owning things they were supposed to own.

A Conversation Is Not a Workflow

This one might be my favorite.

You have a meeting.

Everyone talks.

Decisions get made.

Next steps are discussed.

Everybody leaves feeling productive.

Three days later:

“What were we doing with that?”

Because apparently the system was everyone remembering the conversation.

Absolutely not.

If a conversation creates an action, capture the action.

Who owns it?

What exactly are they doing?

When is it due?

Who needs to know when it's complete?

Does completing it trigger something for someone else?

Put it somewhere visible.

Because “we talked about it” is not the same thing as assigning it.

And saying something out loud to six distracted adults does not magically create a workflow.

Someone will forget.

Someone will remember it differently.

Someone will assume someone else wrote it down.

Someone will miss the part that mattered to them because they were thinking about the fire waiting on their desk.

Remembering is not a system.

It's definitely not a good one.

Better Communication Often Means Needing Less of It

This is the part that sounds backward.

When businesses complain about communication, the instinct is usually to add more communication.

More meetings.

More check-ins.

More messages.

More updates.

More people CC'd “just in case.”

I usually want to do the opposite.

Make ownership visible.

Make status visible.

Connect the work that crosses departments.

Capture next steps when they're decided.

Make handoffs obvious.

Make sure people know what they own versus where they're simply supporting someone else.

Then let the system carry the routine information.

Now your team can communicate about the shit that actually requires human brains: problems, exceptions, ideas, judgment, customers, decisions.

Not:

“Hey, just checking on the status of this?”

for the 900th time.

Because the goal isn't to build a team that communicates constantly.

It's to build a business where people don't have to constantly ask each other what the hell is going on.