Sample Core Story

I've always been the person who asks the question nobody wants to ask yet. Not to be difficult. I just can't move forward until I understand what the user is going through, beyond what the metrics say.

Six years in B2B SaaS, my job has been to sit between engineers, designers, salespeople, and customers and find the thread that connects what everyone needs. I don't start with the roadmap. I start with the conversation. What's the customer struggling with right now? What did they try before they called us? What would their life look like if this thing actually worked? The roadmap comes after I understand the problem well enough to feel it.

“Most PMs hand off requirements and walk away. You sit with us in the trade-offs. Engineers trust you because you understand why things are hard, not just what needs to get built.”

— Sarah C.

The work I'm proudest of started with a hunch. We kept losing enterprise deals to a competitor, and the team assumed it was a feature gap. I spent two weeks doing nothing but customer calls and realized the issue wasn't features. It was that our onboarding made people feel stupid. They didn't need more capability. They needed to feel competent faster. We rebuilt the first-run experience around that insight, and it became the fastest-growing product line in the company.

“When the business puts pressure on the product, you push back, but you do it in a way where everyone still feels like you're on their side. That's a hard thing to pull off and you do it consistently.”

— Marcus J.

I move fast between big picture and small details. I can hold the shape of a product strategy in my head while also noticing that one button label is going to confuse someone. The thing I've learned is that the best products come from teams where everyone trusts each other enough to say what they really think. That's the environment I try to create.