How do mid-sized companies share company-wide updates with employees?

Somewhere between 200 and 2,000 employees, something breaks. Not dramatically — nobody notices the exact moment it happens. But the all-hands email that used to reach everyone starts landing in inboxes people don't check. The Slack channel that once felt like the company's town square turns into noise. And leadership starts asking a question that smaller companies never have to ask and larger ones have already given up on: does anyone actually see what we send out?

This is the mid-size problem, and it's a real one. Small companies communicate by proximity — you can walk over and tell someone something. Large enterprises build entire departments around comms, with budgets and tooling to match. Mid-sized companies sit in the gap. Too big for hallway conversations to carry the weight, too small to justify a dedicated internal comms team with its own stack. So updates get patched together with whatever's on hand: email, Slack, maybe a monthly newsletter someone in HR puts together in their spare time.

The result, more often than not, is a communication style built entirely around volume rather than reach. More emails. More channels. More reminders to "check the pinned message." And still, somehow, half the company finds out about a major policy change three weeks after it happened, from a coworker, in passing.

This isn't just a feeling. Gallup's most recent engagement data puts a number on it: less than half of employees strongly agree that they even know what's expected of them at work. That's not a comms metric specifically — it's Gallup's baseline measure of workplace clarity — but it's a reasonable proxy for how much information genuinely lands versus how much just gets sent. If companies are struggling to communicate the basics of a role, a company-wide policy update buried in week eleven of a busy quarter doesn't stand much of a chance.

The channel problem isn't really a channel problem

It's tempting to treat this as a tooling issue — pick the right platform and the problem solves itself. That's rarely true. The deeper issue is that most mid-sized companies are using channels built for conversation to do the work of broadcast. Email is asynchronous but easily buried. Slack is fast but ephemeral; scroll past a message and it's effectively gone. Neither was designed to answer the question "where do I go to know what's happening at this company," because neither was designed to be a system of record. They're built for exchange, not for reference.

Axios HQ's 2025 State of Internal Communications research shows just how far this gap has drifted. Only 14% of employees say the intranet is where they'd actually choose to get important updates, yet leaders reach for it — and for employee apps, and digital signage, and a handful of other broadcast-style channels — far more often than employee preference would suggest is useful. Leaders are, in effect, over-investing in the channels employees trust least and under-investing in the ones — email and newsletters, mainly — that employees say they actually read.

What tends to happen instead — and this is the part worth naming — is that companies start treating "we sent it" as functionally equivalent to "they know it." An email goes out, a box gets checked, and if someone later says they didn't know, the response is some version of "it was in the newsletter." Technically true. Practically useless.

What actually works at this size

The companies that get this right tend to do a few things differently, and none of them are especially glamorous.

First, they separate the update from the conversation about the update. A company-wide announcement lives somewhere stable — a single, findable place — while the discussion, questions, and reactions happen wherever people naturally talk. This sounds obvious written down. It's rarely how things actually work in practice, where the announcement and the discussion are the same Slack thread, and within a day the original message is buried under forty replies about the Q3 offsite.

Second, they stop assuming reach means comprehension. Sending something isn't the same as it landing. Leaders tend to be the last to find this out: in the same Axios HQ research, 72% of leaders believe their internal communications go out on a timely, reliable cadence their teams can count on. Only 48% of employees agree. That's roughly a person a coin-flip away from feeling informed on any given update — which is a strange place for a company to be comfortable operating from. The organizations that do this well build in some form of confirmation — not a compliance checkbox, but a genuine signal that the message got through: a quick reaction, a short pulse survey, a follow-up in a team meeting. It doesn't need to be sophisticated. It just needs to close the loop.

Third — and this is the one that gets skipped most often — they think about who the update is actually for before they write it. A company-wide update isn't one message; it's usually several audiences reading the same words for different reasons. Engineering wants to know if this affects their sprint. Sales wants to know if it affects a client conversation this week. Finance wants numbers. Writing a single message that tries to answer all of those questions at once usually ends up answering none of them well, which is part of why so many company updates read like they were written to satisfy a legal team rather than to inform actual humans.

The role of a searchable home base

There's a reason "just search the intranet" sounds like a punchline at so many companies: because for years, intranets were where information went to be buried, not found. That reputation is earned. Most legacy intranets were built as static repositories — dump the PDF, tag it vaguely, hope for the best.

But the underlying idea was never wrong. Employees do need one place they trust enough to check when they're not sure where else to look. The failure was execution, not concept. A well-structured knowledge hub — one that's actually maintained, actually searchable, and actually tied into the tools people use daily — does something Slack and email fundamentally can't: it gives an update a permanent address. Six months later, when someone new joins the team and asks "wait, did we change the expense policy?", there's an answer that doesn't depend on someone's memory of a Slack thread from March.

This matters more at mid-size than at almost any other stage. Small companies can rely on institutional memory because there isn't much distance between any two people. Large enterprises have entire knowledge management functions dedicated to exactly this problem. Mid-sized companies have neither the built-in proximity nor the dedicated resourcing — which is precisely why the gap shows up here first, and why it tends to get worse as the company grows rather than better on its own.

The uncomfortable truth

None of this is really about finding the perfect tool. It's about accepting that as a company grows, information stops moving by default and has to be moved on purpose. That shift is uncomfortable because it means someone has to own it — decide what counts as a company-wide update, decide where it lives, decide how you'll know if it worked. Most of the chaos in mid-sized company communication doesn't come from a lack of channels. It comes from a lack of ownership over which channel does what.

It's also, frankly, a gap most leadership teams underestimate. Axios HQ found that 27% of leaders believe their staff are fully aligned with the company's business goals. Among the employees actually being asked, that number drops to 9%.

That's two groups of people looking at the same company and seeing entirely different levels of clarity. Closing that gap doesn't require more communication. It requires communication that's built to be found, not just sent.

Get that right, and the rest — the tools, the cadence, the format — becomes a much smaller problem to solve.

Frequently asked questions

Why do updates that work fine at a small company suddenly stop landing once it grows?
Small companies communicate through proximity. Someone hears something because they happen to be near the person who said it. That stops scaling once a company passes a certain size, and most companies never replace it with anything deliberate. The update volume goes up, but the channels doing that work were never built to be searched or referenced later, so more effort produces the same gap.

Is the fix just choosing a better communication tool?
Not on its own. The research cited above shows leaders consistently overusing channels employees don't actually prefer, while underusing the ones they do read, like email and newsletters. Swapping one tool for another without addressing that mismatch, or without deciding who owns which kind of update, tends to reproduce the same problem in a new interface.

How can a company tell if its updates are actually landing, not just being sent?
Sending confirms delivery, not comprehension. A simple signal, a quick reaction, a short pulse survey, a manager checking understanding in a team meeting, closes that loop without requiring anything elaborate. The absence of any such signal is itself a sign that "we sent it" and "they know it" are being treated as the same thing when they aren't.

Does this problem get worse or better as a company keeps growing past mid-size?
Left alone, it tends to get worse, since every new hire adds another person relying on channels that already don't reach everyone. Large enterprises eventually build dedicated internal comms functions specifically to manage this. Mid-sized companies are usually past the point where proximity works and before that kind of dedicated resourcing exists, which is why the gap tends to show up here first and linger longest.

What's the first practical step for a mid-sized company trying to fix this?
Deciding where company-wide information actually lives, and who's responsible for keeping it accurate there. That single decision, more than any specific tool, is usually what separates companies that close this gap from ones that keep adding channels without solving the underlying issue.

Ready to tackle information chaos? Book a consultation today.