The FieldBook: A Strategist's Handbook - Phase 2

Without a strict, architectural constraint on corporate funding, the urgency of the present will always consume the capital meant for future transformation. Legacy maintenance behaves like a gas: it expands naturally to fill every cubic centimeter of available capital. If left untamed, the baseline cost of running the business will steadily asphyxiate the resources required for evolution.

The "Run" of the business acts like gravity, you need an engineered financial engine to achieve escape velocity. In highly regulated sectors, “Regulatory Gravity” is one of the most common causes of corporate stagnation. When compliance development blindly consumes 100% of discretionary spend, the organization ceases to be an innovative business and becomes a stagnant regulated utility with no competitive edge.

Without a financial framework, you cannot:

Cap the Bleeding: Put an absolute and rational ceiling on what the organization spends just to keep the lights on.

Anchor Spend to Value: Ensure every euro spent directly correlates to either baseline survival, tactical acceleration or structural growth.

Create Predictable Runway: Provide your innovation steering logic with a dedicated, ring-fenced pool of capital completely insulated from operational emergencies.

Its purpose is to weaponize the “fully burdened” TCO built in Phase 0, transforming financial data into an active strategic governor.

P2.01.03 Expected Outcomes

Portfolio Guardrails: Hard structural thresholds to block any proposals that might violate allocation rations.

Cruise Speed Efficiency: Systematic trajectory to achieve and maintain a target baseline running cost, driven by the rationalization actions of Phase 1.

Ring Fenced Capital Reservoirs: Clear and isolated funding streams for both operational evolution and exploratory incursions.

P2.01.04 Execution Steps

1. Define Capital Expenditure and Investment Streams

Segment all enterprise capability expenditures into 3 core investment lanes:

Core Operations (Run - OpEx)

Scope:

The base cost required to execute current operations safely and compliant.
Direct costs of running the “Company Jewels”, “Utilities”, “Fragile Giants” and still existing “Toxic Waste”.
Legal and regulatory mandatory developments.

Target: maximum 70%

Growth, Adaptation and Scaling (Change the Business - CapEx)

Scope:

Refining and scaling proven differentiators through incremental evolution of “Company Jewels”;
Modernizing “Fragile Giants” reducing obsolescence and cleaning technical debt transitioning them into “Company Jewels”
Transformation programs of shifting “Utilities” into elastic SaaS or external services.
Decommission initiatives of “Toxic Waste” assets and processes;

Target: minimum 20%

Disruptive Evolution (Transform the Business – OpEx and/or CapEx)

Scope:

High-risk capital completely unlinked from current operational dependencies.
Focus entirely on prototyping new business capabilities for the future market.

Target: minimum 10%

Pro-Tips:

Do not allocate the budget by department. Create cost and profit centers by Business Capability and allocate funds explicitly to the cost center of each Business Capability;

Register the first baseline you calculate and recalculate it recurrently (monthly or quarterly) and in every major milestone (e.g. when “Toxic Waste” is decommissioned or when a “Fragile Giant” transitions into “Company Jewels”) in order to see trendlines and progress of your actions to feed your prioritization process;

The Core Operations 70% budget allocation must be treated as a ceiling to be actively compressed, not an entitlement to be preserved – allocate immediately any “saved” budget into an activity on the Growth or Evolution that you have in backlog.

2. Enforce and Calibrate Allocation Gates:

Organizations normally set a fixed annual budget for RUN and BUILD and leave a cushion for unplanned activities. Even with a strict distribution of the budget, the unexpected nature of the unplanned procurement de-calibrates the budget split. To counter this, every intervention must be carefully and opportunistically governed.

Enforce at Planning: Lock in the rigid 70/20/10 allocations during the annual budgeting cycle;

Filter Unplanned Demands: For any unplanned initiative, check If it is an absolute, non-negotiable regulatory requirement. If it is not, evaluate its strategic value and criticality. If it lacks immediate, high impact risk or reward, reject it and push it to next year’s budget backlog;

The Regulatory Trojan Horse: If the unplanned mandate is a regulatory requirement, it will to push the Core Operations budget past the 70% ceiling.

If the underlying asset targeted by the regulation is a Fragile Giant, apply a Trojan Horse strategy: Use the compliance mandate as a catalyst to completely refactor, decouple or migrate that legacy system into a clean infrastructure;

Increase the budget so that the compliance core implementation represents a maximum of 70% while 30% of the budget is for lowering or eliminating technical debt;

This budget increase should be covered by the unplanned activities cushion or by re-prioritizing and postponing the lowest priority initiative in the 20% Growth backlog;

Pro tips:

Watch out for “innovation washing” and scrutinize in detail the “Disruptive Innovation” initiatives plan. Sometimes teams use that label for standard platform upgrades under the banner of “disruptive tech” to access the protected 10% ring-fenced fund;

