About

What I do.

I build the systems a product organization runs on: how it decides what to build, scales execution, and learns whether it worked.

Throughout my career, I've led products from discovery through scale, creating solutions that deliver lasting customer and business value. But underneath all of that product work, one constant remains: the operating models and capabilities a team uses to operate effectively. When those systems are strong, an organization compounds what it knows and executes consistently. When they're missing, it keeps re-solving the same problems.

The sharpest version of this is experimentation and measurement. I build both the products that help organizations validate growth opportunities and the programs that embed continuous learning into how teams build. A test is only as valuable as an organization's ability to act on and remember it. The same logic applies anywhere team operations become the bottleneck, whether that's strategy, intake, prioritization, or planning cadence.

That is why this work spans design, engineering, data, and business. It isn't about wearing four different hats; you simply can't build the system that connects those functions without being fluent in all of them. That breadth is how I do the job, not the job itself.

The sauce

I approach product through four interconnected lenses: design, engineering, data, and business. Working across these disciplines allows me to build products that deliver measurable outcomes while improving the product organizations that build them.

Design
Customer needs
Engineering
Technical execution
Data
Evidence and learning
Business
Commercial outcomes

What I can help with

Turn ideas into products From discovery through delivery, I help teams turn promising ideas into products customers adopt and businesses can grow.
Build with clarity When ownership is unclear, priorities compete, or delivery slows down, I help product organizations create the structure, alignment, and rhythm that allow great work to happen.
Understand what actually works Build measurement, experimentation, and decision frameworks that replace assumptions with evidence and accelerate learning.
Put emerging technology to work Whether it's AI, data, or a new platform capability, I enjoy figuring out how emerging technology can be enabled and adopted successfully.
Turn prototypes into products, fast Bridge the gap between a successful proof of concept and a product that can scale, operate reliably, and generate lasting value.
Connect the organization I enjoy creating the conditions that make collaborations successful. Bring together design, engineering, data, commercial teams, and leadership around shared outcomes instead of competing priorities.

How I work

I'm not afraid to ask.

I've learned the fastest way to build the wrong thing is to assume. Curiosity uncovers opportunities that assumptions often miss.

I naturally zoom out before I zoom in.

Whether it's a feature, a roadmap, or an organization, I like understanding the whole system before changing one part of it. So -as covered- I may ask questions

I absorb ambiguity.

One of the most valuable things a product leader can do is create enough clarity that everyone else can focus on building instead of interpreting.

I look for the bottleneck.

My engineering background taught me that every system has a constraint or a few. I instinctively look for it before optimizing everything else.

I prefer evidence over certainty.

I don't expect every decision to be perfect. I care more about creating fast feedback loops that help us learn what works.

I connect disciplines.

I enjoy working at the intersection of design, engineering, data, and business because that's where the best product decisions tend to happen and many questions get answered.

I simplify complexity.

Whether it's a product strategy or an operating model, I enjoy taking something that feels complicated and making it easier to understand, discuss, and execute.

I keep an eye on what comes next.

I've learnt that a solution can create more problems and while shipping is important, so is thinking about what the next team, feature, or decision will inherit.

I care about how products get built and used.

The product matters, but so do the environment that produces it and the people expected to adopt it. Products are a reflection of the organizations that build them.

I'm drawn to messy problems.

The kinds of problems without obvious owners, clear answers, or well-defined paths are usually the ones I find most rewarding.

Embedded Execution.

I work best embedded directly alongside technical and non-technical operational partners - sitting in the trenches to observe daily workflow friction, prototype immediate fixes, and translate hands-on needs into scalable solutions.

