Debug the system. Unleash the engineer.
I’m an engineer who’s spent over twenty years building products and leading engineering teams, through the good stretches and the ones that nearly broke me. What I do isn’t a packaged program. It starts with a conversation and an honest look at what’s really going on, and works from there to get things moving again. I bring it to engineering teams and the leaders who run them, and to individual engineers one on one: find what’s actually in the way, fix the loop, and put the freed-up capacity into work worth doing.
Right now
AI made coding faster. It didn’t make teams faster.
Teams are generating more code than ever and shipping it slower. That’s not the tools, and it’s not the engineers. AI took the typing out of the job and made something obvious that was always true: writing the code was never the bottleneck. The bottleneck is everything around it, the review, the coordination, the decisions, the unclear ownership. Now there’s more code moving through that same system, faster, with the same constraints holding it up. AI doesn’t create that. It amplifies it, and it makes it impossible to ignore. The teams that pull ahead won’t be the ones running the most AI. They’ll be the ones whose system can absorb what it produces.
The ceiling
The ceiling on a team is usually the system, not the people.
Your engineers are good. They ship, they solve hard problems, they care about the work. And there’s still a gap between what the team is capable of and what the current setup lets out: velocity that stalls in handoffs, senior people quietly deciding to leave, creativity that dies on contact with the roadmap. What caps it is rarely the talent you hired. It’s the system around them, the defaults and the load and the shape of the work. Coaching is finding what holds that cap in place and taking it off, so the capacity you already pay for gets to show up.
The method
DEBUG, applied to the system instead of the code.
Diagnose
Find where the system actually stalls, not where it’s easiest to point. The real constraint is rarely the one everyone is already naming.
Evaluate
Separate what the system controls from what it’s only carrying. The second pile is usually bigger than anyone admits, and that’s where the drag lives.
Build
Put real structure under the load: the boundaries, rhythms, and defaults that hold when the week goes sideways. Same discipline for a team and for one engineer’s week.
Unlock
Clear the path for the work that got buried. The capacity didn’t vanish; the system was spending it somewhere no one could see.
Generate
Turn the freed-up capacity into results you can point at, so the change survives the roadmap instead of fading in a month.
Who it’s for
Two seats at the table.
Teams and their leaders
Deadlines met and the team intact. Senior people stay, delivery holds, and creativity survives the roadmap.
Individual engineers
One on one for the engineer who wants this job to feel like theirs again: a sustainable, energizing career without job-hopping to feel something.
How it works
What working together looks like.
It starts with a conversation, not a pitch. You tell me where the team should be operating and where it keeps stalling, and I ask the questions that surface the parts underneath it. From there we work the loop: find what’s actually capping the team, separate what you can change from what you’re only carrying, and build the systems and defaults that let good people do their best work instead of grinding it down. We keep it tied to real delivery, so the change shows up in what ships and who stays, not just in how the team feels about Monday. Same method one on one when it’s a single engineer.
The proof
I wasn’t going to show you these.
I used to leave this space empty on purpose. Anyone can print a five-star quote from “a happy client,” and I wasn’t going to insult you with one. Then people started writing them unprompted, and hiding them felt more dishonest than showing them. Read them or skip them. The work is the same either way.
“Investing in Apothix Coaching was a game changer for us. In just the first session, they helped 10x our subscription service. We launched a brand new side of our business with features we’d never even thought of before.”
Christopher Hopper · CEO, Somnium Publishing“Josh’s keen eye and vast knowledge in development structures, user usability, and overall work environments have been essential to every project.”
“I highly recommend Josh to every team that needs not only a very knowledgeable engineer, but also a very caring leader.”
If you want to unlock yourself or your team, drop me a note and we’ll talk. If it’s you as a person rather than your team, that’s the life coaching side.
Goes straight to my inbox. First conversation, not a pitch.