As soon as an initiative that aims at reducing the Core Operation cost is concluded, immediately transfer the proportional remaining RUN budget of that asset into the 20% Growth budget to activate the nest transformation backlog item that has not cut the chase for the current year before it is reabsorbed by operational overhead.

P02.01.05 Examples

Telecom

70% Run: Maintaining the core cellular network infrastructure and legacy billing system engine
20% Change: Migrating customer care support channels to an automated, self-service digital interface to deflate future run costs
10% Transform: Prototyping an experimental decentralized edge-computing network slice for private enterprise infrastructure

Logistics

70% Run: Fleet management maintenance, driver payroll tracking systems, and warehouse facility operations
20% Change: Upgrading the custom route optimization engine from an obsolete integration stack to modern APIs to lower technical debt
10% Transform: Piloting autonomous drone-delivery lockers in a highly dense metropolitan test-bed

P02.02 Section Fundamentals

P02.02.01 OKRs

O: Structural Rebalancing of the Organizational P&L.
KR1: Reduce the absolute cost of Core Operations (70% bucket) by 10% through automation and legacy decommissioning within 12 months.
KR2: Consume 100% of the absolute value of the ring-fenced 10% Disruptive Innovation annual budget and at least 10% of the actual annual investment after including unplanned initiatives.
KR3: Consume 100% of captured financial savings from the decommissioned assets by executing additional items of the Growth portfolio backlog of by financing opportunistic technical debt elimination.

P02.02.02 Artifacts

Detailed Allocation Ledger: The inventory tracing every euro to its exact allocation layer (70/20/10) detailed by Business Capability and by asset.
Capital Allocation Guardrail: An explicit policy document defining the governance criteria for the funding pools allocation and unplanned activities governance rules.

P02.02.03 Frameworks

Three Horizons of Growth (McKinsey): Structural timeline and corporate intent categorization.
Technology Business Management (TBM): Translating standard corporate ledger entries directly into capability-based investment layers.
Lean Budgeting (SAFe / Agile Portfolio Management): Dynamic funding allocation, moving away from rigid, multi-year fixed budgeting cycles.

P02.02.04 Profiles and Roles

CFO / Portfolio Responsible: Enforces the structural budget limits and protects the ring-fenced funding pools;
Enterprise Architect: Identifies technical blockages inflating the baseline and provides the technical validation for the 20% modernization tracks; Keeps the technical debt catalog and promotes opportunistic “Trojan Horses” to be put in place;
Chief Innovation Officer / Product Strategy Lead: Deploys the 10% exploratory budget against future-state bets.

Conclusion: The Financial Shield

Through Phase 2, The Fieldbook establishes a defensive, unyielding financial architecture designed to fight corporate bloat and break the cycle of strategic stagnation. We have weaponized the organization's fully burdened TCO, converting raw financial data into an active strategic governor.

By capping legacy run-rate costs at a strict 70% compression ceiling, ring-fencing a 20% allocation for adaptive evolution, and isolating a pure 10% stream for exploratory incursions, we ensure the urgency of the present can no longer cannibalize the capital required for tomorrow.

With programmatic governance mechanisms like the Regulatory Trojan Horse and automated efficiency dividends, we ensure that every euro spent is anchored strictly to value. The financial engine is no longer a passive spreadsheet managed by accounting; it is the active governor of enterprise transformation.

Moving Forward: Steering Innovation

With our portfolio thoroughly rationalized and our financial guardrails set, The Fieldbook shifts its focus from structural optimization to market velocity.

Securing the 20% and 10% capital reservoirs is a critical financial victory, but deploying that capital demands equal geometric rigor. Next, we will enter the execution engine of innovation to ensure these transformation tracks don't collapse into unstructured chaos.

We will unpack Phase 3: Innovation Steering Logic to govern exploratory investments without risking operational friction, followed by Phase 4: Pilot-to-Production Pipeline to successfully bridge the corporate valley of death, turning high-conviction prototypes into highly scalable business capabilities.

The fat has been trimmed.

The financial engine is fueled.

Let’s set the pace.

- - -

The FieldBook: A Strategist's Handbook

This article is part of "The FieldBook" series. To know more about it, read this.

The Fieldbook is lean and mean: pure signal, no noise.

• Phase 0: Readiness & Data Foundation (Prerequisites)

• Phase 1: Portfolio Health & Rationalization

• (this page) Phase 2: Financial Architecture

• Phase 3: Innovation Steering Logic
• Phase 4: Pilot-to-Production Pipeline
• Phase 5: Transition & Debt Control

• Wrap-up & Conclusion

#TheFieldBook #AStrategistsHandbook

Search This Blog

Hugo Vicente