The FieldBook: A Strategist's Handbook (Part 2)

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
• Phase 2: Financial Architecture
• Phase 3: Innovation Steering Logic
• Phase 4: Pilot-to-Production Pipeline
• Phase 5: Transition & Debt Control

- - -

Phase 1: Portfolio Health & Rationalization

P01.01 Section: Quickstart

P01.01.01 Objective

Identify “Toxic Waste” Assets and Processes that are hemorrhaging the budget and “Company Jewels” that are architecting the organization’s future.

P01.02 Why

Every organization suffers from "Strategic Inertia" - the dangerous tendency to keep funding assets because they have always existed or executing processes because “that’s how we’ve always been done it”.

Without a cold, objective audit, you cannot:

• Free non-productive resources into more productive activities that drive growth rather than just sustaining existence;

• Identify processual dead-ends where processes or assets exist without contributing to a relevant strategic outcome;

• Spot obsolete or vulnerable assets before they cause a “black swan” event;

• Redirect the organization’s talent from “maintaining the decaying“ to “strengthening the hull” and “architecting the disruptive”;

The ultimate aim is to make value chains leaner and more resilient to unlock the true value of your resources into activities that keep the organization relevant and promote innovation and growth.

P01.03 Expected Outcomes:

• Rationalization List: An operational classification of every asset and process;

• Freed Resources: A “bucket” of talent, budget and attention ready for reallocation to foundational activities;

• Health Transparency: A map of organizational fragilities – knowing exactly where to trim the fat and where to bridge structural gaps;

P01.04 Execution Steps

Evaluate your map through two lenses: Utility (business value) and Stability (technical health).

1. Audit the Added-Value (scoring)

Apply a cold metric to every asset/process in your inventory:

Business Utility Score (BUS) - Functional Fit

Assess the effectiveness of the asset/process in supporting Business Capabilities. Evaluate Criticality, Usage Volume, Operational Reach and Strategic Alignment on a 1 (low) to 5 (high) scale.
Calculate BUS as the average of these measures.

How much does this actually matter to the customer or the core mission?

BUS Scale:

• 5 - Key differentiator: Handles several primary value chains, directly drives market advantage;
• 4 - Essential: Handles several primary value chains without direct differentiation;
• 3 - Tactical: Handles one primary chain.
• 2 - Support: Handles several secondary or support value chains.
• 1 - Commodity: Handles a single support value chain

Technical Debt Score (TDS) - Technical Fit

Assess the technical suitability of the asset to provide effective and efficient support to Business Capabilities. Evaluate Maintenance Intensity, End-of-Life (EoL) / Technical Obsolescence, Functional Adequacy and Security Risk on a 1 (low) to 5 (high) scale. Calculate TDS as the average of these measures.

How much is this asset/process "rotting"?

TDS Scale:

• 5 - Critical: No vendor support, weekly downtimes, recurrent failures.
• 4 - High: Minimum support, monthly disruptions, significant user complaints.
• 3 - Medium: Extended support, planned maintenance only, some friction.
• 2 - Low: Fully Supported, little to no disruption, punctual issues.
• 1 - Healthy: Fully Optimized, zero disruption, no issues from users.

2. Structure and consolidate into a Decision Matrix

Plot your findings into a TIME Matrix (Tolerate, Invest, Migrate, Eliminate) using BUS and TDS as standardized definitions for “Functional Fit” and “Technical Fit”:

Preliminary note: If your evaluation hits the crosshair of the matrix, there is one special zone in the matrix - the SME Judgement Zone”. This classification is done prior to the placement on the other quadrants:

SME Judgement Zone

• BUS = 3 & TDS = 3

After identifying the special zone, plot the rest of the assets and processes in the following quadrants:

Company Jewels

• 3 <= BUS <= 5 (High Business Value)
• 1 <= TDS <= 3 (Low Technical Debt)

Fragile Giants

• 3 <= BUS <= 5 (High Business Value)
• 3 <= TDS <= 5 (High Technical Debt)

Utilities

• 1 <= BUS <= 3 (Low Business Value)
• 1 <= TDS <= 3 (Low Technical Debt)

Toxic Waste

• 1 <= BUS <= 3 (Low Business Value)
• 3 <= TDS <= 5 (High Technical Debt)

3. Analyze and Plan

Define a baseline action and a roadmap for each specific quadrant.

Company Jewels

