Negotiating responsibility – how to avoid blame games in projects
When a project is going well, everyone is happy to share in the success. When delays, mistakes, or ambiguities arise, the search for someone to blame begins. "IT was late." "Marketing didn't deliver the materials." "Sales made the wrong promise to the customer." This is how the blame game begins, destroying cooperation faster than the problem itself.
That is why one of the key areas of a leader's work is negotiating responsibility—discussions that determine who is responsible for what and how we respond when something goes wrong.
Why responsibility is a difficult area to negotiate
Responsibility involves risk. No one wants to be the first in the firing line when something goes wrong.
Scopes often overlap. The boundaries between departments are blurred, and the project does not "ask" who is formally responsible.
Responsibility is emotional. It's not just about tasks, but also prestige, position, and a sense of justice.
The most common mistakes leaders make
Lack of clear agreements at the outset. "We'll take care of it together" sounds good until something goes wrong.
Punishment instead of resolution. Every mistake ends with public finger-pointing, which exacerbates defensiveness.
Too much flexibility. The leader takes everything upon themselves, and the team loses its sense of shared responsibility.
How to negotiate responsibility more effectively
Define responsibilities clearly. Who is responsible for the result, who supports, and who only consults – it's simple, but rarely practiced.
Create rules for responding to mistakes. "We are not looking for someone to blame, we are looking for solutions" must be a real practice, not an empty slogan.
Balance power and responsibility. If someone has decision-making power, they must also have the resources to take responsibility.
Case study: a project paralyzed by buck-passing
In one of the client's projects, every delay ended in an argument about who was to blame. Instead of working, the team produced defensive emails and reports "just in case."
It was only the introduction of a simple model – the RACI (Responsible, Accountable, Consulted, Informed) matrix – that allowed responsibilities to be sorted out. Suddenly, it became clear who decides, who advises, and who only informs. The blame game ended, and the project began to get back on track.
Summary
Negotiations about responsibility are inevitable in any project. A leader who can clearly define roles and respond to mistakes without looking for someone to blame builds a team that is resilient to crises and capable of working together even under pressure.
👉 If you want your team to learn to negotiate responsibility instead of shifting blame, see:
www.szkoleniaznegocjacji.com/szkolenie-negocjacje-w-zespolach-projektowych
This training shows you how to turn conversations about mistakes and responsibility into a process that strengthens the team and speeds up projects.
If you are looking for executive coaching in Poland, check our offer: