--- name: revenue-hoshin-kanri description: "The same X-Matrix discipline connecting long-term revenue direction to this year's targets, the strategies that will move them, and the metrics that prove it — with catchball forcing real negotiated numbers instead of a target set once at an offsite and never pressure-tested. Use when: You have real organisational authority over revenue strategy — you can commit budget and headcount, and hold people accountable to what comes out of this. There's a genuine multi-year revenue direction to connect this year's work to — a retention target, a channel mix shift — not just a list of this quarter's initiatives looking for a rationale. Not for: You're an individual contributor or single-team manager without authority to commit cross-functional resources — Hoshin cascades through an organisation; use a deal A3 for a bounded problem you can act on yourself. The \"long-term objectives\" are really just this year's initiatives relabelled, with no real 3-5 year revenue direction underneath them." --- # Revenue Hoshin Kanri — X-Matrix The same X-Matrix discipline connecting long-term revenue direction to this year's targets, the strategies that will move them, and the metrics that prove it — with catchball forcing real negotiated numbers instead of a target set once at an offsite and never pressure-tested. Family: Hoshin Kanri · Format: .xlsx · Domain: commercial ## What it is 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. The operating loop behind every kata here — 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. ## When to use it Use it when: - You have real organisational authority over revenue strategy — you can commit budget and headcount, and hold people accountable to what comes out of this. - There's a genuine multi-year revenue direction to connect this year's work to — a retention target, a channel mix shift — not just a list of this quarter's initiatives looking for a rationale. - You're willing to have the plan pushed back on by the people who'd have to deliver it. A revenue plan padded with aspirational targets nobody pressure-tested is worse than no plan. Not when: - You're an individual contributor or single-team manager without authority to commit cross-functional resources — Hoshin cascades through an organisation; use a deal A3 for a bounded problem you can act on yourself. - The "long-term objectives" are really just this year's initiatives relabelled, with no real 3-5 year revenue direction underneath them. - You want to skip catchball and go straight from an executive offsite to a finished matrix — it won't survive contact with the first budget conversation. ## How to fill it in - **trueNorth** — 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. - **longTermObjectives** — 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. - **annualObjectives** — 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. - **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. ## What good looks like 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. Full worked example, on-screen and as a downloadable .xlsx: https://www.katafacts.com/katas/revenue-hoshin-kanri ## Common mistakes - **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. ## What it connects to Upstream: - **Deal A3 — win-rate root cause analysis** (`deal-a3`) — A deal A3's root cause is exactly the kind of specific finding an annual objective should trace to — the worked example here sets its win-rate target directly from the deal A3's finding, not independently of it. - **Sales funnel value stream map** (`sales-funnel-map`) — A funnel map's capacity constraint or largest wait contributor is the other natural input to an annual objective — this worked example's proposal-wait target comes straight from the funnel map's finding. Downstream: - **Deal A3 — win-rate root cause analysis** (`deal-a3`) — When a strategy on the X-Matrix isn't moving its metric, a deal A3 is the right tool to find out why for a specific segment — Hoshin sets the direction, the deal A3 closes the specific gap. - **Pipeline management board** (`pipeline-management-board`) — Tracks the metrics named here cadence by cadence — the X-Matrix sets what to watch; the pipeline board is where the team actually watches it between business reviews. - **Revenue cascade map** (`revenue-cascade-map`) — Shows how this X-Matrix's annual objectives become real, committed work inside a specific pod or function — the mechanism that makes this plan cascade through the commercial org rather than living at the leadership level. ## Where AI helps Judgement — stays with you: - Committing to the actual objectives, targets, and owners - Deciding what a catchball response actually resolves to - Judging whether a strategy is really worth the resources it would take Analysis — AI helps: - Challenging vague objectives, strategies, and metrics that sound specific but aren't checkable - Proposing a first-pass correlation matrix from the stated objectives, strategies, and metrics for the practitioner to correct - Flagging an objective that doesn't actually trace back to a real diagnostic finding (a deal A3's root cause, a funnel map's bottleneck) or to the stated true north Drudgery — automated: - Formatting the X-Matrix — rotated axis labels, correlation symbols at the right intersections, merged cells - Keeping the correlation grid's row/column references in sync as objectives and strategies are edited - Exporting to xlsx in the house format --- Revenue Hoshin Kanri — X-Matrix is licensed [CC BY 4.0](https://creativecommons.org/licenses/by/4.0/). Attribution: Katafacts (katafacts.com). ## Using this skill Apply this method as part of whatever broader task, instructions, or deliverable you're already working on -- it's a method to use, not a standalone conversation to start. There is no generation tool for this catalogue yet, so draft the artifact's actual content yourself, following the fields above, the same way a person filling this out by hand would. The canonical guide page and a downloadable worked example (.xlsx) are at https://www.katafacts.com/katas/revenue-hoshin-kanri.