A client calls Monday morning asking about the thing you thought was handled last week. You check with the team. Nobody is sure whose job it was. Somewhere between the meeting, the Slack thread, and the email chain, it got dropped.
This happens in every small business. The owners and teams I talk to usually describe it as a people problem. "We need to communicate better." "I need to follow up more." That framing is wrong, and it is why the same issue keeps coming back.
It is a system problem. Specifically, a channel problem, a norms problem, and a documentation problem.
The three things that make communication drop
Too many channels. Email. Slack. Text. Whatsapp. In person. A project tool. A shared doc. When information can live in seven places, it effectively lives in none of them. Somebody mentions it in person, assumes it is handled, and nobody has it written anywhere.
No shared norms. Your team has not agreed on which channel is for what. Urgent requests hide in email. Non-urgent updates interrupt focus time on Slack. Decisions get made in DMs that the rest of the team never sees.
No single source of truth. Deadlines live in meetings. Status lives in Slack. Client requests live in email. The real state of any given thing is distributed across tools that do not talk to each other. Finding the answer takes five minutes of digging, and often the digging finds conflicting versions.
These three, layered together, are why things slip.
What actually fixes it
Not more meetings. Not a better app. The fix is a shorter list of channels, clearer norms for when to use which, and a single place the truth lives.
Short list of channels
Pick the smallest set that covers your real needs. For most small businesses, something like this.
Slack (or Teams, or whatever) for quick questions and short updates. Use channels, not DMs, by default, so other people can see and learn.
Email for longer updates, external clients, anything that needs a traceable record.
A single project or task tool for the state of work. Notion, Asana, Trello, ClickUp, or something equivalent. One tool, not three.
A shared doc repository for documents, references, and SOPs. Google Drive, Notion, Dropbox.
Phone for urgent. If it truly cannot wait, it is a call.
That is it. No more. Anything else you have opened in the last year should be closed or merged.
Clear norms
Write down the team's norms for when to use which channel. Keep it short. An example.
Urgent and needs a same-day response: phone or specific channel in Slack with @mention.
Needs a response by end of week: Slack DM or a task in the tool with a deadline.
FYI and reference: post in the relevant Slack channel so the team sees, then archive.
External communication with clients: email.
Anything important that needs to persist: a doc or a task with a link back in Slack.
You are not writing a novel. Maybe ten lines total. Everyone reads it, everyone agrees, the norms become the default.
Single source of truth
Whatever you use as your project or task tool, commit to it. Every active project has a page. Every task has an owner and a due date. Status is updated there, not in a meeting, not in a Slack thread.
Meetings reference the tool. Not the other way around. Slack threads end with "I put the decision in the task."
This takes about a month of discipline to become a habit. After that, the team naturally goes to the tool to check status instead of asking a person, and the "I did not know this was my responsibility" moments drop sharply.
Confirming, not assuming
A specific habit worth building. For any important information, end the communication with a confirmation. "Can you confirm you saw this and will handle by Friday?" It sounds formal. It costs ten seconds. It removes the "I assumed you saw it" category of problem almost entirely.
Same with decisions. When a decision gets made in a meeting or a thread, write it down somewhere persistent and tag the people who need to act. Decisions that stay in conversation disappear within a week. Decisions that get written down stick.
The Andon cord habit
Toyota has the concept of the Andon cord, a line any worker can pull when something looks wrong, which stops the line and surfaces the problem immediately. Small teams benefit from a version of this.
Make it easy for anyone on the team to say "I am not clear on this" or "I think we are about to miss something" without penalty. If people feel safe flagging confusion early, the small issues get handled before they become dropped balls. Blame culture kills this habit. You build safety by thanking the person who flags the issue, even if it turns out to be a non-issue.
The Pareto of channels and decisions
A short audit worth doing. For a week, track where communication actually happens in your business. Which channel, which kind of message, which handoff. You will almost always find that a small handful of channels are carrying most of the load, and one or two are generating most of the confusion. The fix is usually to kill the channels nobody uses well and strengthen the ones that actually work.
What gets easier
When channels are clear, norms are shared, and there is a single source of truth, a few things start to happen.
People stop asking you where things are. They know where to look.
Decisions stop getting relitigated. They are written down.
Handoffs stop failing. The task has an owner and a due date, and everyone can see it.
You stop being the hub. Information flows between people without you in the middle, which frees you for actual work.
New hires get productive faster. There is a system to onboard into, not a web of tribal knowledge.
The Monday action
Pick one of these, just one.
Write down the four or five channels you actually use and post the rule for when to use each. Tell the team. Follow it yourself.
Pick a single tool for task and project state. Move the in-flight work into it. Everyone updates status there, not in Slack.
Start adding confirmation to any important message. Ten seconds, habit for a week, big change in what gets dropped.
Any of these alone will noticeably reduce the feeling that things are slipping through.
If this is the constant friction
When I run a Flow Check, communication breakdown is one of the top three things that shows up. The fix is almost never that the team needs to communicate better. It is almost always that the channel design, the norms, or the source of truth is broken. Two weeks of observation usually surfaces the specific fixable pieces.
For related reading, communication norms nobody wrote down, async communication for small business, and feedback loops do not exist.