01 · When things are on fire
Troubleshooting & Project Recovery
I unblock technical bottlenecks, clear up misunderstandings and bring stalled projects back on track — fast, focused and lasting.
Typical situations
When a project stalls, every hour counts. Whether the deadline is close, technical hurdles seem insurmountable or requirements are not clearly understood — in critical phases I take responsibility quickly and deliberately, create transparency and deliver actionable decisions that bring your project back on track.
-
Deadline approaching
Core features are not ready to ship.
-
Team stuck
Blockers in architecture, build/deploy or integrations.
-
Unclear requirements
Conflicting requirements; scope and priorities keep shifting.
-
Interfaces failing
ERP, PIM, CRM, payment or search — errors or latency.
-
Performance & stability
Issues put go-live or conversion at risk.
-
Knowledge missing
A key person has left — nobody really knows how the system runs.
Approach
- 1
Rapid analysis
Review of code, architecture, pipelines and tickets. Clarify goals, risks and blockers. Result: a short diagnosis with the top risks and first quick wins.
- 2
Prioritisation & action plan
Decision-ready measures with cost/benefit estimates, ownership and timeline.
- 3
Execution & team alignment
Hands-on fixes to build/deploy, caching and interfaces, moderation between tech and business, a clear definition of done.
- 4
Stabilisation & handover
Tests, monitoring and alerts, documentation, knowledge transfer and agreed follow-up checks.
Outcomes
Release plannable again
Critical blockers are resolved. The team can ship, the date holds.
Clear action plan
Measures with ownership, effort and dates.
Measurable improvements
Performance, stability and deployability — documented before and after.
What you get
- Short diagnosis (risks, root causes, impact)
- Action plan with effort/impact matrix
- Fixes and pull requests, tickets and technical notes
- Handover document with monitoring recommendations
Frequently asked questions
When does troubleshooting and project recovery make sense?
When an IT project is delayed or technically blocked – for example because the deadline is approaching, interfaces to ERP, PIM, CRM or payment are failing, or a key person has left the team. I analyse the situation, prioritise the measures and bring the project back on track.
How quickly is there a first result in a project recovery?
Within 24–72 hours there is a short diagnosis. It names the top risks, root causes and impact as well as first quick wins. Remote is the fastest start with the shortest onboarding; on-site work is more direct but needs a little more lead time. It all starts with a no-obligation 30-minute initial call.
Do you work with our existing team or vendor?
Yes – I work with your team and with existing vendors or agencies, not around them. I implement fixes to build/deploy, caching and interfaces hands-on and moderate between tech and business. If needed, I temporarily take on the role of interim tech lead, remotely or on-site across the DACH region.
What do we have at the end of a project recovery?
A short diagnosis, an action plan with an effort/impact matrix, the delivered fixes and pull requests with tickets and technical notes, and a handover document with monitoring recommendations. I document improvements in performance, stability and deployability before and after.
Other services
Technical Consulting
Guidance on system selection, architecture and integration — clear to management and engineers alike.
Coaching & Mentoring
Support for development teams and tech leads during live projects.
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