Reading Notes

Ravi Mehta on the Product Strategy Stack, Twelve PM Competencies, and Selective Micromanagement

Source: Ravi Mehta on the Product Strategy Stack, Twelve PM Competencies, and Selective Micromanagement

Notes — Ravi Mehta on the Product Strategy Stack, Twelve PM Competencies, and Selective Micromanagement

Four questions [Adler frame]

Q1 — What is it about? A structured account of how product management works at different scales, built around three frameworks: the Product Strategy Stack (how the layers of product planning relate and sequence), the twelve PM competencies (what skills product managers need and how to assess them), and selective micromanagement (when deep hands-on management is appropriate and how to distinguish it from its pathological form).

Q2 — How is it argued? Through framework exposition with case illustration. Mehta presents each tool as something he developed by noticing a recurring failure mode in practice, then built a model to address. The competency framework is the most explicitly systematic — it is the basis of Outpace as a product. The Product Strategy Stack is the most counterintuitive and most argumentatively developed.

Q3 — Is it true? The claim that goals should follow the roadmap (not precede it) is logically sound: OKRs set before knowing the plan are unmoored from the work. The twelve competency model is a useful taxonomy, though the choice of twelve (rather than eight or sixteen) is somewhat arbitrary. The selective micromanagement distinction is valuable as a normalising frame — it gives managers permission to be hands-on without feeling they are failing at delegation. [?] The frontier-of-understanding goal types are asserted without comparison to other goal taxonomy systems (e.g. Reforge’s outcome vs. output framing).

Q4 — What of it? The Product Strategy Stack’s sequencing insight is immediately applicable to teams running OKR cycles: the sequence should be strategy → roadmap → OKRs, not OKRs → roadmap. The twelve competencies are most useful as a self-assessment and career development tool, not as a hiring rubric (too many dimensions for interview evaluation). The exponential feedback principle is simple and high-leverage: most managers give symptom-level feedback by default.

Glossary

Product Strategy Stack — five layers ordered from mission (top) to goals (bottom). Each layer constrains the one below. Goals are derived from the roadmap; the roadmap is derived from the product strategy; the product strategy advances the company strategy; the company strategy pursues the mission.

Mission — why the company exists. Stable.

Company strategy — how the company wins in its market. Multi-year, directional.

Product strategy — the specific bets the product team makes to advance company strategy. The PM’s highest leverage point.

Roadmap — the sequenced plan of work over a defined horizon.

Goals — measurable outcomes the roadmap is intended to produce. Set after the roadmap.

Velocity — quantity of work shipped per unit time.

Latency — time from forming a hypothesis to receiving data on it.

Selective micromanagement — intentional, time-bounded deep involvement in a specific project. Distinguished from micro-mismanagement by transparency, intent, and exit plan.

Micro-mismanagement — chronic interference driven by distrust. Demoralises and slows.

Scalable leadership — deliberate delegation to capable people with clear goals. The default aspiration.

Frontier of understanding — Mehta’s frame for goal-setting: goals should be set at the boundary of what the team does not yet know, matched to the risk type that is live for a given initiative.

Exponential feedback — feedback delivered at the root cause of a behaviour pattern rather than at the surface symptom. Compounds over time; symptom-level feedback produces local fixes only.

Twelve PM competencies — Mehta’s taxonomy of PM skills across four quadrants: product execution (specification, delivery, quality), customer insight (data fluency, voice of customer, UX design), product strategy (business outcomes, vision/roadmap, strategic impact), leadership (stakeholder inclusion, team leadership, managing up).

Key frameworks

Product Strategy Stack [§ The Product Strategy Stack]

The five layers and their relationships:

  • Mission → Company strategy: strategy must be consistent with mission
  • Company strategy → Product strategy: product bets must advance company strategy
  • Product strategy → Roadmap: roadmap reflects which product bets to pursue and in what order
  • Roadmap → Goals: goals are commitments about what the decided roadmap will produce

The key inversion: goals are at the bottom, not the top. A common failure is setting goals before a roadmap exists — producing OKRs that are either arbitrary or reverse-engineered from whatever work was already planned.

Velocity vs. latency [§ Velocity vs latency]

The diagnostic question: when was the last time we ran an experiment that surprised us? A team that has not been surprised recently may have high velocity (shipping a lot) but high latency (taking too long to learn). The pathology of large companies is not laziness — it is the accumulation of process that slows the feedback loop.

Twelve PM competencies [§ The twelve PM competencies]

Four quadrants × three competencies each:

Product execution — specification, delivery, quality. The operational core: can the PM write a clear spec, ship on time, and maintain standards?

Customer insight — data fluency, voice of customer, UX design intuition. The understanding core: does the PM know the user and can they read the data?

Product strategy — business outcomes, vision and roadmap, strategic impact. The direction core: can the PM connect product to business results and articulate a horizon?

Leadership — stakeholder inclusion, team leadership, managing up. The organisational core: can the PM navigate the humans and systems around the product?

Most PMs are uneven across these twelve. The career diagnostic is to be honest about which competencies are weak and whether the current role rewards improving them.

Selective micromanagement [§ Selective micromanagement]

Three states:

  • Micro-mismanagement: high involvement driven by distrust. Chronic, undeclared.
  • Scalable leadership: high delegation, high trust, clear goals.
  • Selective micromanagement: high involvement, temporary, declared. Appropriate when: project is unusually high-stakes; team is new to the domain; something has gone off-track.

The requirement for ‘selective’ to be legitimate: announce it (‘I’m going to be very hands-on with this for the next six weeks’), time-bound it, and plan the exit.

Frontier-of-understanding goal types [§ Frontier-of-understanding goal types]

Four risk types that goals should address:

  • Understanding risk: is this the right problem and solution?
  • Dependency risk: is there an external blocker?
  • Execution risk: can we deliver this?
  • Strategic risk: are we about to be outmanoeuvred?

Setting goals requires identifying which risk is live. A metric that addresses execution risk does not resolve understanding risk.

Exponential feedback [§ Exponential feedback]

Surface feedback: ‘you missed the deadline.’ Root-cause feedback: ‘you accepted scope late in the cycle without adjusting the timeline; here’s what I’d like to see next time instead.’ The first produces a one-time adjustment. The second changes the behaviour pattern. Mehta argues this is the most compounding management habit — root-cause feedback, delivered consistently over time, changes how people operate at a fundamental level.

Connections