Technology has transformed the way organisations communicate. Messages that once took days to travel between departments now arrive instantly, across email, chat, dashboards, and shared drives. But technology alone does not guarantee good communication. It only changes the speed at which communication, accurate or not, moves through an organisation. The real competitive advantage was never the platform. It is ensuring that the information running through that platform remains accurate, trusted, and accessible to the people who need it.

Poor communication is rarely dramatic. It doesn't usually look like a crisis. It looks like a decision made on a spreadsheet nobody updated, a policy applied from a document that was superseded months ago, or a team executing a plan that changed in a meeting they weren't in. Individually, each of these is small. Across a full year, in a mid-sized organisation, they add up to real cost: rework, missed deadlines, duplicated effort, and slowly eroding trust between teams who no longer believe the information they're handed. Money gets spent twice. Time gets lost re-explaining what should have already been clear. And trust, once it erodes, is far harder to rebuild than any process document.

Knowledge Is More Valuable Than Data

It helps to separate three things that get used interchangeably in most workplaces: data, information, and knowledge. Data is raw and unprocessed, a number, a timestamp, a field in a database. Information is data that has been organised into something meaningful, a report showing that registrations dropped 12% this quarter. Knowledge is what a person does with that information: understanding why registrations dropped, what it means for the next campaign, and what to do about it. An organisation can be drowning in data and still be starving for knowledge, because the step that turns numbers into judgement only happens inside people and well-designed systems.

Knowledge itself splits into two kinds, and most organisations only manage one of them well. Explicit knowledge is what can be written down: SOPs, policies, manuals, checklists, KPI definitions. It's portable and easy to store in a system. Tacit knowledge is different. It's the judgement a finance officer develops for spotting a suspicious invoice, the instinct an event coordinator has for which vendor will actually deliver on time, the unwritten sense of which stakeholder needs to be looped in early or a project will stall. Tacit knowledge rarely makes it into a document, because the person who has it often doesn't realise it's knowledge at all. It just feels like common sense, right up until they leave and everyone discovers it wasn't common at all.

This is why the departure of one experienced employee can quietly damage an organisation more than an entire quarter of turnover among newer staff. The newer staff leave with what's written down. The experienced employee leaves with what was never written down in the first place: the shortcuts, the exceptions, the reasons certain rules exist. Good knowledge management isn't about digitising everything. It's about deliberately converting as much tacit knowledge into explicit, shared knowledge as possible, before the person carrying it walks out the door.

Why Organisations Fail Because of Communication

When something goes wrong in an organisation, the instinct is often to blame the tools. In practice, most failures I've seen trace back to something far less technical.

• Misunderstandings — two people leave the same meeting with two different plans
• Outdated documents — a policy gets followed long after it was quietly revised
• Conflicting versions — three people are editing three different copies of "the" file
• Assumptions — a gap in the instructions gets filled with a guess instead of a question
• Rumours — informal chatter fills a vacuum that formal communication left empty

Each of these is a symptom of the same underlying problem, something worth calling information decay. Information decays the same way physical infrastructure does: not through one dramatic failure, but through small, unaddressed gaps that widen over time. A document goes unreviewed for a year. A process changes but the training material doesn't. A Slack thread contains the real decision, while the official file still shows the old one. None of this is catastrophic on its own. But decayed information behaves exactly like accurate information right up until someone acts on it, and only then does the gap become visible, usually at the worst possible moment.

The Telephone Game

Most people know the telephone game from childhood: one person whispers a sentence to the next, it passes down a line of people, and by the end the message is almost unrecognisable. It's treated as a party trick, but it's actually one of the most accurate models of how information moves through a real organisation.

In a project team, this plays out through status updates that pass from a contributor to a lead to a sponsor to a steering committee, each retelling summarising a little more and qualifying a little less. In corporate communication, it happens between a decision made in a leadership meeting and how that decision is understood three management layers down. In government organisations, it happens between a policy as written and a policy as implemented at the counter. In large enterprises spanning regions and time zones, it happens simply because no one retelling the message has access to the original.

What makes the telephone game genuinely useful as a model, rather than just an amusing analogy, is this: every person in the chain believes they are repeating a fact. They aren't. They're repeating their interpretation of a fact, shaped by what they understood, what they thought was important enough to keep, and what they assumed the listener already knew. None of them are lying. All of them are distorting. That's the part organisations underestimate, distortion doesn't require bad intent, it only requires enough steps between the source and the listener.

Formal vs Informal Communication

The instinct after seeing how easily messages degrade is to formalise everything, route every message through official channels, document every decision, eliminate the sidebar conversations. That instinct is wrong, and it misunderstands what informal communication is actually for.

