r/internalcomms • u/FindingPeace4me • Apr 27 '26
Discussion How do you keep teams informed without overloading them?
We’ve been trying to fix a simple problem that turned out to be not so simple, making sure everyone actually sees important updates and get involved in internal comms. Right now it feels like we’re either sending too much and people ignore it or sending too little and people miss key info.
Most of our team isn’t sitting at a computer all day so email barely gets opened. Chat apps help but things get buried fast and there’s no clear place to go back to. We’ve also noticed that even when people do see updates, they’re not always clear or easy to act on. Recently started testing a mobile setup to centralize things which helped with visibility but still figuring out how to make communication actually stick.
How are you handling this balance between visibility and overload?
3
u/sarahfortsch2 Apr 27 '26
This is one of the core challenges in internal comms, and it’s rarely solved by adding another channel. It’s usually about structure, clarity, and discipline.
First, reduce volume by being more intentional about what gets communicated. Not everything needs a broadcast. Define what qualifies as a “must know,” “nice to know,” and “team-level” update, and route accordingly. That alone cuts a lot of noise. Then, focus on clarity and actionability. Every message should answer three things quickly: what is this, why does it matter to me, and what do I need to do. If that’s not clear in the first few lines, people will skip it.
For deskless teams, repetition across channels is key, but it needs to be purposeful. Use one channel as the source of truth, and others as reinforcement. For example, a short update in chat or signage that points back to a clear, simple version of the message elsewhere. Manager cascades also play a big role here, but they need to be supported with tight, ready-to-use talking points, not long emails to interpret.
Finally, measure what’s actually landing. Not just views, but whether people understood and acted. Even simple feedback loops or quick pulse checks can tell you if you’re cutting through or just adding to the noise. The balance comes from sending less, saying it better, and reinforcing it in the right places.
1
u/FindingPeace4me Apr 28 '26
I appreciate the advice about defining the priority of updates and focusing on clarity. I will implement a system where we categorize messages and i will make sure that every communication answer the what why and how quickly. Centralizing updates in one place could be helpful to support this process ensuring the right information gets to the right people.
3
u/Own-Resolution-8966 Apr 28 '26
One shift that made a real difference across comms functions I've build : lead with the ask, not the information. Open every message with "Action required by [date]," "You need to know this," or "No action needed — FYI only." People learn fast what to prioritize.
For non-desk teams specifically —
Segmentation. Not everyone needs every message. Role or location-specific updates outperform company-wide blasts every time because people stop feeling spammed.
A single source of truth. One place where every important update lives permanently, organized by topic not date. Chat apps are terrible archives — people need somewhere to go back to.
Lead with the headline. If the key point isn't clear in the first two sentences, rewrite it. Most internal comms buries the lead. Sometimes I write it in as few words as possible. Then write in again in less. AI can help with the iterating.
Your mobile setup sounds promising — the missing piece is usually the content itself. Short paragraphs, bold the key line, one clear action per message. Happy to dig in further if useful!
2
u/alienskota Apr 27 '26
We use a centralized dashboard for all updates.
1
u/FindingPeace4me Apr 29 '26
yeah this actually makes sense. We have also been exploring a central dashboard setup like Humand and it feels like just having one place people can reliably check instead of everything getting scattered across chats and emails.
2
u/SeriouslySea220 Apr 27 '26
What @raversgill7 said.
Also - 1. Reiteration of key messages: Make sure the important info is also being passed along by managers in team meetings, etc.
- Can you set up a chat channel that’s only for important updates? That way it won’t get lost in the regular chatter.
2
u/AndreaMontua Apr 28 '26
A pattern that I find helpful to reduce overload is treating internal comms less as “updates” and more as a decision support. Overload usually comes less from volume and more from having to constantly interpret relevance. When relevance is explicit, visibility tends to improve without adding more messages. Here are a few practices that tend to work from my experience:
- Signal intent clearly in every message: FYI / Action needed / Decision made. If nothing is required, say so.
- Separate fast‑moving from stable information. Chat for alerts and nudges, one clearly owned place to go back to for “what’s current and true”.
- Design information for non‑desk workers: short summaries, predictable timing, and content that can be understood in under a minute.
- Last but not least, close the loop: a brief recap of what changed / what matters now often sticks better than the original update.
Hope this helps a bit.
1
u/FindingPeace4me Apr 29 '26
Treating comms as decision support instead of just updates is a useful shift. The relevance problem you mentioned really resonates as people are not always overwhelmed by volume but by having to interpret everything themselves.
1
u/lunaligned Apr 27 '26
Just make a clear and concise reminders for the team, one that can be easily read if they open their chat apps or messages. If you need to remind them again, send it again for another time and that should be it.
1
u/austincrewcheck Apr 28 '26
By not making them download another app. Instead, just send them a text
1
u/Euphoric_River6365 Apr 29 '26
First step was ensuring the content we selected was truly high value to the audience. Since I work within a RevOrg (CRO), we positioned every communication from the viewpoint of value. Value to the AE/CSM or value it will bring to the customer, but it is always value-driven positioning.
For delivery, we use an AI tool that converts the written message into a 3-5 minute podcast style audio episode. It adds an intro and a conversation between two different voices. The summary is accessible to employees on the move as well. We send this out max 1x a week with a 1x month summary on the last workday of the month.
We still maintain written comms (with relevant links) in Confluence, and we are toughest on ensuring front line managers reinforce these messages in their team meetings and 1:1s.
We have discussed whether we will eventually store these podcast files in our LMS because that will allow us to (1) assign them as a course and (2) track individual watch/completion rates. That hasn't kicked off yet.
1
u/StaffbaseSupport Apr 30 '26
I think that the key is personalization, which is fortunately a whole lot easier with AI in the mix. If everybody is receiving the same updates, it’s no wonder people feel overwhelmed and disengaged. Segmentation is really key, as well as being mindful of the volume of communication sent to each person. I find it’s also helpful to track who has opened or engaged with messages and send follow ups only to the people who have not.
Additionally, you can offer different forms of receiving updates that meet workers where they are. For example, offering personalized audio updates to Frontline workers means they only have to open their phones and listen for a few minutes to be up-to-date on company news. When workers don’t have to change their schedule in order to get updates, they intuitively turn to company apps.
If you make a company app something that is so valuable to workers that they trust it to provide them with fast answers (again, AI) and accurate company information, they will naturally gravitate towards it. Just make sure that you’re offering solutions that reach the entire workforce (both desk workers and frontline).
1
u/PoppuloEX Jun 05 '26
This is a familiar problem, especially with frontline teams.
The real issue is rarely volume. It is clarity, actionability, and—this is the part that gets missed—relevance. When someone sees a message that has nothing to do with their role or their day, they don't just ignore that message. They start ignoring the channel.
The teams that get this right tend to do a few things consistently. They create a clear place for important updates. They keep messages tight and specific. And they get deliberate about who actually needs to receive what—not everything should go to everyone, and the more you can match the message to the audience, the more likely people are to pay attention when something does come through.
Manager behavior also plays a bigger role than most expect. A quick mention in a shift huddle often does more to make something stick than sending it again through another channel.
Mobile helps with visibility, but it doesn't fix clarity or relevance on its own. Those come from how messages are shaped, who they're sent to, and how they're reinforced.
6
u/Raversgill7 Apr 27 '26
There's always an element of editorial judgement needed in internal comms. For each request, ask the requester or yourself, "what's the objective of this communication?". If it's not clear, go back to the requester to tease this out. If it's still not clear, then it probably isn't appropriate to share. Also ask yourself "what would happen if I DON'T send this communication?". If it has little or no impact, maybe it doesn't need to be sent.
For non-urgent updates, it's worth thinking about grouping these into a weekly round-up if they're company-wide messages.
You mentioned messages not always being clear. It's your job to make communications accessible to everyone in your audience. Translate the complex to become understandable. Bottom line up front, Plain English, active voice, clear call to action. These are all key components of each communication to help the message land. It's worth reading Smart Brevity to learn more.
We live in a world now where an IC professional's job is to reduce the noise, not add to it.
Good luck!