03 · When a team needs to grow
Coaching & Mentoring
I strengthen engineering teams and technical leaders — practical, focused and lasting. Better processes, higher code quality, clearer decisions.
Typical engagements
Successful teams need more than technical skills — they need clear processes, good communication and the ability to make sound decisions on their own. I help development teams, technical project owners and engineering leads improve how they work and strengthen their technical decision-making.
-
Team coaching
Better collaboration, efficiency and ownership.
-
Mentoring for tech leads
Leadership skills for technical leaders.
-
Code & architecture reviews
Higher quality and better maintainability through structured reviews.
-
Agile process improvement
Scrum, Kanban or hybrid models — applied pragmatically.
-
Workshops & training
Specific technologies or best practices, applied to real projects.
-
1:1 mentoring
Confidential sparring for senior engineers and leads.
Approach
- 1
Analysis & goal-setting
Capture current ways of working, team dynamics and technical challenges, and agree goals together.
- 2
Coaching concept
A plan tailored to team size, maturity and project context.
- 3
Execution & guidance
Coaching sessions, workshops and reviews — practical and tied to real projects.
- 4
Evaluation & continuation
Measure results, adjust measures and make improvements stick.
Outcomes
Less friction in the team
More efficient processes, clear ownership, faster decisions.
Higher code quality
Technical quality becomes part of how the team works — not just an aspiration.
A better bridge to the business
Tech teams can explain and prioritise their decisions.
What you get
- Coaching and mentoring plan
- Review reports with concrete recommendations
- Training or workshop materials
- Follow-up sessions to make change stick
Frequently asked questions
Who is coaching and mentoring for?
For development teams, technical project owners, engineering leads and senior engineers – whenever a team wants to collaborate better, raise code quality or make technical decisions more independently.
How does coaching for engineering teams work?
I start by analysing ways of working, team dynamics and technical challenges, and we agree on goals together. This leads to a coaching concept tailored to team size, maturity and project context, which I deliver through sessions, workshops and reviews and then evaluate. The first step is a no-obligation 30-minute initial call.
Is the coaching done on real projects?
Yes. Code and architecture reviews, workshops on specific technologies or best practices, and confidential 1:1 mentoring start where your team is actually working. I apply agile methods such as Scrum, Kanban or hybrid models pragmatically – remotely or on-site across the DACH region.
What stays with the team after the coaching?
A coaching and mentoring plan, review reports with concrete recommendations, and training or workshop materials. Agreed follow-up sessions make sure changes stick and technical quality becomes part of how the team works.
Other services
Troubleshooting & Project Recovery
Analysing and stabilising projects that are delayed or technically blocked.
More about this service : Troubleshooting & Project Recovery
Technical Consulting
Guidance on system selection, architecture and integration — clear to management and engineers alike.
A first conversation takes 30 minutes and comes with no obligation.
30 minutes, no obligation. Afterwards you will know whether and how I can help.
or directly: hello@michaelseliger.com