Product Leadership · Enterprise UX · Product Advisory
I help product teams turn complex systems into products people actually understand.
Let's talkA gap no one owns
The system
How it's built
Makes sense to the people who built it.
The user's picture
How users think it works
Confusing for the people who have to use it.
I close that gap. I understand how the system works under the hood, and how the people using it expect it to work — and I translate between the two. So people can use the system on their own, without asking an engineer for help.
How I work
Four ways I work with teams building complex software.
Platform Clarity Sprint
A short, focused check-up. I find the places where your system and your users' understanding don't match — and what that costs you. You get a clear map of the problems and a prioritized plan you can start on right away.
Enablement Build
The plan, put into practice. Clear user journeys, a shared set of design patterns, and a setup that lets your teams move on their own instead of re-discussing the basics every time. I make the calls that need judgment; the work arrives as a finished, structured package.
Embedded Product Leadership
I join your organization part-time, on an ongoing basis. I take care of the big picture across teams — journeys, patterns, one shared understanding of the product — while your teams keep building and keep the final say.
Advisory & Decision Forcing
A second opinion, a sparring partner, or the push a stuck team needs to finally decide. No documents, no deliverables — just clear calls for the moments where one decision unblocks everything else.
Nikolaus Rademacher
Most product teams have a translation problem: the system works one way, and the people using it expect it to work another way. Over time, the two drift apart.
That gap is what I work on. I help teams make complex software — big platforms, internal tools, business systems — understandable, so people can use it on their own. To do that, I look at both sides: how the system is built, and how the people using it think.
I don't come in as an extra pair of hands. I take responsibility for the big picture — how the product should work and feel, across all teams — while the teams keep building and keep the final say. Journey maps, design systems, and pattern libraries are the tools I use to make that picture visible.
When people's understanding and the system line up, trust follows. And for anyone making important decisions in their software, trust is the product.