I help small and mid-sized tech and product teams start shipping again. No slides, no magic method. I look at what's stuck, we fix it, the team moves.
I embed with the team.
I see what's actually happening.
I don't sell a method.
I fix problems.
Fewer meetings.
More deliveries.
Teams that aren't shipping all send the same signals. Taken one at a time, each is easy to dismiss. Put together, they're expensive.
Nobody remembers what was promised in January. We reframe, we push back, we call it "prioritisation".
Daily, refinement, grooming, sync, retro. Code gets written in the evening — if anyone still has the energy.
Two teams in the same open space. Two understandings of the project. Two definitions of "done".
The board is red, production is blue. In between, dependencies nobody feels like unblocking.
The ones who wanted to ship go somewhere that ships. What's left is a tired team and settling turnover.
Every meeting re-covers the context. Decisions don't stick. You've become the team's human clipboard.
Some consultants sell a hat. I keep all of mine in the bag and pick the one that answers what your team is living this week.
— Crossed out: things I don't do. Ever.
The value isn't in whatever title gets written on the contract. It's in picking the right hat for the right moment.
One week you need a PO who actually decides. The next, a coach who puts two people in a room face to face. The third, someone who opens Jira and cleans house.
I adapt. And when I'm no longer useful, I leave.
Four steps. No surprises, no jargon, no €120-a-page slides. From first call to handover, you always know where we stand.
I spend time with the team. I watch, I ask obvious questions, I read tickets. The goal is to understand what people live with, not what's written in the plan.
What I'm working on, how we measure it, how often we revisit. No engagement that drags on with nobody remembering why.
With the team, not alongside it. I wear whatever hat the moment needs: PO who decides, facilitator who unblocks, pair who reassures. We ship.
I train someone in-house or line up a replacement. My success is the team shipping without me — not you renewing my contract every quarter.

I started in payment solutions, first for SMBs, then in a public-sector environment. Contexts where every change has a real product impact and where you have to be careful about what you move.
Then, mainframe-to-cloud migrations. Old code moved without breaking what's running, sprawling technical scopes, teams that have to keep delivering while the foundations change.
I'm not a developer — I don't write code. But I've spent enough time alongside technical teams to understand what they live through: the dependencies you can see coming, the trade-offs nobody dares make, the feeling of being the only one who sees where it's stuck.
Today I help SMBs with the same instincts: observe, name it, decide, ship.
No 12-field form, no commitment, no brochure landing in your inbox 20 minutes later. A LinkedIn message, a coffee, twenty minutes. We'll see if we click.
in Reach me on LinkedIn