Five signals that the technology isn’t the problem.
The licenses are bought, individual teams have long been experimenting – and yet day-to-day project work looks like it did two years ago. How you can tell:
- The second AI pilot ends like the first: as a one-off experiment without consequences.
- Backlogs grow, sprints don't get finished, reviews remain status meetings.
- Ten AI ideas are on the table – and the decision which one comes first gets postponed again.
- Who reviews AI results and who is accountable for them is unresolved.
- Too many parallel projects: everything is started, nothing gets finished.
And you wonder why, despite the methods you’ve introduced, everyday work doesn’t feel any different. My focus is exactly there: software-driven R&D, where development and organization are closely intertwined.
Whether AI pays off isn't decided by the tool, but by three questions: Who reviews? Who's accountable? What's allowed to wait?
Consulting, coaching, training – which fits you?
Three formats, depending on where things are stuck right now: consulting for the organization, coaching for you, training for your teams. Bookable individually or combined.
Organizational Development & AI Readiness
For R&D units where every AI pilot gets stuck on the same questions: Who reviews? Who's accountable? What's allowed to wait?
- AI readiness workshop
- Taking stock: how work is prioritized, decided, and delivered today
- Pilot integration in everyday work
- Support over several months
Leadership Coaching & Development Support
For leaders preparing decisions on roles, priorities, and AI use – with a counterpart who knows R&D leadership from firsthand practice.
- Leading through uncertainty
- Clear decisions and roles
- Sparring ahead of decisions with long-term impact
- MBCI and ICF standards
Trainings for Project, Product, and Process Skills
For teams that want to prioritize, deliver, and learn better in complex environments.
- Agile project management (Scrum-Kanban mix)
- Multi-project management with Portfolio-Kanban
- Product Discovery & business model development
- Understanding and mastering AI systems
Project management, Kanban, and coaching aren’t side dishes here: they build the work system in which an AI workflow survives everyday operations – with clear roles, priorities, and reviews.
A five-stage approach – how a consulting engagement works
The five stages are a frame, not a rigid process. Coaching and trainings can be added as modules at any stage.
- System diagnosis.
How you prioritize, decide, and deliver today, and where AI would run up against your structures.
- Data and workflow analysis.
Where data needs to flow differently and which roles shift: the places where your work concretely changes.
- Pilot integration.
A first AI workflow in real everyday work, with review, accountability, and quality assurance.
- Scaling with Train-the-Trainer.
Your experienced people pass the approach on themselves, as an internal circle of multipliers.
- Re-diagnosis after 6 to 12 months.
Take a fresh look, decide the next stage – based on what you've measured by then.
We'll work out which stages fit your plans in the intro call →
How I work
Understand first, then design. Before I commit to a single hour of training, I clarify with you directly where the problem really sits. That only works directly: through an intermediary I get a briefing – but not your problem. That’s why every engagement starts with a 45-minute intro call and a written concept outline.
From practice, not from the textbook. In my day job I lead software and systems development for robot-assisted computed tomography at Fraunhofer IIS / EZRT – robots that X-ray industrial components. That puts me in the same prioritization, review, and AI questions you face, every day. What I recommend, I do myself.
Three roles, clearly separated. I work as a trainer, coach, or consultant, sometimes in a hybrid form. I say upfront which role I’m taking at any given moment. That way, the consulting trap where method and accountability blur never opens up in the first place.
What others say
“One of the best and most engaging seminars I have attended so far. I can recommend Maik as a trainer for agile methods without reservation.”
“The way he moderates group situations quickly establishes trust and encourages people to share their ideas. This mixture of warmth and competence is a great asset to any team.”
Intro call: 45 minutes, free.
After 45 minutes you’ll know whether and how to proceed. You then get a written concept outline with a proposal, effort estimate, and terms – only then do you decide on the engagement.
- Understand the occasion: trigger, sponsor, target group
- Clarify the goal: what should be different afterwards?
- Explore the format: full path, individual modules, or a mix
- Agree on next steps: concept outline follows within 3 to 5 days
