Communication Over Being Right: How to Deliver IT Projects Without Conflict 

Because a project is not an Oxford debate. The goal isn't to prove who’s right, but for everyone to move forward together. When you start fighting to „win” the conversation, you lose something far more important… the trust of your team and the client. Without trust, there’s no chance of making progress. Sometimes it's worth pausing and asking yourself: does what I'm saying contribute to the project's execution? Every conversation with a client should carry a meaningful, substantive message.

Communication begins to break down – people shut down, get defensive, stop cooperating. An atmosphere of mutual suspicion emerges, and team members start focusing on blaming each other. As a result, issues no longer get raised openly, because no one wants to be the next scapegoat. Mistakes surface later – and fixing them costs more. Blame doesn’t speed up the project; it actually stalls it. We’re just wasting time. 

Moreover, why turn the client into an enemy? It’s better to think in terms of long-term collaboration. Let’s also remember that the project has a single goal – one that both we as the vendor and the client share. 

First of all: speak impersonally. Not „X didn’t send the documentation”, but „the documentation is missing, so the work is on hold”. It’s a subtle difference, but a very effective one. This way, we focus on action rather than judgment. Communication in IT projects should be constructive, not accusatory. This way everyone feels safer. Stick to facts, figures, and dates – in other words, substance. 

When someone speaks calmly, relies on data, and doesn’t get carried away by emotions, they earn respect. In IT projects, where emotions can run high, that kind of communication style brings stability. 

In conversations, we should focus on the problems – and above all, on objective solutions. Let’s work together to identify ways to overcome project obstacles and improve processes. A proactive attitude will certainly be appreciated by the client. 

It’s crucial. In complex, dynamic, and stressful projects – trust is the most valuable currency. When people feel they can speak freely, without being publicly criticized or exposed to blame, they work more effectively. Trust is built through daily small gestures and consistent behavior. 

Good communication can truly work wonders. A discussion that turns into a blame game leads nowhere. Watching such a „conversation”, you’d think that no one is actually responsible and everyone is doing their job correctly. 

They need a purpose, a structure and most importantly – meaning. Meetings shouldn’t be accusation sessions, but opportunities to find solutions together. The facilitator’s role is to keep emotions in check, avoid being drawn into conflicts, and steer the conversation so everyone stays focused on the future, not the past. After the meeting, everyone should know what to do and why. That’s why it’s worth preparing short, substantive summaries – for example, writing down agreed actions in an email or shared document.

Most of all, avoid the „us vs. them” mindset. Instead of accusing „why didn’t you do this?”, it’s better to ask „what can we do to make this work?” This is a pragmatic approach. Shared language builds a sense of shared purpose. People aren’t willing to help if they feel attacked. But they are willing to act if they feel like we’re on the same team.

Calmly, but firmly. In such moments, go back to the agreements, documents, and facts. Don’t attack, don’t accuse – but also don’t let yourself be cornered. The best defense is clear, calm communication and being well-prepared. If we’ve built trust beforehand, there’s a chance the client will listen. 

We certainly can’t afford to react to provocation — stay indifferent to it. Over time, the client will see that it doesn’t affect us and might adjust their attitude. 

Firstly, talk to them. Simply ask what’s frustrating them, what can be improved, what’s getting in the way of their work. Secondly, give them a sense of purpose. People handle pressure better when they know why they’re doing something and that their effort matters. And thirdly, shield them from unnecessary escalation – show them they have your support. That really helps.

Don’t fight to be right. Fight for the project. Being right might be satisfying for a moment, but a well-delivered project in a good atmosphere stays with you for a long time – in relationships, in reputation, in future contracts. In the long run, effectiveness is what defines a good project manager.