Internal Communications

Internal communications is hired to close the gap between "the company decided something" and "the people who need to act on it actually know." That gap is where quarterly objectives quietly die. The pattern shows up every post-mortem: the decision was made, the email went out, nobody on the frontline read it, and three weeks later the data reveals no one adjusted behavior. IC's real product isn't the message. It's the measurable change in what employees do next.

Take a 120-store quick-service restaurant chain rolling out a new cash-handling procedure after a regional shrink spike. Corporate drafts an announcement. The IC team targets it to shift leads only (not all crew), pairs it with a 40-second video in English and Spanish, gates the next shift clock-in behind an acknowledgment tap, and tracks which stores hit 95% acknowledgment by Friday. Two weeks later, shrink data gets re-checked against acknowledgment rates. That feedback loop — message → targeted delivery → acknowledgment → behavior metric — is what separates IC-as-a-department from IC-as-a- broadcast-function.

The IC team's dashboards almost always overstate reach. "Sent to 12,000" is not "read by 12,000." Open rates on intranet posts are usually in the 20–35% range for corporate and 5–15% for frontline. The honest IC leaders know this and plan for it: critical messages get a second channel, a third pull through managers, and an acknowledgment gate. The ones who don't end up in a crisis meeting explaining why "we sent that email in February" didn't prevent the safety incident in April.

In healthcare, internal communications sits on top of a regulatory reality that retail and tech don't share. A 2,000-bed hospital system has messages that must legally reach every person in a role by a specific date — Joint Commission readiness, OSHA updates, drug recalls. "Engagement" isn't optional; failure to reach is a compliance event. IC teams in healthcare end up running two parallel systems: the engagement side (newsletters, CEO videos, the culture stream) and the compliance side (targeted, acknowledged, auditable). The teams that combine them into one channel do both jobs better.

By 2027, the "one message for everyone" model is dying. Generative AI makes it trivial to produce the same announcement in nine role- appropriate versions — a paragraph for managers, a two-sentence push for floor staff, a data-dense summary for analysts, each in the reader's language. The shift isn't that IC writes faster. It's that writing-the-master-version becomes less than half the job; the rest is choosing the audiences, the channels, and the acknowledgment strategy, and then measuring which versions moved behavior. The IC manager who spends Monday mornings editing a newsletter is doing the obsoleted work.

• One channel fits all. Email for HQ, intranet for office, and nothing for the plant floor — the signal never reaches half the company.
• Writing for the sender, not the reader. Corporate announcements in corporate voice land in a 5-inch phone screen in a breakroom. The message has to survive that context.
• Confusing send volume with reach. Three newsletters a week isn't engagement; it's training employees to ignore the sender.
• No closed loop. If the IC team doesn't know which messages moved which behavior, every program decision is anecdotal.
• Owning only the channel, not the outcome. When IC is scoped as "we send the messages HR writes," the team gets blamed for every missed acknowledgment without the authority to change the message, the audience, or the cadence.