Capabilities

  • Build Products

    Product strategy & vision · Discovery & user research · Roadmaps & prioritization · Requirements · Delivery and go-to-market · Monetization & commercial model · AI product strategy & development · LLM-assisted prototyping · Design-to-engineering fluency · Front-end development · Product design

  • Build Product Operating Systems

    Product operations · Operating model design · Portfolio & delivery governance · Planning cadences (QBRs, offsites) · Capacity management · Process design & change management · Cross-regional orchestration · Vendor & partner management · AI adoption & enablement

  • Measure Impact

    Experimentation platforms · Experiment design & statistical rigor · A/B testing & Geo Lift · Measurement strategy & governance · Test-and-learn programs · Personalization & optimization

  • Turn Data Into Decisions

    Data strategy & governance · Analytics & reporting · Dashboards & visualization · Decision frameworks

  • Leadership & Management

    Cross-functional leadership · Stakeholder management · Executive communication & storytelling · Talent development & mentorship

  • AI Prototyping & Developer Stack

    Claude · OpenAI · Gemini · Cloudflare · Cursor · GitHub · Local AI Workflows ("Vibe Coding")

* A representative sample, not an exhaustive list.

Selected experience

  • Sr. Director, Product - Data, Media & Experimentation

    Monks

    Strategy, governance, and commercialization for the media product portfolio; led the ground-up build of its flagship experimentation & measurement platform.

  • Lead Product Manager - Experimentation

    Best Buy

    Built the in-house experimentation platform that replaced third-party tooling across a high-traffic e-commerce ecosystem, and embedded an always-on test-and-learn program.

  • Product Manager - Audience Insights & Analytics

    McKinsey & Co

    Led a 10+ person team building self-serve analytics and reporting products for stakeholders across business units globally.

  • Product Manager - Data Acquisition & Ops

    22Squared

    Established the data-acquisition practice and operating model from scratch, and moved the data & analytics org to Agile.

Earlier: measurement and activation at AutoNation, product-marketing design at Assurant, and a first career in engineering and design. Full history on LinkedIn →

BS Industrial & Mechanical Engineering · MS Petroleum Engineering · BFA Web Design & Interactive Media

How I write

I develop the ideas, arguments, and examples in my writing from my own experience and research. I use AI as an editing partner to question the structure, clarify passages, or tighten language. I review and revise every piece, and the final judgment about what to say and how to say it is mine.

The Story Behind the Sauce

If my career had a shape, it would probably look like a bowl of spaghetti.

I've spent years trying to explain it. Engineering. Design. Product. Strategy and Operations. Experimentation and Measurement. AI. Marketing and Advertising. Analytics. On paper, it can look like I couldn't make up my mind. But the funny thing is, it never felt that way, at least not to me. I knew the journey was leading me somewhere worthy of its sauce.

I've always been drawn to interesting problems. Not because I wanted to become an expert in every discipline, but because every new challenge seemed to teach me something new, answer one question while raising three more. So I'd follow those too.

Looking back, I wasn't changing directions. I was following my curiosity and collecting perspectives. What looked like separate paths eventually revealed themselves to be deeply connected.

One role developed my systems thinking. Another taught me how products are built. The next showed me how to measure them, and another how organizations make decisions. Along the way came lessons in experimentation, operations, strategy, leadership, and the often messy reality that exists between having a good idea and successfully delivering it.

Eventually, those experiences stopped feeling disconnected. They became a mental model for how I think about products, organizations, and the systems behind them.

Today, when I look at a product problem, I rarely see just the product. I see the decisions that led to it. The incentives around it. The process supporting it. The data informing it. The assumptions hiding underneath it. The people trying to make it all work.

That's also why I write. Writing has become my way of thinking out loud and testing ideas before I become too attached to them. Sometimes an observation turns into an article. Sometimes an article turns into a framework. Sometimes I revisit something I wrote months ago because I no longer agree with it. I like that. It means I'm still learning.

This site isn't meant to be a collection of polished answers. It's a record of the way I approach problems and the ideas that shape my work.

If you're here because we work together, because you're curious about product leadership, or because you simply enjoy pulling apart how things work, I hope you find something that makes you stop and think for a minute.

And if not, at least you'll know why my career looks like a bowl of spaghetti.