Revenue Hoshin Kanri — X-Matrix

A revenue Hoshin Kanri is the same X-Matrix — long-term objectives, this year's annual objectives, the strategies that move them, the metrics that prove it, catchball negotiating all of it — pointed at revenue direction instead of a factory floor. The lean connection matters here specifically because Hoshin closes the loop the other two commercial artifacts open: a deal A3 finds a specific root cause, a funnel value stream map finds a specific bottleneck, and a revenue Hoshin is where those findings actually become this year's committed strategies with owners and targets, not just conclusions in a slide nobody revisits. Master-plan §7.2's operating-system thesis — direction, then the gap, then the fix, with results feeding the next planning cycle — applies to a revenue org exactly as it applies to a shop floor.

True North

One or two sentences: why does this revenue plan exist beyond hitting a number? Every objective on the page should trace back to it — if you can't draw that line for an objective, it doesn't belong here.

Long-term breakthrough objectives

Where does revenue need to be in three to five years? Give each one a checkable target — "grow net revenue retention from 98% to 115%" is checkable; "become customers' most trusted partner" isn't.

Annual objectives

What has to be true by year-end to be on track for the long-term objectives? This is where a deal A3's root cause or a funnel value stream map's bottleneck finding directly becomes this year's committed target — not a separate conversation from the RCA that found the gap.

Catchball

The record of who proposed each annual objective, how the people who'd deliver it pushed back, and what was actually agreed. An objective never negotiated with frontline reps or RevOps is a wish, not a commitment — and it usually means the target didn't account for how long a fix actually takes to roll out and take effect.

Strategies

The initiatives that will actually move the annual objectives — often literally the countermeasures from a deal A3 or funnel value stream map, promoted from a bounded fix to a resourced strategy with an owner. A strategy with no owner doesn't happen.

Metrics

What you'll track to know the strategies are working, each with a target. Win rate, stage wait time, and retention are the natural revenue metrics here — pull them from the same CRM data a deal A3 or funnel map would use, not a separate estimate.

X-Matrix correlations

Which long-term objectives each annual objective supports, which metrics track each objective, which strategies move each metric, which strategies support which long-term objectives. Mark primary, secondary, or weak, and leave a pair blank when there's genuinely no connection — a fully-shaded grid means the correlations weren't actually thought through.

The example below is a full worked revenue X-Matrix: long-term objectives (net revenue retention, an outbound growth channel) and annual objectives with real targets — including two that trace directly to the deal A3 and funnel value stream map worked examples elsewhere in this catalogue — a catchball record showing the negotiation behind those targets, strategies with named owners, metrics with targets, and a correlation grid that's honest about which connections are strong and which are weak.

• Objectives read like a mission statement instead of a target — "delight our customers" instead of a number.

  If two people could reasonably disagree about whether it was achieved, it isn't specific enough to plan against. "Grow NRR from 98% to 115%" is checkable; "delight our customers" isn't.

• Annual objectives are set without reference to an actual root-cause finding — a target picked because it sounds ambitious, not because a deal A3 or funnel map showed where the real gap is.

  A revenue Hoshin disconnected from real diagnostic work is a forecast wrapped in a planning document, not a plan — it commits to an outcome without committing to the specific mechanism that would produce it.

• The correlation matrix is fully shaded — every objective connects to every strategy.

  Same failure mode as the canonical X-Matrix: a matrix that dense means the correlations weren't actually thought through. Which connections are weak or absent is the useful information.

• Catchball is skipped and the target goes straight from an executive offsite to the matrix.

  The reps and RevOps staff who'd actually have to hit the number never got to pressure-test whether the rollout timeline makes it achievable — exactly what happened when 35% was proposed before catchball corrected it to 30% in the worked example.

• A strategy has no owner, or a metric has no target.

  An unowned strategy or untargeted metric is a line on a page, not a commitment — this is what the specificity check exists to catch.