• Definition: Core differentiators. High debt tolerance.
• Action: Protect / Invest
• Directives:
• Analyze the supportability windows of the underlying technologies. If the window is less than 18 months, plan a preemptive technology upgrade;
• Analyze the business processes journeys for incremental improvements in the flow or performance;
• Implement Observability Capabilities. Gather telemetry on journey and value chain execution to find opportunities for continuous optimization.

Fragile Giants

• Definition: High value, high risk. The "Ticking Time Bomb".
• Action: (Urgently) Migrate
• Directives:
• Estimate the total cost of inaction (i.e. systemic failure risk); 
• Compare a technical version upgrade against a full market replacement – define a business case for each option.
• Decide on the most effective scenario for each asset and plan the migration;

Utilities

• Definition: Not critical to the core business. Evaluate transition to "As-a-Service".
• Action: Tolerate / Lease / Externalize
• Directives:
• Identify “As-a-Service” market solutions. If a reliable commodity market exists, stop building and maintaining it internally;
• Define minimum viable service level required (SLAs) for each “Product/Service delivered” based on Phase 0 value chains;
• Create a business case for each service and decide whether to Tolerate, Lease or Externalize;
• Define a revision window for the assets to Tolerate (i.e. every 12 to 24 months re-evaluate market evolution);

Pro Tips:

• Target Volatility: Focus externalization on services with highly volatile demand. Maintaining fixed internal capacity for peak loads is expensive, external elasticity is highly more efficient; 

• Contractual Awareness: Be aware of minimum/maximum service consumption, limits, response times and hidden fixed fees;

• Market Benchmarking: Locate credible benchmarks for cost and performance to ensure the external service brings clear, quantifiable gains over your AS-IS costs and matches market rates;

• SLA Definition: Consider engaging professional expert external consultancy  to assist with SLA definition as it may be challenging and it is key to success;

• Avoid Dogmatism: Do not be a purist, don’t externalize just because. If externalization lacks clear cost and risk advantages (i.e. the business case is negative), it’s perfectly acceptable to “Tolerate” it temporarily until a next evaluation cycle;

• Lifecycle Loop: Every externalized asset or process must still be classified as an "Utility" and subjected to the exact same recurrent revision cycle;

• Assymetry Protection: To protect the organization overexposure to external services and vendor lock-in, every revision cycle (including “Utilities” already externalized) must include an internalization cost/benefit comparison within the business case;

Toxic Waste

• Definition: No value, high cost. Pull the plug.
• Action: (Ruthless) Eliminate
• Directives:
• Evaluate the impact on the value chains of eliminating these assets;
• If minimal to no impact, just discontinue them immediately - the organization will cope with a very small disrruption;
• If a residual activity is needed for the functioning of the value chain, consolidate it into an existing process in other asset outside "Toxic Waste", preferably a "Company Jewel" or "Utility" (because of the short time-to-market those low technical debt assets allow) and then kill the legacy asset or process;

Pro Tips

• Fight the Habit: Do not overestimate the low value of an asset. Stakeholders will defend “Toxic Waste” out of habit. Keep the objectiveness. Keep being analytical. Keep the focus on “cutting the fat”;

• Verify Dependencies: Analyze the impact carefully before pulling the plug. Sometimes a small, cheap and simple component is the reason the whole machine runs. Do not discontinue without running an explicit dependency trace;

SME Judgement

• Definition: The middle axis. It is not objectively clear the classification of the asset.
• Action: Qualitative Tie-Breaker.
• Directives:
• Assets landing exactly in the centre require a qualitative analysis. Business and Technology Leaders must decide: Is this a Utility that can be outsourced, or a "Fragile Giant" that must be modernized to protect a core asset?

Pro-Tips:

• Be prepared for structural deadlock and to collect different and antagonic perspectives;

• The transformation Leader must be empowered to be the tie-breaker and force a decision between the tech and business leaders. Tech Leaders usually want to modernize (to lower tech debt) and Business Leaders normally want to tolerate or outsource (to save short-term cash)

Final Pro Tips: 

• The lindy Effect: The fallacy that states that "if it has worked for the past 20 years, it will work for another 20" - unless an asset is a unique trademark of your brand, its age is likely a liability (Technical Debt), not an asset;

• Kill your Darlings: Detach emotionally. It doesn't matter who built the process or how much it cost in 2015 - sunk costs are irrelevant to future survival;

• Hunt pounds, not Pennies: If decommissioning an asset saves less than the hourly rate of the person doing the work, ignore it for now. Focus your architectural energy on the heavy freight;

P01.05 Examples

