Internal communication is one of the most overlooked parts of operations. When a company is growing quickly, it is easy to give processes, tools and reporting all the attention. Listening to people and explaining decisions becomes something we will “get better at later.”
Later rarely arrives. And the cost of skipping it is not abstract. Communication is how people understand what matters, what they are accountable for, and how their work contributes to what the company is trying to do. Without it, even a well-designed process is a set of instructions nobody quite believes in.
It starts with listening
For me it starts with listening, and listening is an operational activity, not a personality trait. What does the team care about? What frustrates them? What makes them proud of their work? Their stories tell you things a dashboard never will. A dashboard shows you that a handoff is slow. A conversation tells you the handoff is slow because two people have quietly stopped trusting each other’s numbers.
That is information you can act on. The dashboard alone would have sent you looking for a tooling fix.
Honesty is a system property
Honesty matters just as much. I want the people I work with to trust that I will tell them the truth, including when the answer is “I don’t know” or “I got that wrong.” That trust is not built in an all-hands. It is built in everyday conversations and in whether our actions match our words when nobody is checking.
The operational version of this: if you say a process is mandatory and then wave it through for the loudest team, you have communicated that the process is optional. Everyone heard it. No memo required.
Connect the work to the person
Listening also lets you connect people’s own motivations to the work ahead: the chance to grow, to take ownership, to solve a meaningful problem, or to see the impact of what they did. You cannot make that connection for someone if you have never asked what they actually want.
Accountability is only fair after clarity
Clear communication also makes accountability fairer. Before holding someone accountable, we should be able to say three things honestly: we made the expectations clear, we explained why they mattered, and we gave them room to raise concerns. If any of those is missing, the problem is upstream of the person.
This is the part operations teams skip most often. We write the process, publish the doc, and move on. Then we are surprised when adoption is patchy, and we treat the patchiness as a discipline problem instead of a communication one.
A daily responsibility
I see communication as a core leadership skill and a daily operational responsibility. Not a soft skill, not a comms team’s job, not a quarterly town hall. If people do not understand the direction, do not trust what they are hearing, or do not feel able to speak honestly, how much can even the best process achieve?