Skip to main content
Back to Curriculum
Module: Defining Products & PRDs•Lesson 77•40 min read

Innovation Accounting and Portfolio Management

Lesson 77: Innovation Accounting and Portfolio Management

Lesson 71 introduced the Strategy Cascade and the Three Horizons framework, establishing that a healthy bet portfolio deliberately spans core, adjacent, and transformational risk levels, and specifically warned against judging Horizon 3 bets by the same near-term metrics appropriate for Horizon 1. This lesson makes that warning concrete and actionable: what, exactly, should a company measure for a bet that is genuinely too early to show revenue, and how should a portfolio of many such bets, at different stages of maturity, actually be managed and reported on over time?

The natural organizational instinct is to measure every initiative using the same familiar metrics — revenue, user growth, profit margin — regardless of how early-stage or exploratory that initiative genuinely is. This instinct is understandable, since these are the metrics an organization already knows how to read and compare, but applying them uniformly to bets at fundamentally different stages of maturity produces a specific and damaging failure: promising early-stage bets get killed prematurely for failing to show revenue they were never realistically going to show yet, while genuinely failing bets can survive far too long if they happen to generate superficially impressive but ultimately meaningless activity metrics.

This lesson introduces the Portfolio Health Grid, this lesson's core mental model, to give you a structured way to track and evaluate a portfolio of bets at genuinely different stages of maturity, using stage-appropriate evidence rather than forcing every bet through the same evaluative lens regardless of how ready it actually is to produce that kind of evidence.

Learning Objectives

  1. 1

    Explain why applying uniform, revenue-based metrics across bets at different maturity stages produces systematically bad portfolio decisions.

  2. 2

    Apply the Portfolio Health Grid to evaluate a bet using evidence appropriate to its actual stage of maturity.

  3. 3

    Distinguish validated learning metrics from vanity metrics in the context of an early-stage bet.

  4. 4

    Identify the specific risk of both premature bet cancellation and prolonged bet survival caused by metric mismatch.

  5. 5

    Evaluate a portfolio of bets for whether each is being measured using stage-appropriate evidence.

This lesson assumes the Strategy Cascade, Three Horizons framework, and falsifiable-bet discipline from Lesson 71, since this lesson provides the measurement system that makes ongoing bet evaluation genuinely possible, and the Metric Provenance Chain from Lesson 64, since evaluating any bet's progress depends on the same underlying data trustworthiness that lesson established.

Why Uniform Metrics Fail Across Maturity Stages

A Horizon 1 bet — extending an established core business — can reasonably be judged against revenue, profit margin, and market share, because the underlying business model is proven and the relevant question is one of execution and optimization. A Horizon 3 bet — a genuinely new, exploratory initiative — cannot reasonably be judged against these same metrics in its earliest stages, not because the team is executing poorly, but because the entire premise of an early-stage exploratory bet is that the business model itself has not yet been validated, and demanding revenue-scale proof before that validation has occurred is asking the bet to demonstrate something it is structurally too early to demonstrate. Applying Horizon 1 metrics to a Horizon 3 bet doesn't produce a more rigorous evaluation; it produces a category error that reliably kills promising early bets before they've had a chance to answer the actual questions they were designed to test.

The Portfolio Health Grid

This lesson introduces the Portfolio Health Grid, plotting each bet in a portfolio along two axes: its Three Horizons classification from Lesson 71, and its actual stage of validated progress.

Process diagram showing flow: Validation Stages → Concept: hypothesis articulated, not yet tested → Prototype: minimal version tested with real users → Pilot: validated with a limited but real customer segment → Scale: validated model being deliberately scaled...

Validation Stages

Concept: hypothesis articulated, not yet tested

Prototype: minimal version tested with real users

Pilot: validated with a limited but real customer segment

Scale: validated model being deliberately scaled

Horizon 1
(Core)

Horizon 2
(Adjacent)

Horizon 3
(Transformational)

The Grid's core discipline is that the appropriate metric for any given bet depends on its position on both axes simultaneously — a Horizon 3 bet at the Concept stage should be evaluated on whether its core hypothesis has been clearly articulated and an initial test designed, not on revenue; a Horizon 3 bet that has progressed to Pilot stage should be evaluated on whether a real, if limited, customer segment shows the validated behavior the hypothesis predicted, a meaningfully different and more demanding bar than the Concept stage, but still not the same bar as a mature Horizon 1 business. Placing every bet somewhere on this Grid, rather than evaluating all bets against a single organizational-standard metric, is what makes stage-appropriate evaluation possible at all.

Validated Learning vs. Vanity Metrics

Validated learning, a concept from lean startup methodology, refers to evidence that a specific, falsifiable hypothesis about customer behavior or business viability has actually been tested and either confirmed or disconfirmed — directly connecting to the falsifiable Strategic Bet discipline from Lesson 71. Vanity metrics, by contrast, are numbers that look impressive and tend to always increase over time (total signups, cumulative downloads, total page views) without actually testing whether the bet's underlying hypothesis is correct. A Horizon 3 bet can generate an impressive-looking vanity metric — a large number of free trial signups, for instance — while providing no validated learning at all about whether those users would actually pay, retain, or behave in the way the bet's underlying hypothesis predicted. Innovation accounting, done well, insists on validated learning metrics specific to the bet's stated hypothesis, rather than accepting vanity metrics as a substitute simply because they are easier to produce and more comfortable to report.

The Two Failure Modes of Metric Mismatch

Metric mismatch produces two distinct, opposite failure modes. Premature cancellation occurs when a genuinely promising early-stage bet is killed because it hasn't yet produced Horizon 1-scale results it was never structurally positioned to produce this early — the specific risk Lesson 71 flagged for Horizon 3 bets judged by near-term metrics. Prolonged survival occurs when a genuinely failing bet continues to receive resources because it generates comfortable-looking vanity metrics that mask the absence of any real validated learning supporting its underlying hypothesis — a bet can look active and growing by activity metrics while its actual, falsifiable hypothesis has already been quietly disconfirmed by the available evidence, with no one having checked because the vanity metrics provided a comfortable alternative narrative.

Common Mistakes to Avoid

✕

Applying the same revenue and profit metrics to every bet in a portfolio, regardless of Horizon or validation stage

This produces the category error described in the Theory section, killing promising early bets and providing false comfort for others.

✕

Accepting vanity metrics as evidence of progress simply because they are readily available and always trending upward

Vanity metrics can create a comfortable illusion of progress while providing no actual validated learning about the bet's underlying hypothesis.

✕

Failing to explicitly place each bet on the Portfolio Health Grid, leaving its appropriate evaluation criteria ambiguous

Without an explicit stage classification, there is no principled basis for deciding what evidence should or shouldn't count as meaningful progress.

✕

Treating a bet's progression from one validation stage to the next as automatic rather than something that must be genuinely earned by evidence

A bet should not advance from Prototype to Pilot status, for instance, simply because time has passed, but because specific validated learning milestones have actually been met.

✕

Allowing organizational politics or sunk cost to substitute for validated learning evidence when deciding whether to continue or cancel a bet

A bet's continuation should be justified by genuine evidence at the appropriate stage, not by how much has already been invested or who championed it internally.

Ready to test your product judgment?

Take the interactive practice quiz for Lesson 77 and build your skill radar dashboard.