Revenue cascade map

A revenue cascade map records the one hand-off a revenue Hoshin plan depends on and nothing else in this catalogue tracks: whether the plan's annual objectives actually became real, owned work inside a specific pod or function. The X-Matrix sets the plan; catchball is the negotiation that produces it; a cascade map is the separate, later question of what happened after — did Outbound, RevOps, or Customer Success actually take the objective on, and is that commitment real or just a name in a deck. It is not a KPI tree: a KPI tree breaks one goal into the driver metrics that move it inside a single function; a cascade map tracks which function owns which objective, across the whole plan, and says nothing about the metrics that prove any of them are moving.

Parent plan objectives

Name the parent revenue X-Matrix and describe its real annual objectives — a first-pass list gets drafted from that, for you to correct against the plan's actual objectives and targets.

Cascade units

The pods or functions this plan needs to cascade to — drafted from your description.

Cascade links

Only enter a link where a pod or function has actually proposed or committed to carrying a parent objective forward as its own, with a local objective that's genuinely more specific than the parent one — a real hand-off, never the parent text copied down.

Coverage

Computed for you from your parent objectives, units, and links — nothing to enter here.

Narrative

Drafted from the cascade actually built.

Next steps

What will you do about a dark objective or an unloaded function, ranked by impact and effort, owned and dated.

The example below cascades Beacon Analytics' own FY2027 revenue Hoshin Kanri (the revenue Hoshin Kanri worked example) to its commercial functions: two of the three annual objectives have a real, committed owner — the Outbound Sales Pod and RevOps — while the expansion-motion objective is still only proposed to Customer Success, honestly left uncommitted rather than marked done to round the numbers up.

• Marking a link 'committed' when it's really still just an assignment in a slide.

  A function that was told to own an objective, but never actually agreed to it, hasn't really taken it on — the whole point of tracking 'proposed' separately is catching this before the year ends and nobody delivered.

• Copying the parent objective's text down as the local objective instead of making it genuinely more specific.

  A cascade that doesn't get more specific at each level isn't actually cascading — it's relabeling. The local objective should say exactly what this function is going to do, not restate the parent's aspiration.

• Building the cascade once at the annual kickoff and never updating it as proposals turn into commitments or quietly fall through.

  Same living-document discipline as the X-Matrix itself — a cascade map that was accurate in January and never touched again is stale by the first business review.