Industry Knowledge
I've shipped products in healthcare, automotive, heavy-duty trucking, and public safety. Not as a tourist passing through — as the person responsible for the roadmap. Each industry has its own regulatory gravity, its own buyer psychology, its own definition of trust. Moving between them didn't confuse me. It taught me to see the patterns underneath the surface differences. The problems are almost always the same. The context is everything.
Building and Leading Visionary Product Teams
I don't recruit for resumes. I recruit for curiosity — people who can't stop asking why, who get uncomfortable with "that's just how we do it." Once I have those people, my job is to give them a direction worth running toward and then get out of the way. I set the north star, I remove the obstacles, and I trust the team to be smarter than me about their part of it. That's not a management philosophy I read somewhere. It's what I've seen actually work.
Cultivating High-Performing Product Managers
The thing I'm most proud of isn't a product I shipped. It's the PMs I've worked with who went on to lead their own teams and build things I never could have imagined for them. Mentorship isn't about teaching frameworks — anyone can hand someone a book. It's about teaching judgment. How to know which problem is actually the problem. How to hold a hard conversation without burning the relationship. How to trust your read on a room. That's the work I care about most.
Driving Cross-Functional Alignment
In most organizations, the product team is the translation layer — engineering speaks one language, sales speaks another, executives speak a third, and users are barely in the conversation at all. I've spent 25 years building bridges between those groups. Not by watering down the message, but by finding the version of the truth that each person can actually act on. When everyone understands the why — really understands it — you stop fighting over priorities and start moving.
Mastering the Product Lifecycle
I've built products from a napkin sketch and I've sunset products that used to be someone's whole career. Both require courage. The launch gets the press, but the harder decisions happen at the edges — in early discovery when you're not sure if the problem is real, and late in life when you have to tell a team their work is done. Knowing where you are in the lifecycle changes every decision you make. I've been at every stage. I know what each one actually feels like.
Data-Driven Problem Solving
Opinions are common. Insight is rare. I've worked in data products long enough to know that the most dangerous number is the one everyone agreed to track without asking why. I build measurement frameworks that connect what teams do to what customers experience — not activity metrics that make everyone feel busy. And I came up as a developer, so I know the difference between data that's actually trustworthy and data that looks trustworthy. That's not a small distinction.
A Forward-Thinking Mindset
I don't spend a lot of time predicting the future. I spend time building teams and systems flexible enough to respond to it. The product leaders I've watched struggle are the ones married to a vision of what the market will be — the ones who succeed stay curious, stay close to actual users, and make small bets constantly instead of one enormous one. I've never had a five-year roadmap that survived contact with year two. I've had plenty of teams that figured it out anyway.