It sits in your meetings.
I fired a team member. Not because of poor performance. Because his behavior was poisoning the team. He had reduced a female colleague to tears. When I found out, I immediately involved HR and opened the conversation. What we uncovered: behind the aggressive behavior was a deep frustration about salary and recognition. The person was doing the absolute minimum required and demanding significantly more money for it.
What I learned: unresolved tension in a team is not a soft-skill challenge. It is a system failure. And if you do not intervene early, it spreads. In this case: within days of that person leaving the company, the team was itself again.
This page is not about conflict theory. It is about what I have learned in 25+ years in the automotive matrix: how conflicts emerge, why they stay invisible, and how to solve them structurally — before they break the SOP.

25+ years of Tier-1 automotive experience
€150M annual revenue responsibility as Head of Electronics, Brose Prievidza
40+ engineers built from zero in Slovakia
12 executives coached in Pune (2023–2024)
6 Countries operational experience
What conflicts really cost: The numbers that never appear in a board deck.
Friction is expensive. These numbers decide whether your next SOP date holds – or not.
The neuropsychology of conflict: Why talking alone fails.
Conflicts do not fail because of bad intentions. They fail because of biology. In high-pressure environments, conventional conflict management systematically fails because the brain shifts from the prefrontal cortex to Amygdala Mode: from thinking to fight-flight-freeze.
That is why ‘could you please sort this out’ almost never works. The people involved are not operating from the rational part of their brain.
Where conflicts actually come from: Three patterns from the DE-SK-IN matrix.
Across 25 years in the global automotive matrix, I have observed three conflict patterns that recur consistently. None of them are personality problems. All three are structural.
1. The hidden assignment: When your team is caught between two chairs.
In Pune, I experienced my team not delivering for weeks – even though they confirmed to me that they were working on the tasks. When I flew there for four weeks, I had the answer within two days: the plant manager had been giving my team hidden parallel tasks to support the plant.
My team was caught between two chairs. I was the German manager with functional responsibility. He was the plant manager with local authority. Both had legitimate requirements. Nobody had clarified the conflict.
This is not an Indian problem. I have seen the exact same pattern in Slovakia, in Germany, and in Mexico. Whenever accountabilities in a matrix organization are not explicitly clarified, these conflicts emerge. The solution was a direct conversation with the plant manager, a written RACI agreement, and a clear signal to my team: I carry the responsibility. You have one manager. Me.
2. The toxic team member: When loyalty becomes weakness.
I had a team member who was treating my assistant aggressively and reduced her to tears. And, I did not find out through a formal complaint – I found out through observation.
I involved HR immediately. Together we opened the conversation. What we uncovered: behind the behavior was a deep frustration about salary expectations that had not been met. The person was doing the absolute minimum and demanding significantly more. When we dug deeper: the hourly contract was not even being fulfilled.
My decision was clear: this person had to leave. What I learned was twofold. First: I should have acted earlier. The toxic behavior had already spread to two younger colleagues before I intervened. Second: the team recovered within days. The energy that had been going into self-protection could flow back into work.
Do not act too late out of misplaced loyalty. One toxic team member costs the entire team its energy.
3. The protection conflict: When hierarchy works against your own team.
A manager from outside my team demanded that I fire one of my people. The reason: that person’s behavior had not met their expectations.
I investigated. What I found: my team member had broken no rule. They had simply bruised that manager’s ego. I rejected the demand clearly: ‘This person has done nothing wrong. I will not fulfill this request.’ That took courage — including in a follow-up conversation with my own direct manager, where I had to defend this position again. In the end, I succeeded.
What I took from this: if you do not protect your team, you cannot expect trust. And without trust, no team member will honestly escalate when something goes wrong. That is the direct connection between your willingness to act on conflict and the Green-Melon risk in your projects.
‘The problem is not that your teams are not talking. The problem is they are speaking the wrong language: positions instead of interests, blame instead of system analysis, guilt instead of solutions.’ – Andy Balbus, Industrial Conflict Architecture
The BYG Conflict Architecture: An operating system for alignment.
Conflict resolution is not therapy. It is system architecture. We build an operating system for alignment that scales even in complex matrix structures. Four principles, grounded in Harvard negotiation research and 25 years of automotive practice:
SDV context: Why Conflict Architecture matters more in 2026 than ever before.
The transformation to software-defined vehicle (SDV) architecture fundamentally changes conflict dynamics in R&D teams. Requirements that used to come quarterly now come every two weeks. OEM platform decisions change mid-project. Feature-freeze dates shift.
In this environment, three new conflict sources emerge that did not exist in classical hardware development:
- Interface conflicts between classical electronics development and software teams: different cadences, different definitions of done, different escalation cultures.
- Requirements conflicts between OEM platform decisions and running development projects: when the target architecture changes but team goals are not adjusted, frustration and hidden resistance emerge.
- Accountability conflicts in the global matrix: who is responsible when the software specification from German HQ collides with the hardware reality of the Slovak development center?
The Harvard principle of interests instead of positions is particularly powerful in SDV projects: both sides want to hold the SOP. That is the shared interest. Everything else – who is right, whose specification applies – are positions. Bring the conversation to the interest level, and many deadlocks dissolve within one session.
What is your Alignment Tax? Calculate it in 3 minutes.
5 questions. Your dominant conflict type. The real costs – per month.
Do not rely on theory - trust the results.
- Academic Foundation: Graduate Industrial Engineer (Dipl.-Wirt.-Ing. FH), HFH Hamburg.
- Coaching Excellence: ICF Professional Certified Coach (PCC), Coacharya Advanced Program (160 hours, Level 2 + 3). Over 1,000 documented coaching hours.
- Slovakia Reference: Built the complete electronics department at Brose Prievidza from 0 to 40+ engineers. Team culture, RACI systems, and escalation architecture built from scratch. Department still runs today under his successor.
- India Reference: Coached 12 executives at Brose India Pune (2023-2024). Established the Brose Training Academy Pune. Direct application of Conflict Architecture in the DE-IN matrix.
- Task Force Reference: Led a 50-person Task Force in a high-value automotive crisis. Conflicts between OEM, suppliers, and internal teams resolved in real time.
- Google Ratings: 5.0 stars. LinkedIn recommendations from Vasanth Suratkal Kamath (President Brose India), Vinayak Gaddam (Deputy Manager Brose India), Ashish Pensalwar (IT Operations Lead).
'With his keen listening ability and thought-provoking guidance he is an excellent mentor and coach, especially well suited for people that have dealings across multiple geographies.' -- Vasanth Suratkal Kamath, President Brose India
'Andy has a unique ability to simplify complex leadership situations and offer actionable guidance tailored to individual needs.' -- Vinayak Gaddam, Deputy Manager Brose India
Scale Your Operational Impact
FAQ - Conflict Architecture & EBIT Security

What is your Alignment Tax? Stop the silent investment in friction.
If your global matrix system is stagnating because of friction, you do not have a growth problem -- you have a Conflict Architecture problem. Let us analyze together what it is costing you and reclaim a structured system for your team.
Systemic leadership does not end after one call.
Follow for unfiltered insights and straight-talk strategies:

