Thinking
I don’t think product leadership is primarily about roadmap judgment.
It’s about designing how decisions get made—how ideas are shaped, how tradeoffs are evaluated, and how teams connect their work to outcomes.
In most organizations, these systems are implicit, inconsistent, and highly dependent on individuals. That creates friction, misalignment, and uneven product quality.
Get a grounded read on responsibility, evidence, impact, or what to read next.
When there is no shared operating model:
These are not just execution issues—they are product problems.
I believe the team’s operating model is part of the product outcome.
Strong product teams don’t just build features—they build systems that make good decisions repeatable.
That means creating shared structures for:
In practice, this meant designing and standardizing a product operating model across the team.
The goal was not to add process, but to make decision-making clearer, more comparable, and easier to scale.
We defined a consistent lifecycle for every initiative—from early signals and problem definition through discovery, delivery, and impact measurement.
This created a shared language across product, engineering, and stakeholders, and made it clear how any piece of work connected to outcomes.
Operating model
One of the core challenges was inconsistent prioritization. Different teams evaluated work differently, making tradeoffs difficult.
We standardized a lightweight scoring model using RICE, paired with “napkin math” estimates grounded in available data. This allowed teams to compare opportunities on a shared scale and made prioritization discussions faster and more objective.
Prioritization
We introduced a consistent product review cadence to connect strategy, execution, and outcomes.
Teams regularly reviewed work across three states: what’s happening now, what’s coming next, and what impact has been delivered. This created alignment without heavy process and ensured that progress, risks, and results were visible across the organization.
Review cadence
At the team level, we aligned sprint planning and execution with the broader operating model.
Clear constraints on work in progress and a consistent sprint structure helped teams focus on delivering outcomes, not just managing backlog volume.
Execution rhythm
We standardized roadmap communication using a Now / Next / Later framework.
This allowed teams to balance short-term delivery with longer-term strategy, while also making uncertainty explicit. Stakeholders could understand what was committed, what was being explored, and what was intentionally deprioritized.
Roadmap language
To reduce friction and improve consistency, we embedded AI-assisted workflows across the lifecycle.
Custom GPTs supported idea generation, opportunity framing, ROI estimation, and PRD creation—ensuring that every initiative started with a consistent level of clarity and structure.
This allowed teams to spend less time formatting work and more time evaluating and executing it.
One challenge we encountered was that all product work was implicitly evaluated as if it were consumer product work.
This created misalignment—platform, data, and operational products were often measured against the wrong expectations, leading to unfair comparisons and poor prioritization decisions.
To address this, we introduced a framework to clarify different product types, their metrics, time horizons, and dependencies.
While this approach resonated strongly with product teams, it did not ultimately gain executive adoption.
Even so, it highlighted an important gap: without shared understanding of product types, organizations struggle to evaluate work consistently.
Product types
This work improved more than execution—it improved how decisions were made across the organization.
Teams were able to:
More importantly, it made the operating model visible—so it could be improved intentionally, rather than emerging by accident.
That is the core of how I think about product leadership.
Contact
The essay is here to show how I think about product leadership in practice, not just in principle. Happy to go deeper on the operating model, the tradeoffs, or how this translated into day-to-day work.