Leadership

A product operating system, not just a roadmap.

How I think about leading product organizations — the principles, the frameworks, and the operating system underneath the work.

Five principles I lead by

Roadmaps are bets on outcomes — usage, retention, revenue. Velocity is a side effect of clarity.

Framework

RICE-by-outcome

Reach × Impact × Confidence ÷ Effort — but Impact is mapped to one north-star outcome per team, not a generic score.

Framework

PQL definition

A defensible Product-Qualified Lead model based on cohort behavior, not assumptions.

Framework

Product-to-Impact Bridge

Metric simulation → opportunity trees → leading indicators. A 3-layer model that connects product decisions to revenue, turning signals into a business case finance understands.

Framework

Pre-mortem

Before any large bet — 'it's six months from now and we failed. Why?'

Continuous discovery is the cheapest moat a product org can build.

Domain Knowledge

Know the industry, competitors, and customer segments. Read reports, track trends, and map the terrain you compete in.

Motivation

Align work with personal passion and company mission. Curiosity and ownership are what turn research into real insight.

Empathy

Understand pain points through interviews, personas, and direct feedback. Build a user feedback loop that never sleeps.

Data

Measure performance, spot trends, and make informed decisions. Identify key metrics and start every day with data.

Creativity

Synthesize insight into new possibilities. Use structured brainstorming and cross-functional collaboration to turn findings into bets.

Operating cadences, dashboards and frameworks scale further than a heroic PM.

Roadmap

Centralized, outcome-anchored, visible to the whole company.

Analytics

Shared event taxonomy and a single source for activation, conversion and retention.

Discovery

Always-on customer feedback loop, with explicit owners.

Competitive intel

Continuous, structured, distributed — not a once-a-year deck.

Rituals

Quarterly planning, monthly outcome newsletter, weekly team standups, everything with accountability in heart

Dual-track agile

Discovery and delivery run in parallel, never a sequential 'discovery phase'.

AI is an operating model change, not a tool purchase.

I lead teams that operate AI-natively end-to-end — from how we interview customers to how we ship and review. The bar isn't 'we use AI tools'. It's that the workflows would not be the same without them.

Discovery
AI-assisted market research and synthesis of customer interviews, support tickets and validation sessions
Design
Shared context Github repo and prototyping workflows that compress feature prep work from weeks to days.
Delivery
AI as a co-pilot not only for PRDs, but also for tickets, release notes, internal communication and competitive intelligence.
Decisions
Reusable evaluation rubrics so AI outputs are reviewed against business outcomes, not vibes.

Team shape and talent caliber determine the ceiling. These are the moves I use to staff and structure for outcomes, not headcount.

Onboarding is product design

How someone enters the team determines how fast they contribute. I treat it as a designed experience.

Manage the ceiling, not the floor

My job is to remove what's blocking the best people, not to pull up the bottom.

Clear ownership, not consensus

I hire people who can push back. Silence in a room of smart people means something is wrong.

Talent density

Hire fewer, level higher. Reviewing hundreds of applicants is part of the job.