• Banking
• Resource: Manual KYC ("Know Your Customer") verification.
• TDS: (5) High error rate, massive manual labor, slow throughput.
• BUS: (3) Non-negotiable legal requirement.
• Verdict: Fragile Giant
• Action: Migrate
• Analysis: Automate the support function to remove the human "debt" while maintaining compliance flow.

• Cross-Sector
• Resource: On premises Employee Payroll Processing Software
• TDS: (2) Standard Commercial Off-The-Shelf (COTS) product that supported and updated, with little disruption to the few users.
• BUS: (2) Handles a support value chain with no differentiation value
• Verdict: Utilities
• Action: Externalize
• Analysis: Transition to an external payroll service or a to cloud-based Software as a Service (SaaS) solution to free internal maintenance resources

• Logistics
• Resource: Custom-built route optimization solution
• TDS: (3) It executes as designed but requires some specialized support to integrate with modern API-based tacking tools. Users are mostly happy with occasional feedback on the integration speed.
• BUS: (3) Supports a primary value chain. Provides some differentiation but is no longer “cutting edge”.
• Verdict: SME Judgement
• Action: To be decided
• Analysis: Business and Technology leaders should decide if it is a Fragile Giant with potential differentiating factors to be modernized or if there is no business advantage to be had and it is an utility to be externalized or leased

P1.02 Section Fundamentals: 

P1.02.01 OKRs

• O: Maximize Portfolio ROI.
• KR1: Achieve 10% reduction in overall portfolio TCO within 12 months.
• KR2: Deliver a decomission roadmap for 100% of “Fragile Giants” within 1 months.
• KR3: Complete the decommission roadmaps for 100% of “Toxic Waste” within 12 months.
• KR4: Deliver an obsolescence resolution plan for 100% of "Fragile Giants" within 3 months.
• KR5: Complete the transition evaluation for 100% of “Utilities“ within 6 months.

P1.02.02 Artifacts

• Application Rationalization Report: Obsolescence roadmap, Decommission roadmap and Transition Evaluation supported by clear business cases;
• TIME Matrix

P1.02.03 Frameworks

• Gartner’s TIME Model (Tolerate, Invest, Migrate, Eliminate);
• Ward Cunningham’s Technical Debt Concept;
• The Lindy Effect life expectancy theory.

P1.02.04 Responsible

• Enterprise Architect

- - -

Phase 2: 70/20/10 Financial Architecture

P2.01 Section: Quickstart

P2.01.01 Objective

Enforce unyielding investment lanes to prevent operational "gravity" from cannibalizing the budget meant for the organization's future.

P2.01.02 Why

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 Optimization Engine

Part II of The Fieldbook – A Strategist’s Handbook moves us out of pure observation and throws us directly into tactical warfare against corporate bloat and strategic stagnation. We have deployed the maps built in Phase 0 to execute surgical interventions across the entire operational ecosystem:

• Surgical Portfolio Analysis: Through Phase 1, we ended the subjectivity. By analyzing capabilities through the lenses of Business Utility (BUS) and Technical Debt (TDS), we mapped exactly where the organization core strengths reside (Company Jewels) and where the systemic operational liabilities are hiding (Fragile Giants and Toxic Waste).
• Airtight Allocation Boundaries: Through Phase 2, we established strict structural financial guardrails. We converted the organization’s TCO into a defensive shield that caps legacy running costs at 70%, forces a dedicated 20% on growth and modernization by tackling technical debt and decommission of obsolete assets, and isolates a pure 10% for high-conviction innovation bets.

The combination of Phase 1 and Phase 2 changes enterprise architecture from an internal consulting group into a highly objective strategy execution engine. We have pruned the dead weight, stabilized structural liabilities and engineered a financial architecture built for the organization agile performance.

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.

In Part 3, we will enter the execution engine of innovation, ensuring that our ring-fenced 20%+10% transformations are structured with the same cold, geometric rigor as our core architecture. We will cover:

• Phase 3 - Innovation Steering Logic: Establishing the rules to govern exploratory investments without risking operational collapse.

• Phase 4 - Pilot-to-Production Pipeline: Bridging the vision with the execution and operation, turning high-conviction prototypes into highly scalable business capabilities.

The fat has been trimmed. 

The financial engine is fueled. 

We are walking the path.

Let’s set the pace.

- - -

"The Fieldbook: A Strategist's Handbook":

• Part 1
• Part 2 - You are here
• Part 3

#TheFieldBook #AStrategistsHandbook