I’ve worked inside technical environments where capable people could all be right — and the project still got stuck.
That experience taught me to look beyond individual people — and at the goals, priorities and decision structures shaping how they work together.
I thought I was solving a technical problem. I wasn’t.
One experience that shaped my work started with what looked like a technical request.
Engineering had been called in. Tasks had been assigned. People were working hard.
But the deeper I looked, the clearer it became: the problem wasn’t a lack of technical expertise.
It didn’t need another engineer. It needed a better system for turning expertise into coordinated action.
I started seeing the same pattern again and again.
Different functions were often looking at the same project through completely different — and completely legitimate — lenses.
ENGINEERING
Technical feasibility, performance, technical risk.
QUALITY
Compliance, robustness, customer requirements, failure risk.
BUSINESS / PRODUCT
Customer value, timing, commercial outcomes, market needs.
MANUFACTURING
Stability, capacity, manufacturability, operational impact.
None of these perspectives are irrational.
But when each function optimizes for something different without a shared way to resolve the trade-off, reasonable people can make completely different decisions.
From solving technical problems to improving the system around them.
Over time, my work became less about fixing isolated technical problems — and more about creating systems that helped people make better decisions and work more reliably.
500+ engineering hours/year saved
Through clearer knowledge structures and greater employee independence.
€260k investment avoided
Through technical analysis, customer alignment and a stronger decision basis.
€1.5–1.8m potential investment avoided
Through a different technical system concept addressing space and capacity constraints.
~40% fewer system failures
After building more structured troubleshooting and knowledge systems.
The common thread was always the same: the biggest improvements came when the system around the work became clearer.
Most teams don’t have a communication problem. They have a system problem.
When the same conflicts, reopened decisions or coordination loops keep returning, I look at the structures around the people:
Goals · Priorities · Responsibilities · Information · Decision logic
Clarity is Respect.
To me, clarity is not just about efficiency. It is also a form of respect.
Respect for people’s time.
Make things clear before ten people have to figure them out individually.
Respect for responsibility.
Make clear what was decided, who owns what and what happens next.
Respect for people’s expertise.
Bring the relevant perspectives into the decision before it is made.
Good systems reduce unnecessary friction so people can spend more energy on the work that actually matters.
I don’t want capable people spending their energy fighting avoidable friction.
People spend a huge part of their lives at work. I don't believe that work should be harder, more chaotic or more exhausting than it needs to be.
That is why I built Gotenbruck Consulting: to help technical teams spend less energy on repeated priority conflicts, rework and organizational friction — and more on solving the problems that actually matter.
How does this shape the way I work today?
CLEAR
Make complexity understandable.
PRAGMATIC
Build systems that work in real projects.
FAIR
Take legitimate functional perspectives seriously.
SYSTEMIC
Look at the structures behind recurring friction.
Good systems don’t eliminate different perspectives. They make them useful.
Technical background. Human-centered approach.
Materials Engineering
RWTH Aachen University
Economics & Psychology
120 ECTS credits in Economics and 60 ECTS credits in Psychology — adding a broader perspective on business decisions, organizations and people.
Industrial R&D & Scientific Research
Simulation, experiments, metallurgy and technical analysis.
Published Research
Peer-reviewed publications in metallurgy and high-purity aluminium.
Change Management & Systemic Coaching
Certified Change Management Consultant, Business & Systemic Coach.
Regulated Production & Process Engineering
Technical responsibility, process structures, investment and change projects.
That combination helps me understand the technical depth, the business trade-offs and the human dynamics behind cross-functional decisions.
Today, I use that perspective to help technical teams make better cross-functional decisions.
Especially when several functions have legitimate priorities and an important trade-off is slowing progress, consuming capacity or repeatedly being reopened.
My role is not to decide which function is right. It is to create the structure that allows the team to understand the trade-off and make the decision together.
Different perspectives are not the problem. The problem is having no system for turning them into a decision.
If your team is full of capable people but still gets stuck between competing priorities, the problem may not be the people.
Bring the project issue that keeps coming back. We’ll look at what is behind it and whether the Priority Conflict Resolution Workshop is the right next step.