A €500,000 project was about to fail. Nothing was wrong with the people. Everything was wrong with the interface.
Manufacturing operations. Belgium and UK interface. Client identity withheld at their request.
The acquisition changed the ownership. Nobody changed the operating rules.
A Belgian operational team of around 15 people had moved under new ownership after acquisition by a UK corporate group.
Different expectations. Different assumptions. No shared operating rules. The friction accumulated quietly for over a year. On the surface, it looked like a people problem. It was an interface problem.
Work refusal. Deliverables blocked. €500,000 at risk.
The surface read was a conflict between teams. The diagnostic revealed something more structural.
What was visible
- Work refusal from the Belgian team
- Deliverables blocked across the interface
- A client project worth over €500,000 at risk of collapse
- Leadership on both sides firefighting constantly
- Escalation arriving after damage was already done
What was really happening
The problem was not motivation. It was not competence. It was not resistance. Nothing had changed about the work itself. Only the way each side interpreted it. The same decisions, handoffs, and escalations meant different things on each side of the interface.
How the loss moved through the business
The project did not fail at once. The interface slowly changed the meaning of the work until delivery stopped.
Acquisition
Ownership changed. The way work should move did not.
Different assumptions
Decisions, handoffs, and escalation meant different things on each side.
Delivery blocked
Work refusal followed. The project moved into risk.
Nuancea corrected the operating rules at the interface. Delivery resumed. The client stayed. A second project followed.
The missing operating rules were installed where the work crossed teams
No workshop. No slide deck. A 30-day correction of how the two sides made decisions, handed work over, and escalated risk.
Found where work changed meaning
Within 10 days, we identified where ownership disappeared, where handoffs broke, and where escalation arrived too late to protect delivery.
Installed the missing operating rules
The correction became a simple manager handbook covering who decides, what finished means, and when escalation is required.
Aligned both sides
Managers on both sides were coached to use the same rules without creating new friction, especially in moments of disagreement, feedback, and escalation.
The difference was where the fix lived. It was installed inside the real working interface, not recommended in a deck for someone else to implement later.
The project did not collapse. The relationship held.
Within 30 days, the interface was working again.
Execution
- Work refusal stopped
- Deliverables unblocked
- Productivity recovered across the interface
- Escalation arriving earlier, before damage compounded
- Leadership no longer firefighting the same issues
Business
- Client retained
- €500,000+ project delivered
- A second project generated in the months that followed
- Belgian operation recovered its credibility within the group
In the client's words
Philippe pinpointed the underlying issues within 10 days and gave us a clear way of working: who decides what, how work is handed over, and when to escalate. Within weeks, the friction dropped, productivity recovered, and a project we had been close to losing was delivered.
Head of Operations, Belgian operations
Named reference available to serious prospects, with the client's agreement.
The project was not saved by another workshop.
It was not saved by restructuring. It was not saved by asking people to communicate better. It was saved by correcting the operating rules where the work crossed from one team to another. This is not an exceptional case. It is simply the first one we are allowed to talk about.
A €500,000 project was about to fail. Nothing was wrong with the people. Everything was wrong with the interface.
Manufacturing operations. Belgium and UK interface. Client identity withheld at their request.
The acquisition changed the ownership. Nobody changed the operating rules.
A Belgian operational team of around 15 people had moved under new ownership after acquisition by a UK corporate group.
Different expectations. Different assumptions. No shared operating rules. The friction accumulated quietly for over a year. On the surface, it looked like a people problem. It was an interface problem.
Work refusal. Deliverables blocked. €500,000 at risk.
The surface read was a conflict between teams. The diagnostic revealed something more structural.
What was visible
- Work refusal from the Belgian team
- Deliverables blocked across the interface
- A client project worth over €500,000 at risk of collapse
- Leadership on both sides firefighting constantly
- Escalation arriving after damage was already done
What was really happening
The problem was not motivation. It was not competence. It was not resistance. Nothing had changed about the work itself. Only the way each side interpreted it. The same decisions, handoffs, and escalations meant different things on each side of the interface.
How the loss moved through the business
The project did not fail at once. The interface slowly changed the meaning of the work until delivery stopped.
Acquisition
Ownership changed. The way work should move did not.
Different assumptions
Decisions, handoffs, and escalation meant different things on each side.
Delivery blocked
Work refusal followed. The project moved into risk.
Nuancea corrected the operating rules at the interface. Delivery resumed. The client stayed. A second project followed.
The missing operating rules were installed where the work crossed teams
No workshop. No slide deck. A 30-day correction of how the two sides made decisions, handed work over, and escalated risk.
Found where work changed meaning
Within 10 days, we identified where ownership disappeared, where handoffs broke, and where escalation arrived too late to protect delivery.
Installed the missing operating rules
The correction became a simple manager handbook covering who decides, what finished means, and when escalation is required.
Aligned both sides
Managers on both sides were coached to use the same rules without creating new friction, especially in moments of disagreement, feedback, and escalation.
The difference was where the fix lived. It was installed inside the real working interface, not recommended in a deck for someone else to implement later.
The project did not collapse. The relationship held.
Within 30 days, the interface was working again.
Execution
- Work refusal stopped
- Deliverables unblocked
- Productivity recovered across the interface
- Escalation arriving earlier, before damage compounded
- Leadership no longer firefighting the same issues
Business
- Client retained
- €500,000+ project delivered
- A second project generated in the months that followed
- Belgian operation recovered its credibility within the group
In the client's words
Philippe pinpointed the underlying issues within 10 days and gave us a clear way of working: who decides what, how work is handed over, and when to escalate. Within weeks, the friction dropped, productivity recovered, and a project we had been close to losing was delivered.
Head of Operations, Belgian operations
Named reference available to serious prospects, with the client's agreement.
The project was not saved by another workshop.
It was not saved by restructuring. It was not saved by asking people to communicate better. It was saved by correcting the operating rules where the work crossed from one team to another. This is not an exceptional case. It is simply the first one we are allowed to talk about.