Horizon Budget Allocation¶
Resource-allocation method — instantiates Three-Horizon Transition Mapping
Sets and defends how much funding, people, attention, and risk tolerance each horizon receives, including protected floors for transition work and a ring-fenced line for legacy support.
Horizon Budget Allocation decides the numbers. Where classification says which horizon a project belongs to, this method says how much money, headcount, management attention, and risk appetite each horizon actually gets — and then defends that split against the quarter-by-quarter gravity that pulls everything back into the present. Its defining move is the protected floor: because Horizon Two and Horizon Three are always the easiest lines to raid when the current system needs cash, allocation only bites if some share is ring-fenced and hard to divert. It also does the opposite job most portfolios forget: it budgets an explicit legacy-support line so the current system is neither starved into failure nor allowed to consume everything. It sets the target distribution and enforces it; it does not judge whether the split is wise (that is a review) or label the projects (that is the buckets).
Example¶
A metropolitan transit agency runs on a fixed subsidy and fare revenue. Its default budgeting is entirely Horizon One: keep the buses and trains running, patch the aging signalling, cover pension and maintenance. Every year, a "mobility innovation" line — on-demand microtransit pilots, an open fare-payment API, a future mobility-as-a-service platform — is proposed, approved, and then quietly consumed by mid-year operating shortfalls.
Horizon Budget Allocation changes the mechanics. Leadership sets an explicit split: 82% to Horizon One operations, 12% to a protected Horizon Two floor that cannot be swept to cover operating gaps without board sign-off, and 6% to Horizon Three options. Crucially, the H1 share is itself split into a defined legacy-support line — a committed but capped budget for keeping the current fleet and signalling safe and reliable during the transition — so "keep the trains running" can no longer expand without limit to eat the pilots. The microtransit pilot survives its first bad quarter for the first time, because the money was fenced before the pressure arrived, not after.
How it works¶
- Set a target split across horizons. Express the intended distribution of funding, people, and attention as explicit shares (e.g., 82/12/6), tied to strategic intent rather than last year's baseline.
- Ring-fence the fragile horizons. Put protected floors under H2 and H3 with a named, deliberately awkward process required to breach them — the friction is the point.
- Budget the legacy line explicitly. Give Horizon One a defined support-and-maintenance envelope: enough to stay safe and reliable, capped so it cannot silently absorb the transition budget.
- Release against evidence, then rebalance. Stage the fragile-horizon money so it flows as milestones are met, and re-set the split on a slow cadence as the transition matures.
Tuning parameters¶
- The split itself — how aggressively toward the future. A bold H2/H3 share accelerates transition but raises near-term risk; a conservative one protects continuity but can strand the future. Classic starting stances like a 70/20/10 rule exist as anchors, not laws.[n1]
- Floor hardness — how difficult it is to divert protected money. Hard floors resist raiding but can trap funds in a failing bet; soft floors flex but leak under pressure.
- Legacy-line cap — how tightly the H1 support budget is bounded. Too tight and the current system degrades unsafely; too loose and it eats everything.
- Release gating — lump-sum versus milestone-staged. Staged release preserves option value and stops runaway bets, at the cost of coordination overhead.
- Rebalance cadence — how often the split is re-set. Frequent resets track a fast transition but invite churn and short-termism.
When it helps, and when it misleads¶
Its strength is that it makes the exploration budget real and defended — the single thing most reliably raided when the present is under pressure — while refusing the opposite error of letting future enthusiasm starve the legacy system that still has to work. It converts strategic intent from a slogan into a number with a lock on it.
Its failure mode is allocation theater: a published split that everyone quietly overrides, so the numbers exist on a slide while the real money flows by habit. It can also over-protect a bad bet, keeping a hard floor under a Horizon Two experiment that the evidence has already killed — a floor is protection, not immortality. The guarding discipline is to pair the allocation with an honest signal or review that can lower a floor on evidence, and to audit actual spend against the declared split rather than trusting the plan. Allocation sets the numbers; something else must be allowed to tell it when they are wrong.
How it implements the components¶
Horizon Budget Allocation realizes the resource side of the archetype:
portfolio_balance_map— it sets and defends the target distribution of funding, talent, attention, and risk across the three horizons.legacy_system_support_plan— it budgets an explicit, capped maintenance-and-support envelope so the current system stays viable without consuming the transition.
It does not decide which horizon a project belongs to (horizon_role_classification — that's Core / Emerging / Future Investment Buckets) or supply the evidence that a floor should move (transition_signal — that's Transition Signal Dashboard).
Related¶
- Instantiates: Three-Horizon Transition Mapping — this method is the resource-allocation engine that turns horizon strategy into defended numbers.
- Consumes: Core / Emerging / Future Investment Buckets for the classification it allocates against, and Transition Signal Dashboard for the evidence that justifies moving a floor.
- Sibling mechanisms: Core / Emerging / Future Investment Buckets · Lifecycle Portfolio Review · Innovation Portfolio Review · Three Horizons Map · Strategic Transition Map
Editorial Notes¶
Form Classification¶
Form family: Decision, Gate & Allocation
Rationale: Horizon Budget Allocation operates as a case-specific gate, selection, routing, prioritization, or resource disposition because it sets and defends how much funding, people, attention, and risk tolerance each horizon receives, including protected floors for transition work and a ring-fenced line for legacy support
Independent corroboration: The frozen evidence defines Horizon Budget Allocation as 'Sets and defends how much funding, people, attention, and risk tolerance each horizon receives, including protected floors for transition work and a ring-fenced line for legacy support', so its operative form is Decision, Gate & Allocation.
Nearest alternative: Rule, Policy & Commitment — The mechanism makes a concrete portfolio resource allocation rather than only stating a general future allocation policy.
Review outcome: Independent reviewer agreement; medium confidence.
Origin Attribution¶
Primary origin: Organizational & Management Science
Origin pattern: Single lineage
Present-day reach: Multi-domain
Rationale: Allocating resources across core, adjacent, and speculative horizons is a strategic portfolio-management practice, typified by the 70/20/10 heuristic.
Related originating lineages:
- Innovation & Entrepreneurship — Innovation portfolio design materially shaped protection of exploratory bets from core-business metrics.
Review resolution: Both reviewers independently assign organizational_management as the primary originating domain, so that shared primary is retained. Alternate domains are the union of reviewer-identified formative or independently originating lineages; later application settings alone are excluded. The evidence describes one principal historical lineage. It has established independent use across several domains, but that does not make it domain-free. The encyclopedia entry makes that composition explicit.
Encyclopedia synthesis: The exact catalogued form synthesizes established practice rather than reproducing a single standard historical label.
Review outcome: Reconciled after independent review; high confidence.
Notes¶
Allocation and review are a pair, not the same thing. Innovation Portfolio Review checks whether the split has drifted into over-concentration and recommends a change; Horizon Budget Allocation is the method that sets and enforces the split in the first place, with floors and a legacy line. Keeping them separate lets a team defend the numbers between reviews without re-litigating the whole allocation every quarter.
[n1] The 70/20/10 heuristic — roughly seventy percent of resources on the core, twenty on adjacent/emerging work, ten on speculative future bets — is a widely cited starting stance for balancing a portfolio across horizons. It is an anchor to argue from, not a prescription. ↩