Choosing the Right Mix of Evolve, Jump and Attack for Financial Services Transformation
For banks, insurers and wealth managers, transformation is no longer a question of whether to act, but how to act with clarity. Customer expectations are rising. Digital-first competitors are reshaping market standards. Regulatory complexity continues to grow. And many institutions are still carrying the weight of legacy technology, siloed data and operating models built around products rather than customer outcomes.
That is why the most important transformation decision is rarely “Which model should we choose?” It is “Which combination of models will move our business forward now, while building the capabilities we need next?”
Evolve, Jump and Attack are three distinct but not exclusive approaches to transformation. The strongest agendas are usually not defined by one of them alone. They are shaped by when to use each one, where to place the first bet and how to sequence them over time.
A practical way to decide
A useful starting point is to assess your transformation agenda across six dimensions:
- Legacy complexity: How deeply do core platforms, processes and data constraints limit change?
- Speed-to-market pressure: How urgently do you need to launch new propositions or capabilities?
- Customer experience gap: How far are your current journeys from what customers now expect?
- Cost-to-income ambition: Is your priority structural efficiency, growth or both?
- Appetite for new revenue creation: Are you trying to defend the core, expand existing value pools or create entirely new ones?
- Organizational readiness: Does leadership, culture and governance support new ways of working?
These factors help determine whether your institution should modernize the core, create a parallel path for migration, launch something entirely new or combine all three.
When Evolve is the right starting point
Evolve is the incremental transformation of a legacy organization toward a more effective future model. It addresses the business end to end, from customer journeys and commercial offerings to operational and technical capabilities. It is often the right choice when the core business is too important, too interconnected or too regulated to bypass.
Choose Evolve when:
- Your core franchise is strong, but costly or slow
- Legacy systems create friction, yet cannot be replaced all at once
- Customer journeys need redesign across channels and functions
- You want to reduce structural inefficiency while preserving continuity
- Leadership is prepared for enterprise-wide commitment and investment
For many institutions, Evolve is the foundation. It modernizes legacy systems, improves data accessibility, supports real-time decision-making and enables more seamless, omnichannel engagement. It is also the model most associated with broad operating model change, including the shift from product-centric structures toward customer-centric journeys and cross-disciplinary teams. When done well, Evolve has been shown to support cost-to-income targets in the 40 to 50 percent range.
But Evolve has limits. If market pressure is intense, if technical debt is too constraining or if a business line needs a cleaner break from the past, incrementalism alone may not move fast enough.
When Jump becomes the smarter move
Jump is the establishment of a new shell into which an existing business or functional capability can be migrated. It is designed to overcome the practical limits of evolving in place. Rather than untangling every dependency inside the existing estate before progress can happen, Jump creates a cleaner destination with new platforms, new ways of working and new customer experiences.
Choose Jump when:
- A specific business line is constrained by legacy architecture or operating processes
- You need a faster route to modern platforms without waiting for enterprise-wide change
- The institution wants to ring-fence risk while proving a new model
- There is a clear migration path for customers, products or capabilities
- The business is ready to adopt new operating rhythms in a contained environment
Jump is particularly useful when leaders ask: does this need to be a full end-to-end transformation, or can we move business line by business line? In many cases, a targeted migration creates the right balance between ambition and manageability. It can reduce costs, accelerate delivery and create better customer experiences without requiring the whole enterprise to move in lockstep.
For example, if a retail bank wants to replatform a lending business, or an insurer wants to modernize a claims capability without overhauling the entire organization at once, Jump can create a practical bridge between today’s constraints and tomorrow’s operating model.
When Attack is the right answer
Attack is the launch of a brand-new digital proposition designed to reach new customers and generate a new revenue stream. It is best suited to moments when defending the core is not enough and the institution needs to compete more directly with digital-native challengers or pursue entirely new growth.
Choose Attack when:
- You see unmet customer needs that the current business cannot serve well
- Time-to-market matters more than integrating immediately with the full legacy estate
- You want to test a new commercial model, segment or proposition
- Leadership has appetite for innovation and tolerance for experimentation
- New revenue creation is a strategic priority, not a side initiative
Attack works best when it is driven by a clear customer problem and a commercial model that becomes more powerful over time rather than more commoditized. That means starting with the big idea: what need are you solving, why will customers value it and what distinctive capabilities will make it successful?
This model is especially relevant for launching net-new propositions in areas such as digital banking experiences, new insurance products or wealth offerings designed for emerging segments. Publicis Sapient’s experience building a fully digital trade finance bank from concept to live in a matter of months shows what is possible when strategy, product, experience, engineering and data come together around a sharply defined opportunity.
Three common scenarios
1. Modernizing a core legacy business
If your biggest challenge is a high-cost, slow-moving core business with major customer experience gaps, start with Evolve. Redesign the journeys that matter most, modernize the technology that enables them and align teams around customer outcomes rather than internal silos. Then use Jump selectively where legacy constraints are too severe to overcome efficiently inside the existing environment.
2. Migrating a single business line into a new shell
If one business line is disproportionately constrained by legacy complexity, Jump is often the better lead model. It provides a modern platform and operating model without waiting for full enterprise transformation. Evolve can then continue in parallel in the legacy organization, especially where shared services, governance and enterprise capabilities still need modernization.
3. Launching a net-new digital proposition
If the objective is growth through a new customer offer, Attack should usually lead. Build the proposition around a clear unmet need, rapid experimentation and a differentiated set of capabilities. Over time, use Evolve to prepare the broader organization to absorb what works, and Jump where migration into a scalable modern environment is needed.
Why sequencing matters more than purity
The biggest mistake is treating Evolve, Jump and Attack as mutually exclusive choices. In reality, they are most powerful when used as a portfolio.
Evolve helps stabilize and strengthen the core. Jump creates a faster path to strategic platforms and new ways of working. Attack builds optionality, new revenue and future relevance. Together, they allow institutions to address immediate pain points, mid-term modernization goals and long-term growth opportunities at the same time.
The real leadership challenge is not selecting a label. It is making a few high-conviction decisions:
- Where do we need continuity?
- Where do we need separation?
- Where do we need speed?
- Where do we need experimentation?
- What capabilities should we build because they differentiate us?
- What should we rent, simplify or retire?
The organizational question is just as important. Every model depends on readiness for change. Transformation requires new approaches to planning, performance and decision-making. It requires empowered cross-functional teams. It requires investment in people, not just platforms. And it requires the willingness to trial new ways of working while keeping compliance, trust and security embedded by design.
A better transformation conversation
For financial institutions, the goal is not simply to modernize technology. It is to become more adaptive, customer-centric and capable of continuous evolution. Choosing the right mix of Evolve, Jump and Attack creates a practical framework for doing that.
If your institution is deciding where to place the next transformation bet, the smartest move may not be one model. It may be a sequenced strategy: evolve the core, jump where constraints are too great and attack where new growth demands a fresh start. That is how transformation moves from aspiration to action—and from isolated initiatives to measurable business outcomes.