Project communication is part of project management. Why acceptance doesn't come from planning alone

Why projects fail due to communication issues despite sound planning

Large projects are often judged based on their hard factors: deadlines, budget, technology, approvals, committees, and milestones.

All of this is necessary.
However, all of this alone is not enough.

Because projects do not fail solely because of the initiative itself. They often fail because their rationale is not made clear. They fail because those affected cannot make sense of the direction. They fail because communication begins too late or is reduced to mere information.

This is precisely why it is worth taking a look at a recent example from Ulm. In connection with the ongoing B10 construction site, the local section of the Neu-Ulmer Zeitung on March 14, 2026, described how communication surrounding the project is organized. What becomes apparent there is an approach that does not merely react to criticism, but involves the public early on. Among other things, the article mentions guided tours, consultation hours, digital formats, social media, livestreams, and visible information resources on-site.

What is interesting here is not the number of channels.
What is interesting is the underlying understanding of leadership.

For there, communication is clearly not viewed as a friendly add-on, but as part of the project itself. This is precisely what distinguishes effective project communication from an after-the-fact explanation.

Many organizations make a strategic mistake at this point. They treat communication as a final step. First, decisions are made. Then planning takes place. Then implementation follows. And at some point, when questions or resistance arise, explanations are provided.

That sounds efficient.
It often isn't.

Because in the meantime, something has long since developed that is difficult to correct later: uncertainty, personal interpretations, office gossip, irritation, defensiveness. Subtle, but effective.

Especially in complex projects, acceptance does not arise automatically from technical accuracy. A project does not become viable simply because it is well-founded internally. Viability arises when people can understand what is happening, why it is happening, and what consequences will result.

This is not some watered-down romanticism of communication.
This is operational reality.

Those who underestimate this connection create friction. Sometimes delayed, sometimes invisible, but almost always palpable. Then projects become more protracted, coordination more cumbersome, and questions increase. Energy shifts from implementation to explanation, from leadership to reassurance, from action to correction.

Four Functions of Effective Project Communication

That is why project communication is not simply the distribution of information.

It fulfills at least four functions:

First. It provides orientation.
In situations of change, people need not only facts, they need context.

Second. It translates complexity.
Technical logic alone rarely convinces those who must live with or work through the consequences.

Third. It absorbs tension.
Especially in publicly visible, stressful, or long-running projects, the tone helps determine whether criticism escalates or remains manageable.

Fourth. It keeps the project socially acceptable.
A project can be formally correct yet still be unacceptable from a communication standpoint.

That is precisely the point. Communication is not merely a decoration for a project; it is part of its effectiveness.

What companies can learn from the B10 construction site in Ulm

This applies in the public sphere just as much as it does in companies. For construction sites as well as for reorganizations, transformation programs, regulatory initiatives, audit follow-ups, IT migrations, or safety-critical changes. Wherever interventions are felt, it is not enough to be right internally. You must also communicate the measure in a way that people can make sense of it.

Those who fail to do so lose time.
Often trust as well.
Sometimes both.

The B10 communication campaign in Ulm is therefore not just a local example of good public relations. It is a vivid case study for a broader leadership question: When is a project truly accepted, and when is it merely tolerated?

This distinction is essential.

A tolerated project remains fragile.
An accepted project is more likely to be supported.

In between lies communication as a leadership skill.

Those responsible for projects must therefore do more than just manage initiatives. They must also manage how these initiatives are perceived. This is precisely where it is decided. whether a project generates resistance or provides direction.

Uta-Alexandra Kral
Kral Kommunikation
Hauptstrasse 2
89250 Senden

Germany

office@kral-kommunikation.de

Uta-Alexandra Kral brings nearly three decades of corporate experience to the table, including many years in leadership and security roles. She knows from personal experience how paralyzing coordination loops can be and how much operational relief a clearly communicated decision can provide. She works on decision readiness, leadership voice, and communication in high-stakes situations, and supports organizations in structuring critical projects in such a way that decisions are not only made formally but also communicated transparently and embraced by all.

This release was published on openPR.