From fuzzy problem to shipped product.

I start by getting clear on the problem before anyone touches a solution: running discovery workshops, gathering requirements, and turning ambiguous asks into functional specs and acceptance criteria that design and engineering can actually build from.

I build intake and backlog systems that give every request a clear path, then prioritize by real business impact, not who asks loudest. The result is a roadmap the whole team can see, trust, and plan around.

I don't just theorize about emerging tech. I built Outpost, a coffee-shop finder for remote workers, from product brief to working prototype using Claude Design, Claude Code, Supabase, and Vercel, running it like a real product team with Linear tickets, grooming, and a feedback loop.

Getting a skeptical engineer, an anxious stakeholder, and a design team pointed in the same direction is the part of the job I like best. I translate between disciplines, spot the quiet bottleneck before it breaks a timeline, and keep everyone moving together.

I build reporting that's easy to self-serve. When our tools couldn't give me the visibility I needed, I taught myself SQL and pulled my own Metabase reports, so decisions on scope, capacity, and priorities rest on real numbers.