A crack exists wherever the economics visible inside a decision or action differ from the economics ultimately borne by the enterprise.
Value leaks through six recurring mechanisms
- The enterprise can underwrite the wrong proposition.
- Individually defensible commitments can produce an inferior combined result.
- The investment can change while the approved economics remain attached to it.
- Installed capability can fail to become operating value.
- New evidence can change the economics without changing the commitment.
- The resulting estate can make the next modernization decision more expensive.
These mechanisms form a loop.
The residual state created by one generation of modernization changes the opportunity set, constraints, costs, and options facing the next.
The economic object is larger than the project
Modernization begins as an economic promise.
The enterprise commits
- money
- attention
- expertise
- operating capacity
- organizational capacity
- time
- future flexibility
because it expects a better operating state later.
The return depends on the whole path.
The enterprise has to
- identify the right opportunity
- compare materially different alternatives
- allocate scarce resources among competing uses
- account for interactions across the portfolio
- carry the economics through implementation
- convert capability into operating change
- revise commitments when evidence changes
- leave a useful starting point for what follows
Project performance captures only part of that proposition.
- A project can finish on time and still represent a poor allocation of resources.
- A system can work correctly without producing the operating change assumed in its business case.
- An initiative can generate a positive return while displacing a better investment.
- A successful program can leave architecture, dependencies, contracts, or organizational fatigue that make later modernization more expensive.
The economic object is larger than the project.
Sophistication creates interfaces
Complex enterprises divide difficult problems because specialization works.
- Financeunderstands capital.
- Operationsunderstands process.
- Engineeringunderstands technical feasibility.
- Architectureunderstands systems and dependencies.
- Securityunderstands exposure.
- Procurementunderstands commercial terms.
- Business unitsunderstand local economics.
- External specialistscontribute capabilities the enterprise should not maintain internally.
Facts, assumptions, requirements, budgets, authority, technical decisions, operating constraints, and accountability have to cross them. Different participants optimize legitimate but different objectives.
- purchase economics
- security
- local speed
- standardization
- maintainability
- return on capital
- program delivery
- provider economics
- revenue
can all matter at once.
Sometimes the divergence begins at the level of meaning.
In one Talbot West engagement, a multinational telecommunications company had more than a dozen ERP environments inherited across acquired businesses. Core business concepts were represented differently across those environments. Before forecasting and capital analysis could operate on a common enterprise view, those definitions had to be reconciled and encoded into a shared data architecture.
See the project: Enterprise data unification across acquired businesses.Each local environment could function adequately while the enterprise-level representation remained incomplete.
- Commitment adds another force. An assumption that is cheap to challenge when proposed becomes harder to revisit after it acquires a budget, architecture, provider, integrations, staffing, executive sponsorship, and dependent programs.
- Time adds another. Reality continues changing while the enterprise executes the answer.
- Executive teams, portfolio councils, enterprise architecture, PMOs, transformation offices, procurement functions, centers of excellence, and provider ecosystems close real gaps.
- Each still operates within a mandate.
The enterprise therefore has to preserve the economics across boundaries that cannot simply be removed.
Six recurring forms of leakage
Underwriting error
The enterprise commits against the wrong or incomplete economic proposition.
Before implementation begins, the enterprise has to
- establish the desired outcome
- identify the relevant constraint
- construct the opportunity set
- compare materially different interventions
- decide which use of scarce resources deserves preference
The opportunity can narrow too early.
- An ERP modernization directs attention toward systems.
- An AI initiative directs attention toward a technology class.
- A cloud migration establishes a destination.
- Internal functions and external providers naturally see problems through the capabilities they possess.
- A precise analysis of an incomplete opportunity set can still produce a poor investment.
- A weaker path can consume scarce capacity, delay learning, displace a stronger alternative, or close options that were never properly evaluated.
In one Talbot West software engagement, a heavier AI architecture was tested against the behavior the product actually required. A simpler architecture produced the required behavior with less computational burden, complexity, and control risk.
See the project: Architectural engineering for AI in legacy software.Control specification
Keep the outcome, constraint, and proposed mechanism separate long enough to compare materially different alternatives and the resources each would displace.
Composition error
Individually defensible commitments produce an inferior combined result.
Large enterprises make modernization decisions across business units, functions, technologies, providers, geographies, and budget cycles.
The enterprise inherits the combination.
- Procurement can lower acquisition cost while engineering absorbs higher integration cost.
- A business unit can avoid a migration while the enterprise inherits another bespoke environment.
- A security control can reduce one exposure while creating enough operating friction to produce workarounds.
- Several providers can make sound recommendations that depend on incompatible architectures or future operating states.
Costs move between ledgers.
- One function records a saving while another absorbs integration work.
- Operations inherits manual effort.
- A later program absorbs switching cost.
Programs also compete for shared constraints such as
- architects
- engineers
- executive attention
- operating downtime
- data access
- organizational capacity for change
- One investment can enable another,
- make another unnecessary,
- consume a dependency,
- or foreclose a later path.
Project economics do not add cleanly into enterprise economics.
Control specification
Portfolio decisions have to account for shared constraints, dependencies, sequencing, integration burden, and the combined future created by separate commitments.
Translation drift
The approved economics remain while the investment changes.
A consequential commitment passes through many representations before it reaches operating reality.
- 01 →Strategic intent becomes requirements.
- 02 →Requirements become architecture.
- 03 →Architecture becomes program design.
- 04 →Program design becomes contracts, workstreams, backlogs, code, configuration, procedures, and operating behavior.
- A requirement survives after its reason disappears.
- A provisional constraint hardens into architecture.
- A procurement substitution changes an operating assumption.
- Scope is reduced while most of the cost remains.
- Delivery moves far enough that the benefit arrives outside the period in which it had the expected value.
Ownership changes at the same time.
- The executive who approved the economics does not write every requirement.
- Architects do not negotiate every commercial substitution.
- Providers do not own every operating consequence.
- Engineering teams may receive instructions without the reasoning that made them economically sound.
The business case can remain unchanged while the thing consuming the capital becomes materially different.
Control specification
Material execution changes must retain a path back to the economic proposition they alter.
Conversion failure
Installed capability fails to become operating value.
Technology business cases usually assume changes beyond the technology.
- Approvals change.
- Work moves.
- Roles change.
- Staffing or external spend changes.
- Controls change.
- Legacy systems disappear.
If the technical capability changes while the surrounding operating system remains largely intact, part of the modeled return remains stranded.
- Employees can use the new application while preserving the old spreadsheet.
- Automation can execute the task while the manual control remains.
- A new platform can operate while the legacy system remains licensed and supported.
- Faster task execution can disappear inside an unchanged approval chain.
Usage and economic conversion are different measures.
Control specification
The investment case has to include the workflows, roles, decisions, incentives, controls, costs, and legacy mechanisms whose change is required for the expected return to exist.
Revision failure
New evidence changes the economics faster than the enterprise changes the commitment.
Execution produces information that did not exist when the decision was made.
- Integration proves harder than expected.
- Vendor capability changes.
- Users behave differently.
- One bottleneck disappears and exposes another.
- Actual operating costs become clearer.
- Regulation changes.
- A competing mechanism improves.
- The people who see the evidence first often control implementation detail rather than the underlying capital allocation, architecture, provider, or premise.
- Meanwhile, contracts, integrations, standards, staffing, executive sponsorship, dates, and dependent programs make revision progressively more expensive.
A program can remain green after the enterprise answer has turned red.
Control specification
The commitment needs explicit conditions for reconsideration, enough retained reversibility for reconsideration to matter, and a route by which material evidence can reach someone able to change the underlying decision.
Residual burden
The completed investment changes the economics of the next one.
Every modernization initiative leaves an estate.
- architecture
- interfaces
- data structures
- contracts
- provider dependencies
- skills
- workflows
- governance
- institutional knowledge
- technical debt
- workforce experience
- future options
remain after the original program closes.
- Many of those costs arrive under another sponsor and another business case.
- The residual estate then becomes part of the opportunity set and constraints presented to the next decision.
The original investment can retain its reported return while exporting part of its cost into the future.
Control specification
Evaluate the state the investment leaves under both success and failure, including future change cost, exit cost, reusable capability, retained knowledge, dependencies, organizational effects, and preserved options.
The six mechanisms form a loop
- Underwritingdetermines what receives resources.
- Compositiondetermines how that commitment interacts with everything else.
- Translationchanges the proposition as it becomes executable.
- Conversiondetermines how much installed capability becomes operating value.
- Revisiondetermines whether new information can change the commitment.
- Residual statebecomes part of the starting condition for the next decision.
The residual estate becomes part of the opportunity set and constraints presented to the next decision.
Consider one platform decision.
- The enterprise selects the platform from an incomplete opportunity set.
- The platform has a defensible standalone business case, but its architecture conflicts with two other modernization programs.
- Procurement and implementation make individually reasonable substitutions that reduce part of the expected operating benefit.
- The platform goes live, but legacy processes remain and much of the old cost base survives.
- Delivery teams learn that an original assumption was wrong, but the platform is now deeply integrated and costly to replace.
The program closes.
The economics continue.
- A later initiative now has to accommodate the platform, pay to unwind it, or abandon alternatives that no longer fit.
- The first commitment has altered the second decision before the second decision begins.
The same mechanism can compound positively.
A well-chosen investment can
- reduce uncertainty
- create reusable capability
- remove dependencies
- improve institutional knowledge
- preserve useful flexibility
The next decision then begins from a stronger state.
Modernization accumulates conditions for future modernization.
How much of the promise survives?
- BeforeMaterial value disappears before implementation begins,
- Duringwhile the commitment is being executed,
- Afterand after delivery is nominally complete.
The relevant economic question is how much of the original promise survives the full path.
Call that modernization yield.
- FinancialSome of that yield appears as realized financial benefit.
- CapabilitySome survives as reusable operating, technical, informational, or organizational capability.
- OptionsSome appears in the options the enterprise preserves for what comes next.
- No universal percentage combines those forms honestly. Different enterprises value capacity, knowledge, flexibility, and future options differently.
- The financial arithmetic alone shows the leverage.
One large transformation study illustrates the financial portion of this problem. In McKinsey’s 2021 global survey, respondents from companies reporting successful transformations estimated that they captured 67 percent of the maximum financial benefit available.
The same study attributed the lost value across the full transformation path: 22 percent during target setting, 23 percent during planning, 35 percent during implementation, and 20 percent after initiatives had been fully executed. In other words, 55 percent of the reported loss occurred during or after implementation.
This evidence supports the financial-benefit component of modernization yield. The broader construct, including retained capability and future options, is Talbot West’s.If the available financial benefit is B, improving capture by p produces B × p of additional realized benefit.
- $3M
Three additional percentage points against a $100 million benefit pool.
- $15M
The same three points against $500 million.
- $30M
The same three points against $1 billion.
The larger effect comes when improved capability and future options also change the economics of later decisions.
Continuity is the control problem
The enterprise can have a capable
- finance organization
- architecture function
- PMO
- operating organization
- transformation office
- executive team
- provider ecosystem
and still lose the economic proposition as responsibility moves among them.
One consequential commitment has to remain legible and actionable from the original opportunity through the residual state.
The modernization continuity test
Take one consequential modernization commitment and trace it through six points.
- 01
Underwriting
The enterprise can reconstruct the outcome being pursued, the constraint being changed, the materially different alternatives considered, the expected economics, and the assumptions on which the commitment depended.
- 02
Composition
The enterprise can show how the commitment interacts with other investments, shared constraints, dependencies, architecture, and scarce organizational capacity.
- 03
Translation
Material implementation changes remain traceable to the assumptions and economics they alter.
- 04
Conversion
The operating changes required to turn installed capability into the expected result remain defined, owned, and measurable.
- 05
Revision
Material new evidence retains a route to someone with authority to reopen the commitment while revision remains economically possible.
- 06
Residual state
Before the investment is declared economically complete, the enterprise accounts for what it has added to or removed from the costs, capabilities, dependencies, and options facing the next decision.
Keep more of the promise
Complex enterprises will not eliminate modernization leakage.
- Specialization is necessary.
- Uncertainty is real.
- Conditions change.
- Execution produces information that did not exist when the original decision was made.
The objective is to preserve more of the economic promise as it moves through the enterprise.
The leverage comes from scale, breadth, and recursion.
- ScaleLarge enterprises pursue large pools of modernization value.
- BreadthBetter continuity can affect portfolios rather than individual projects.
- RecursionEach improved commitment can also improve the conditions under which later commitments are made.
Bibliography
- Bucy, Michael, Bill Schaninger, Kate VanAkin, and Brooke Weddle. “Losing from Day One: Why Even Successful Transformations Fall Short.” McKinsey & Company, 2021.
- Brynjolfsson, Erik, and Lorin M. Hitt. “Beyond Computation: Information Technology, Organizational Transformation and Business Performance.” Journal of Economic Perspectives 14, no. 4, 2000.
- Flyvbjerg, Bent. “From Nobel Prize to Project Management: Getting Risks Right.” Project Management Journal 37, no. 3, 2006.
- Kruchten, Philippe, Robert L. Nord, and Ipek Ozkaya. “Technical Debt: From Metaphor to Theory and Practice.” IEEE Software 29, no. 6, 2012.
