You know the picture. A meeting, two directors, each of them right – because each measures reality by their own indicator. Production defends volume, quality defends zero defects, sales defends the deadline. Nobody is lying, nobody is lazy, and yet the conversation goes nowhere until the board steps in as judge and settles the dispute by force.
The first reflex in this situation is: “We need to get along, everyone towards one common goal.” And that very reflex is partly wrong. Because some goals are meant to conflict – and trying to unify them does more harm than the conflict.
This article is about what to do when departmental goals are mutually exclusive – not to erase the contradiction, but to make it start producing good decisions instead of war.
Conflicting goals aren’t a mistake. Having no mechanism to resolve them is
Let’s start with a truth that’s easy to overlook: some of the tension between departments is designed on purpose and works in your favour.
Quality is meant to slow production down – that’s why it exists. Controlling is meant to slow sales down. Maintenance is meant to push for inspections that don’t pay off for production in the short term. These are built-in safety fuses. If production and quality wanted exactly the same thing, one of them would be redundant – and the company would lose the balance that protects it from foolish decisions.
So the problem isn’t that the goals are different. The problem is that the organisation has no way of resolving these differences. Tension without an arbitration mechanism turns into war – won not by the better decision, but by the louder director or the faster escalation.
Your task isn’t to remove the tension. It’s to build an architecture that turns it into a conscious choice.
First, distinguish healthy conflict from toxic conflict
Before you start fixing anything, make a diagnosis – because not every conflict of goals needs intervention.
Healthy conflict reveals a trade-off and forces a good decision. Quality stops a questionable batch, production pushes for the deadline, and at the interface a conscious decision is made: do we take the risk or not? The system works – the difference in priorities has produced a considered choice.
Toxic conflict doesn’t produce decisions, only losses. Departments optimise their own indicators at the expense of the whole company’s result, hide information, play for time, and the dispute ends in rework, escalation and looking for someone to blame. Everyone wins their indicator; the company loses.
The test is simple: does this conflict lead to a better decision for the whole – or to a local victory at the expense of the whole? Leave the first alone. The second needs to be redesigned.
Five moves when goals conflict
Here’s the practical part – what an organisation (and its leaders) actually does so that conflicting goals start working for the company rather than against it.
1. Name the overriding goal that breaks the tie. When two departments pull in opposite directions, there has to be a higher goal that cuts through the dispute. “Delivered without defects and on time” stands above “maximum volume” and above “zero defects” – and when those two clash, it is the arbiter. If no such overriding goal is explicitly named, every dispute is settled again from scratch, by force. Name it – and make it the arbiter.
2. Build a shared metric at the interface. Where the interface generates the most friction, give both departments one indicator they are jointly responsible for. If production and quality share “delivered without defects”, they stop playing against each other – because they win or lose together. A shared metric does what no appeal for cooperation can: it changes the maths of the bonus.
3. Make the trade-off explicit, not hidden. In a toxic conflict, the trade-off is decided by whoever shouts louder or escalates faster. In a healthy one, it is decided consciously and openly: “On this order we’re choosing the deadline over margin, because it’s a strategic client.” Create a forum and a rule in which compromises are made openly, with a rationale – not quietly in the corridor, in favour of the stronger side. An explicit trade-off is a decision. A hidden one is a conflict.
4. Give a mandate for horizontal decisions and clear escalation rules. Agree before a dispute breaks out: what departments should resolve between themselves, and what should go higher, and when. Without this, every conflict lands on the board’s desk; the board wastes time playing judge, and departments learn that escalation is the normal way of working. A mandate to decide at the same level plus a clear escalation threshold shortens the cycle and takes load off the top.
5. Eliminate local optimisation in bonuses. This is the deepest and hardest lever – and the only one that only management can pull. If people are rewarded for an indicator that harms the whole, no communication will fix it. Do an audit: what are you really paying for? Does the incentive system reward optimising a silo at the company’s expense? As long as the bonus contradicts the overriding goal, people will rationally choose the bonus.
The leader’s role: arbiter and translator, not judge of guilt
When goals are mutually exclusive, the worst thing a leader can do is step into the role of a judge looking for the guilty party. Because there is no guilty party – both directors are right within the limits of their indicators. Looking for blame is a game the company always loses.
The leader’s role is different – and twofold. First, arbiter: they consciously resolve the trade-off in relation to the overriding goal and take responsibility for the choice, instead of letting the strongest decide. Second, translator: they help departments understand that the other side isn’t acting in bad faith, but is optimising a different, equally important goal – and often simply thinks and communicates differently. A shared language of styles (e.g. DISC) isn’t a soft add-on here – it concretely reduces the number of clashes that come from pure misunderstanding of intentions.
What not to do
Three traps most organisations fall into:
Don’t pretend there is no conflict – tension swept under the carpet doesn’t disappear, it moves to the interfaces and comes back as rework. Don’t settle it by force every time – escalation as the default mode teaches departments helplessness and eats up the board’s time. And don’t send people to a communication workshop when the source is conflicting bonuses – that treats the symptom, a classic activity without results, for which the board later cuts the whole development budget.
The goal isn’t a company without contradictions
You aren’t aiming for an organisation in which no goals ever clash – it would have no safety fuses and would make ever more foolish decisions. You’re aiming for an organisation in which conflicting goals are resolved by architecture, not by war: there is an overriding goal, a shared metric at the interface, an explicit trade-off and a clear rule about who decides and where.
Then the tension between departments stops being a cost and becomes what it was meant to be from the start – a mechanism that makes sure the company makes wise decisions.