Ever felt like one department in your company has no idea what another is doing? It’s a common problem. Marketing launches a campaign that Sales wasn’t ready for. Engineering builds a feature that Customer Support knows will cause confusion. It’s as if each department is its own small country, complete with a unique language, culture, and set of priorities.

This disconnect isn't just frustrating; it slows down work, creates unnecessary conflict, and can ultimately impact customers. The first step to fixing this is to understand why it happens. The barriers are often invisible, built from habit and routine.

One of the biggest reasons departments struggle to communicate is that they're working towards different goals. On paper, everyone is supposed to be helping the company succeed. But in practice, each team has its own specific targets, or Key Performance Indicators (KPIs).

For example, the marketing team might be measured on how many new leads they generate. So, they run a huge campaign offering a big discount, and they bring in thousands of leads. Success! But the sales team is measured on closing deals and revenue. They discover most of these leads are just looking for a freebie and have no intention of buying. The result? Marketing hits its goal, Sales misses its goal, and both teams end up resenting each other.

Beyond goals, each department develops its own culture. This includes its own jargon, work pace, and values. The engineering team might value precision and careful planning, leading them to take more time on projects. The sales team, driven by monthly targets, likely values speed and agility. When these two cultures collide without understanding, it can lead to friction. Engineering might see Sales as “pushy,” while Sales might view Engineering as “slow.”

Sometimes, the problem isn't the people or their goals but the systems they use to communicate. Relying on the wrong tools can easily lead to delays, lost information, and misunderstandings.

Think about it. An important decision is made in a fast-moving chat channel and is quickly buried under hundreds of new messages. An email thread with ten people on it becomes impossible to follow. Or, there's no clear process for how the design team should hand off its work to the development team, leading to missed details and rework. These are all examples of inadequate communication channels.

When channels are broken or poorly defined, people will create their own workarounds. This leads to inconsistency, making it hard for anyone to have a clear picture of a project's status. Important information doesn't get to the right people at the right time, and delays become inevitable.

Ready to test your ability to spot these common barriers? Let's see what you've learned.

Recognising these obstacles is the essential first step. Once you can see the barriers, you can start to think about how to take them down.