Organisations need both, and the goal isn't to eliminate informal communication in favour of formal, it's to make sure they're not competing for the same job. Formal communication should own the record: what was decided, by whom, and when. Informal communication should own the relationship: how people actually get things done between the formal checkpoints. The mistake isn't having informal channels, it's leaving a transparency gap large enough for rumour to fill. Leaders who try to suppress informal communication don't get more accuracy, they just push the same conversations somewhere less visible. The better move is the opposite: communicate openly and early enough, formally, that there's nothing left for the rumour to explain.

The Single Source of Truth (SSOT)

If information decay and the telephone game describe the disease, the Single Source of Truth is the closest thing to a cure. The principle is simple to state and surprisingly hard to enforce: for any given piece of information, there should be exactly one authoritative version, and everyone who needs it should know exactly where to find it.

In practice, most organisations violate this constantly without noticing. A KPI exists in a dashboard, a slide deck, and a spreadsheet someone built for a meeting eighteen months ago, and all three show different numbers by the time anyone checks. A policy exists as a signed PDF, a summarised intranet page, and whatever a manager remembers being told about it in an onboarding session.

• Multiple spreadsheets tracking the same metric, updated on different schedules
• Duplicate files saved locally instead of in the shared system
• Outdated PDFs still circulating after the policy has changed
• Conflicting SOPs across departments describing the same process differently

None of this requires malice, it just requires the absence of a single trusted home for the information. That home doesn't need to be exotic. Platforms like SharePoint, Confluence, Notion, Microsoft Teams, and ERP systems all serve this purpose well, the specific tool matters far less than the discipline of actually treating it as the only place the truth lives, retiring every parallel copy, and training people to check the source rather than their inbox history.

Knowledge Management Is Digital Leadership

It's tempting to treat digital transformation as a procurement decision, buy the platform, migrate the files, declare the problem solved. That's not transformation, that's just moving the same disorganisation onto newer software. Real digital transformation means building systems that guarantee the right information reaches the right people, at the right time, in the correct version, every time, not just on the day the system launched.

That guarantee doesn't come from the software itself, it comes from the governance wrapped around it: version control so people aren't editing stale copies, clear document ownership so every piece of information has a named person accountable for keeping it current, and a regular review cycle so outdated material gets retired instead of quietly accumulating. A platform without governance just becomes a faster way to distribute inaccurate information. Leadership's job is the governance, not the login credentials.

My Reflection

Throughout my work in project management and digital transformation, including building SOPs, governance documents, FFOS submissions, and KPI reporting structures for the Saudi Muaythai Federation, I've learned that the biggest organisational problems are rarely technical. A registration system can be flawless and still produce chaos if the process feeding it isn't clearly owned. A KPI report can be beautifully formatted and still be wrong if three departments are defining the same metric differently. Most failures I've encountered didn't start with broken software. They started with inaccurate information, inconsistent communication, or knowledge that stayed trapped inside one person's head instead of being shared across the team responsible for the outcome.

“

Technology can store knowledge, but only people can create trust.

Ali Abdisalam Hussein

That distinction has shaped how I approach every system I've helped build since. A repository can hold every SOP an organisation owns and still fail, if no one trusts that what's inside it is current. Trust is earned through consistency: the document that was true last week is still true this week, the version people are shown is the version that's actually being followed, and when something changes, the people who rely on it hear about it before they discover it the hard way. Successful organisations don't just protect their knowledge, they protect the trust that makes people willing to rely on it. Build systems for one without the other, and neither survives.

Key Takeaways

• Knowledge is an organisation's greatest competitive advantage.
• Communication should be both fast and accurate.
• Informal communication builds culture but can spread misinformation.
• Formal communication creates accountability.
• Every organisation should maintain a Single Source of Truth.
• Good knowledge management is a leadership responsibility, not just an IT responsibility.

Final Thought

“

In an age where information travels faster than ever, the organisations that succeed won't be those with the most data. They'll be the ones that know how to protect its accuracy.

Further Reading

• Davenport, T.H. and Prusak, L. (1998) Working Knowledge: How Organizations Manage What They Know. Boston: Harvard Business School Press.
• Nonaka, I. and Takeuchi, H. (1995) The Knowledge-Creating Company: How Japanese Companies Create the Dynamics of Innovation. New York: Oxford University Press.
• Project Management Institute (2021) A Guide to the Project Management Body of Knowledge (PMBOK Guide). 7th edn. Newtown Square, PA: Project Management Institute.
• Drucker, P.F. (1999) Management Challenges for the 21st Century. New York: HarperBusiness.