Smart Event Studio

Orgs lose 10%–30% of every work year to ineffective communication.

Axios dropped their 2026 State of Workplace Communication report this week, and that's the headline finding.

If you think THAT sounds high, the salary math makes it worse:

Employees earning $100K–$150K are losing the equivalent of $19,000 a year.
At $200K+, it's over $51,000. Per person. Per year.

The super-surprising stat: there's a nearly 40-point gap in performance outcomes — revenue, retention, customer loyalty, team engagement — between organizations that invest in aligned communication tools and training and those that don't.

This is money walking out the door because of the way information moves inside your organization.

This is all near and dear to my heart, because one of the things I've been fixated on lately is message sprawl.

You know exactly what this looks like: 30 minutes spent hunting down a decision that was made in a chat thread nobody can find. Finally, a meeting gets scheduled because no one can find the original comm.

It gets treated as the cost of doing business. But it doesn't have to be.

The fix isn't a platform overhaul. It's a decision — what is our source of truth for work items, and how does everything get there?

A few things that actually work:

If your project board has an email address — and most do — you can email a Slack or Teams message directly into it. It becomes a task. The thread stops being the record.
AI-powered connectors that automatically pull tasks out of call recordings and automatically add them to your system of record
When something comes in through chat, the standard response becomes: can you make a ticket for that? It's not a bureaucratic hurdle — it's a shared agreement that random messages are not a tracking system.
In Slack or Teams, you reference the ticket — not the conversation. Everyone knows where to look, and status is visible without asking.

That's process. That's also culture — and culture is just the thing your team does consistently enough that it stops being a decision.

I've seen teams run this so tightly it borders on annoying. Every request ticketed, every status visible, every Slack message cross-referenced. The team grumbles about it until the first time they don't have to spend forty minutes hunting something down.

I've also seen the other version. Twenty-seven open chat threads about a single issue, no ticketing system, no source of truth, no shared understanding of where work actually lives. Somehow things get done — until they don't, and nobody can figure out why.

The difference between those two teams isn't talent. It's infrastructure.

Axios confirmed what most of us already suspected: the cost of this just being "the cost of doing business" is real, it's measurable, and it compounds. Our event teams feel it faster than most — the timeline is fixed, the dependencies are cross-functional, and there's no pushing the date to buy more runway.

If this is your organization and you want to talk through what reducing this hidden tax could look like, reach out: jen@smarteventstudio.com.

‍