How I Work
Engineering excellence is not created by better documentation. It is created when organizations learn systematically from every failure.
Why I do, what I do
Technical problems rarely exist in isolation.
Throughout my career, I have repeatedly seen projects where enormous effort was invested, yet the most critical technical issues were identified far too late.
By then, teams are already under intense schedule pressure, working with fragmented knowledge, different perspectives, and increasing technical complexity.
This is exactly where I can help.
Together, we transfer proven engineering practices from highly regulated industries - such as automotive - to small and medium-sized manufacturers, hidden champions, and industrial organizations.
The same principles also deliver measurable value in sectors such as logistics, public administration, skilled trades, mechanical engineering, and defense.
Similar approaches are widely used in medical technology and the aerospace industry.
My experience as an engineer, a father, and a football coach has shaped the way I work. I believe successful collaboration is:
- Structured
- Objective
- Respectful
- Solution-oriented
Inspired by Lean Thinking and Toyota Kata
✅ We solve problems where they actually occur - not from an office or conference room. (Gemba)
✅ We replace assumptions with facts gathered directly from your processes.
✅ We develop cross-functional solutions that people support because they helped create them. (Nemawashi)
✅ Every solved problem becomes the foundation for continuous improvement - not just another completed project. (Kaizen)
Less Administration. More Engineering.
Excellent products and robust processes are built through technical discussions, shared understanding, and transparent documentation - not through maintaining spreadsheets.
Every hour spent manually updating Excel files is an hour that cannot be invested in engineering, innovation, or preventing future failures.
More importantly, productive technical discussions rarely happen by accident. They require clear communication, shared perspectives, and constructive collaboration. I meet your teams where they are today and apply proven methods pragmatically - not dogmatically.
The result is faster, better-informed decisions and fewer costly engineering changes later in the project.
In one defense project, our structured cross-functional analysis identified a safety-critical material incompatibility during product development.
As a result, costly field modifications and product changes were avoided before the product entered service.
methodIQ - Areas of Expertise:
Reactive
- Structured Root Cause Analysis (Ishikawa, 5 Whys, etc.)
- Systematic Problem Solving (8D, A3)
Preventive
- Transforming Excel-based FMEAs into effective engineering tools
- FMEA Sprint Facilitation for critical projects
- Internal Audits
Capability Development
- Method Reviews
- FMEA Competency Development
- Cross-Organizational Learning
One Observation Remains Constant
Even organizations with mature processes often overlook critical weaknesses - until they are systematically analyzed and openly discussed.