The execution engine for the global automotive matrix.
This page is for the people who carry the responsibility in the automotive matrix when an SOP date starts to slip. Perhaps you lead an R&D department whose team has been almost finished for weeks. Perhaps you are a plant manager receiving green reports while you already know the line will stop tomorrow. Or you have just taken over your first team as an experienced specialist and notice that technical excellence suddenly works against you. If you recognise yourself, you are in the right place.
You are not the problem. Your system is.
It is 10:30 PM. Your project status report is green. And yet you have that feeling, the one that tells you someone will call with bad news tomorrow morning. Your team confirmed everything is on track in the last alignment call. Your team lead in Pune said yes. Prievidza reports no deviations.
And you know: it is not true.
That is not a motivation problem, and not a personnel problem. It is a system failure, one that has a name and a solution. My name is Andy Balbus. I spent 25+ years inside exactly this system: as Director of Electronics in Slovakia, as Task Force Manager in a 50-person crisis, later as mentor to 12 leaders in India. This page is what I actually learned in that time, and the reason my GROW version no longer matches the textbook.
👉 Book Your Free 30-Minute Reality Check
Why Standard GROW systematically fails under automotive pressure.
Sir John Whitmore developed GROW in the 1980s for stable, psychologically safe development conversations. That was not a bad idea. The problem is: the automotive matrix in 2026 is the exact opposite of that.
Across 25+ years in German headquarters, in the electronics lab in Prievidza, and in R&D alignment meetings in Pune, I have observed four patterns that standard GROW does not solve, and that together put your SOP at risk.
Four patterns that put your SOP at risk
The Dopamine Paradox: Why your team feels productive, and ships nothing.
As an ICF-certified coach (PCC, Coacharya Advanced Program, 160 hours), I have identified a recurring pattern in hundreds of leadership conversations. It has a name: the Dopamine Paradox. And it is the reason standard GROW fails at the decisive moment.
It is not a motivation problem. It is neurochemistry, and those who understand it can structurally disable it.
The paradox across the four GROW phases
[R] Radical Reality
Confronting the real situation takes courage.
In Prievidza, my team leads polished their reports to look green, not out of bad intent, but because honest escalation felt dangerous. The Green-Melon Effect: green on the outside, red on the inside. Risk: The Ground Truth never surfaces, until it is too late.
A Deal is a Deal. No almost done, no trying, just a deadline: it holds, or it does not. Andy Balbus
The BYG GROW Method, calibrated for Industrial DNA.
25+ years of operational experience as Director of Electronics and Task Force Manager. Built for exactly the two places where excuses cost millions: the R&D laboratory and the production plant.
The four phases, recalibrated
[R] Radical Reality
We stop the Green-Melon Effect.
Through Active Listening and structured open questions, never Are you on track, always What is your concrete plan for the next two weeks, we force the Ground Truth to the surface. Whether in Pune, Prievidza, or Munich. Psychological safety is not a soft-skills exercise here, it is escalation infrastructure.
Active Listening │ Ground Truth │ Psychological Safety │ DE-SK-IN Matrix
[O] Operational Options
Industrially proven tools, not free brainstorming.
The RACI matrix structures accountability with precision: Responsible, Accountable, Consulted, Informed. The EKS bottleneck strategy identifies the fastest path through the constraint. Clear boxes, clear names, no whiteboard output that nobody remembers on Monday.
RACI │ EKS Bottleneck Strategy │ Ownership Design │ Gemba Walk │ Delegation
BYG Commitment-Check
Which leak is costing you the most right now?
6 questions. 3 minutes. A clear diagnosis.
What I actually learned, from a 50-person crisis.
I was a Task Force Manager. Pushed from zero into a high-value project that had gone off the rails. I was not the developer, not the supplier, not the line manager. I was the protocol owner for over 50 people from multiple countries.
The first thing I did was a mind map. All stakeholders, their accountabilities, their dependencies, including external partners for whom a budget and a procurement process had to exist before they could act. That was my RACI before I knew the word RACI.
The W-step in practice: I forgot.
The day came when a senior developer sat in the round and said: I forgot. I controlled my reaction, no escalation in front of the group. Calmly I asked: What does that mean for the overall project? Together with the group, we documented the impact and defined the path to resolution.
But after the meeting, I went to that person directly. And I made it clear: A Deal is a Deal. What is in this protocol is a valid contract, formulated by you, confirmed by you. I will not accept this a second time.
What happened next: within a few meetings, everyone in the round understood, including senior managers from external partner companies, that commitments are kept. Not because I was loud, but because I was consistent.
The protocol principle: Whose words are in it?
The decisive difference between a meeting protocol that nobody reads and one that works: I do not write down what I understood. I ask the accountable person: How should I note this? And then: By when will you deliver this? And then I let the group discuss whether the deadline is realistic.
When a delivery faces the person’s own commitment, formulated in their own words, then I forgot is no longer an option. That is the W-step as commitment architecture, not as hope.
India: When silence is not failure, it is respect.
In Pune I encountered a situation I had not read about in any leadership book: my team was not delivering. Escalated twice, twice received Yes, we are working on it. Then I flew to India for four weeks.
What I discovered in two days on the ground: the plant manager had been giving my team hidden parallel tasks to support the plant. My team was caught between two chairs, the German manager on one side, the plant manager with local authority on the other. They had no way to do it right.
The solution was not a coaching exercise. It was a direct conversation with the plant manager about accountabilities, the RACI for the team, on paper, bilaterally agreed. After that, my team relaxed, deliveries came back on track, and we were even able to expand the scope of our collaboration.
What I learned: behind every Yes, we are working on it can be a situation where the team had no structural choice. Ask instead of accuse. Go there instead of calling. The Radical Reality is often not found on a video call.
Measurable value: the hard ROI for every stakeholder.
This is not a seminar about soft skills. It is a clinical intervention to protect your EBIT, your talent pipeline, and your SOP schedule.
GROW in the SDV transformation: Why 2026 is the wrong year to skip structure.
The transformation to software-defined vehicle (SDV) architecture fundamentally changes the requirement dynamics in R&D departments. Feature-freeze dates shift. OEM platform decisions change mid-project. Release cycles shorten. That sounds like an argument against structure. It is the exact opposite.
- Grounded Goals in SDV projects do not mean rigid adherence to original specs. They mean clear binary gate criteria for the current sprint, so that every requirement change runs as a formal goal update through the monitoring cycle, not as an informal scope shift that nobody can trace.
- Radical Reality is particularly critical in SDV projects. When requirements change at weekly pace, the temptation for Green-Melon reporting is highest. Teams obscure uncertainty as on track to avoid political pressure, exactly when you need the real information most urgently.
- Weaponized Will in SDV environments means explicit commitment protocols for every requirement change. Whoever says yes to a new specification commits to a binary deliverable, not a best effort. That is how you prevent the Translation Tax.
FAQ: Tactical Sparring on the BYG GROW Method
Results or Excuses? There Is No Middle Ground.
In R&D and production, you either hit the SOP or you do not. If you are ready for Radical Agency: the science is proven, the Industrial DNA is here. The only variable in this equation is your commitment.
👉 Book Your Free Reality Check
The next step: mentoring matched to your leadership reality.
The GROW Method is the tool. Which guidance fits you depends on where you stand. Four tiers, one method.
Do Not Rely on Theory, Trust in 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 and 3). Over 1,000 documented coaching hours.
- Slovakia Reference: Built the complete electronics department at Brose Prievidza from 0 to 40+ engineers. EUR 2M technical laboratory. Full product responsibility for IFE and POT lines. Department still runs today under my successor.
- India Reference: Coached 12 executives at Brose India Pune (2023 to 2024). Established the Brose Training Academy Pune. Confirmed by Vasanth Suratkal Kamath, President Brose India.
- Task Force Reference: Led a 50-person Task Force in a high-value automotive crisis. Real-time application of the BYG GROW Method under maximum OEM pressure.
Related methods and depth:
Intercultural mentoring: the DE-SK-IN leadership bridge
Remote Leadership: leading distributed teams
Systemic leadership does not end after one call.
Follow for unfiltered insights and straight-talk strategies: