The Hidden Cost of Poorly Managed Communication in Projects

Projects rarely fail due to a lack of methodology. They fail when people believe that "everyone understood", without ever truly aligning expectations, decisions, and responsibilities. Underestimated communication is the elegant silence that precedes operational chaos.

In corporate environments, especially under pressure, communication is often treated as something intuitive, when in practice it is a strategic asset. It's not about talking more, but about communicating better, at the right time, with the right clarity. When this doesn't happen, the project remains on paper… while execution follows parallel paths.

Every project is, first and foremost, a human system. And human systems break down when information doesn't flow, when decisions aren't made explicit, and when conflicts are swept under the rug.

At PMI, Communication is one of the most critical knowledge areas, and paradoxically one of the most neglected. A poorly defined communication plan generates rework, misaligned decisions, and unrealistic expectations. It's not enough to have the plan: you need to govern the communication.

Frameworks like RACI (Responsible, Accountable, Consulted, and Informed) help clarify who decides, who executes, who consults, and who only informs. Many project conflicts are not technical, but political, and RACI exposes this objectively, before it turns into a crisis.

In Agile environments, ceremonies like Daily, Review, and Retrospective are not symbolic rituals. They exist to create a cadence of alignment. When treated as an obligation, they lose their power to anticipate risks and adjust course.

Tools like MS Project, JIRA, and Power BI only deliver value when the data communicates a clear story. Schedules that nobody understands and dashboards that nobody uses are classic symptoms of failed technical communication.

Failed communication is not a lack of information, it's a lack of courage. Courage to say what needs to be said, to hear what you don't want to hear, and to deal with discomfort before it turns into conflict.

Organizational psychology shows that people under pressure tend to avoid difficult conversations. A mature manager does the opposite: they approach conflict with method and empathy. Leading is about translating complexity into emotional clarity.

As I've learned in practice: projects go into crisis when leaders hide behind tools and avoid human conversations. Effective communication begins with the manager's internal positioning, not the slide presentation.

The Queensland Health (Australia) payroll system case is one of the biggest global examples of failure in public projects. More than AUD 1.2 billion in costs and thousands of employees affected. The problem wasn't just technological.

Official reports show that there were multiple suppliers, constant scope changes, and ignored technical alerts. The information existed, but it didn't circulate clearly between executives, managers, and technical teams.

Critical decisions were made without real alignment, political deadlines suppressed operational alerts, and communication became fragmented. Each part of the project believed it was "doing its part", while the system as a whole collapsed.

The result was not a one-off mistake, but a classic domino effect of under-communication: ignored risks, diffuse responsibilities, and leadership disconnected from the reality of the project.

Before asking which methodology to use, ask: what is still not being said in this project?

Because projects don't fail due to lack of information, they fail due to lack of alignment.

Solutions

Transforming companies with tailored IT consulting services.

Consulting

Innovation

contact@dunamistech.net

+1-407-848-1078

© 2026. All rights reserved.