Why Transformation Programmes Fail in Global Markets
A diagnostic for COOs, business heads and programme sponsors
Most transformation programmes in Global Markets do not fail dramatically. What happens in practice is quieter and more corrosive: the programme closes milestones, status packs stay amber at worst, and the steering committee receives a steady diet of activity rather than evidence.
By the time the outcome is assessed with any rigour, the benefits are diluted, the costs have overrun, the timeline has stretched and the operating model looks considerably less like the target state approved at the outset.
The diagnosis is consistent across many institutions and programmes. Most underperformance is not caused by weak project management or a failed workstream. It is caused by a structural gap between what the steering committee believes it has funded and what a live, front-to-back Global Markets environment actually requires to change safely - that gap opens early, often before mobilisation, and widens progressively as execution uncovers complexity that was never truly costed or sequenced.
Ambition without institutional self-knowledge
The initiating business case can often occur where most programmes are already compromised. Investment banks routinely approve transformation on the strength of a strategic narrative: simplification, resilience, cost reduction, regulatory compliance, competitive positioning.
The problem that can arise is that approved scope, budget and milestones frequently do not reflect the true complexity of what needs to change. The organisation has not fully mapped how work gets done in practice; where the control burden sits, how many dependencies exist outside the formal programme boundary, and how much of the current operating model is sustained by tacit knowledge, manual intervention and workaround logic accumulated over years.
The consequence is that what later appears as slippage is usually delayed discovery of work that was always necessary. The programme is not failing to deliver what it promised. It is discovering what it should have promised in the first place.
Five recurring failure patterns
Across our experience of Markets transformation, five patterns recur with sufficient consistency to be treated as structural rather than situational.
1. Weak translation from ambition to executable design
Programmes are approved with insufficient bottom-up validation of process variants, exception volumes, booking model nuances, regulatory obligations and non-functional requirements. Strategic narratives compress complexity.
The result is that design and build phases encounter variation and edge-cases that were not visible at approval, and the programme absorbs both the cost and the time of resolving them without formally acknowledging that the original scope was under-specified.
2. Absent benefits discipline
The link between programme activity and commercial or operational outcome is rarely defined with enough precision to be tested.
In practice this means a programme can continue to report delivery and expenditure while remaining unable to evidence whether client experience, processing capacity, capital efficiency or cost-to-income has materially improved. The benefits case at approval becomes a historical artefact rather than a live accountability mechanism.
3. Organisational fragmentation
Ownership of a Markets transformation is split across trading, sales, risk, operations, finance, compliance, technology, legal entity management and infrastructure, each with different objectives and different tolerance for pace of change. In Markets those silos are structural rather than accidental.
The programme sits in the middle of the functions and is damaged by each.
4. Pace asymmetry
Transformation timetables are built as if all participants change at the same speed.
Front-office businesses, control functions, operations teams, architecture groups and external vendors move at materially different cadences. In execution, that produces serial dependency chains, delayed sign-offs, repeated redesign and rework. The critical path is not where the programme sponsor believes it is.
5. Misaligned practitioner engagement
Programmes routinely require input from front-line practitioners asked to carry a project role alongside core responsibilities.
The structural problem is that financial performance in the front-line role remains the primary measure of career progression and organisational standing. Project contribution is therefore secondary, and most experienced practitioners respond accordingly.
A related dynamic compounds this. When a genuinely high-performing practitioner is identified as a project resource, the business faces an implicit choice: release someone whose contribution is missed from the desk, or find an alternative.
In practice, project roles frequently fall to experienced individuals whose front-line contribution has become more marginal. The programme can receive nominal business sponsorship with the right institutional history but, in practice, neither the active engagement nor current operational awareness the role requires.
There is a further distinction this dynamic obscures. Corporate memory, knowing which systems behave unexpectedly under load, which cross-border dependencies are undocumented, which relationships carry institutional weight, is genuinely valuable and synthesisable without endangering the programme.
Genuine front-to-back operational awareness is different in kind: the capacity to hold the integrated view across trading, risk, finance and operations simultaneously, to understand how a design decision in one part of the chain creates consequences three steps downstream, and to carry the authority to act on that understanding across functional boundaries.
This is not automatically accumulated by twenty years in a front-line role. It is a specific and relatively rare capability, and the one most consistently absent from programmes where the structural gap between ambition and executable design is widest.
Why Global Markets fails differently
These patterns exist across banking. In Global Markets they are amplified because revenue generation depends on market access, pricing quality, client responsiveness and uninterrupted control environments. Even small defects in workflow design carry immediate conduct, prudential or reputational consequences.
The business model is not tolerant of extended parallel runs or systems instability.
Product and workflow complexity is routinely underestimated. A programme labelled as a global markets platform simplification typically conceals dozens of different operational realities across rates, FX, credit, equities, listed derivatives, prime and structured products. Standardisation assumptions that appear reasonable in a business case become expensive to maintain under the weight of product-by-product variation discovered during design and testing.
Control intensity is a first-order delivery constraint, not a background condition. Technology change in a Markets environment alters pre-trade controls, kill-switch logic, monitoring thresholds, model assumptions and supervisory accountability. Late design changes in this context are not just expensive. They are risky in ways that require separate governance treatment and can trigger regulatory engagement at a point where the institution has limited room to manoeuvre.
The front-to-back nature of the business creates hidden propagation risk. A change that appears front-office-led typically propagates into confirmations, settlements, collateral, P&L explain, market risk, finance substantiation, prudential reporting and surveillance. Local optimisation frequently creates enterprise fragmentation rather than simplification, particularly when programmes are sponsored by a single desk without genuine lifecycle ownership of the end-to-end chain.
Third-party dependency is a live source of delivery risk. Reliance on exchanges, clearing houses, market data providers, execution venues and post-trade utilities means programme timelines can be constrained by parties outside the bank's direct control.
Internal plans treat these as fixed assumptions. They rarely are.
How governance conceals deterioration
One of the more consequential structural failures is that governance mechanisms can mask delivery risk rather than surface it. Steering packs show green because milestones were rebaselined, scope was quietly narrowed, or target metrics were softened without a formal reset of the business case. The programme continues to report forward momentum while the underlying operating model remains dependent on manual intervention, subject-matter-expert concentration, unresolved vendor commitments and control exceptions.
From a COO perspective, the tell is almost always the same: the programme is reporting delivery while the business is absorbing an increasing volume of manual exception management and duplicate processing to keep operations running. That operational drag does not show up in programme status. It shows up in headcount, exception rates and operational incident volumes, often in functions that sit outside the formal programme boundary.
Where under-delivery actually shows up
Benefits under-delivery presents first as slippage in hard economic outcomes. The programme closes milestones, but the bank does not remove expected headcount, reduce manual touchpoints, lower exception rates, improve capital velocity or retire duplicate platforms at the pace assumed in the investment case. Local efficiencies are created while enterprise costs remain intact because old and new processes coexist for longer than planned.
Cost overrun has three diagnostic causes:
hidden work excluded from the approved budget,
the absorption of architectural debt that predates the initiative but must be resolved to enable it,
and scarce subject-matter experts pulled into repeated design loops because requirements were not stable at inception.
Timeline overrun follows from dependency congestion: governance sign-off, model validation, vendor release calendars and regulatory clearance all become rate-limiting constraints that were treated as background conditions in the original plan.
The diagnostic conclusion
The central weakness is not that investment banks attempt too much change. It is that they routinely underestimate what done means in a Global Markets context. The organisation has approved a transformation without a sufficiently grounded prior assessment of how work actually happens, where the genuine control burden sits, and how much of the current franchise depends on manual judgement and accumulated workaround.
In a Global Markets division, those gaps convert quickly into benefit dilution, cost escalation and schedule slippage.
The programmes that do deliver tend to share one characteristic: someone with genuine operational authority and front-to-back credibility was involved in framing the scope before approval, not in recovering it after the fact.
What underperformance actually costs
The failure patterns described above produce two distinct categories of cost.
Delivery costs are the direct, budget-visible consequences of a programme under-specified at approval: hidden work never costed, architectural debt absorbed mid-delivery, and subject-matter-expert time consumed by repeated design loops.
Outcome costs are less visible but more consequential: headcount not removed, manual touchpoints not eliminated, platforms not retired, capital velocity not improved. Where old and new processes coexist for longer than planned, the enterprise cost base remains largely intact while the programme is reported as closed.
There is a third cost that rarely appears in any budget line: leadership attention. A programme in difficulty consumes disproportionate senior time, occupies governance capacity that would otherwise be directed at strategic decisions and creates organisational drag that compounds across the full duration of underperformance.
The companion paper sets out two modes of response: intervention when a programme is already in difficulty, and front-loaded engagement that addresses the structural gap before delivery and outcome costs have the opportunity to arise.
About FMCR
FMCR is a network of senior practitioners, former COOs, global business heads, traders and risk leaders from Tier 1 global banks, providing advisory services to Markets and Banking leadership teams across risk management and performance. To discuss how FMCR can help your firm, contact Jason Richardson (jasonrichardson@fmcr.com) or Ian Gaskell (iangaskell@fmcr.com), or visit fmcr.com.
Written by Jason Richardson, a Senior Consultant at FMCR with over two decades’ experience across trading, sales, and enterprise transformation.