Most transformation programmes that end up needing rescue work in the UAE do not fail dramatically. They drift. The drift is rarely visible from the outside, sometimes not even visible from the inside until quite late, and almost always shaped by patterns that recur from one engagement to the next. The patterns are not about incompetence. The teams running these programmes are usually capable, the advisory firms are usually substantial, and the original specifications are usually reasonable. What produces the rescue moment is the cumulative effect of small, individually rational decisions accumulating into a programme state that is no longer delivering what it was set up to deliver.
This piece is a perspective on the structural shapes that rescue work in the UAE consistently has, what they teach about how transformations drift, and what the rescue model actually involves when done with discipline. The argument is opinionated. We are not arguing that programmes drift because of poor execution. We are arguing that drift has predictable mechanics, that the mechanics are not the fault of the people running the work, and that the rescue model that holds up in this market is structured rather than heroic, observation-led rather than blame-led, and explicitly designed to keep the original advisory relationship intact rather than to displace it.
The audience for this analysis is two-sided. Advisory firms running long-running UAE transformation engagements that have started to drift, and considering bringing in delivery support to stabilise. And client-side transformation directors carrying portfolios of programmes that include one or two that are not where they should be. In both cases, the most useful question is not "whose fault is the drift" but "what shape is the drift, and what does the structured response look like."
The Six Shapes of Drift
Below is a representation of the six recurring patterns visible across UAE rescue engagements. The point is not that any single programme matches one pattern exactly; most struggling programmes show two or three of these shapes in combination. The value of naming the patterns is that the diagnostic conversation moves from "what is wrong with this programme" (a question that invites blame) to "which of these recurring shapes are we seeing, and what is the structured response" (a question that invites delivery). Tap any pattern to see its symptoms, underlying cause, and the rescue approach that holds up.
Six recurring drift patterns in UAE transformations
Tap any pattern to see what it looks like, why it happens, and what works in rescue
Why Most Rescues Have the Same Shape
The recurring patterns visible across UAE rescue work are not coincidence. They reflect structural realities of how large transformation programmes are run in this market: long timelines that span multiple steering rotations, regulatory environments that evolve faster than programme specifications, multi-vendor delivery models that are now the norm rather than the exception, and stakeholder communities that are wider than they used to be. The patterns are produced by the operating environment as much as by any specific programme decision.
Three observations stand out from looking at rescue work across sectors. The first is that drift compounds quietly. A programme that is six weeks behind plan rarely escalates immediately; the team absorbs the slippage and replans. By the time the slippage is twelve weeks, then twenty, the programme has often crossed a threshold where catching up requires structured intervention rather than tactical adjustment. The compounding is not visible at any single point because each individual decision was reasonable.
The second is that the same shapes recur across sectors. Banking transformations, government modernisation programmes, construction technology builds, large retail platform replacements - the surface details differ but the drift mechanics are remarkably consistent. Scope creep collapses look the same in a CBUAE-supervised banking build as in a Dubai government portal modernisation. Governance fatigue looks the same across a CBUAE programme and a multi-tenant retail platform. This is useful because it means the rescue patterns are transferable across sectors, even when the technical details are not.
The third is that the cause is rarely incompetence. Programmes that need rescue work are usually staffed by competent people, run by capable firms, and originally specified by sound advisors. What produces the rescue moment is structural: change governance that scaled down without anyone noticing, integration assumptions that did not survive contact with reality, vendor cycles that left explicit knowledge but not tacit knowledge with the next team. The structural framing matters because the rescue then becomes about restoring structural conditions for delivery, not about replacing the people involved.
The shift in one observation
The most useful diagnostic question in a struggling programme is not "what went wrong" but "which structural conditions for delivery have weakened, and what is the smallest restoration that gets the programme moving again." The first question invites blame and slows the response. The second question invites action and respects the work that came before.
The Rescue Model That Holds Up in This Market
Four principles distinguish rescue work that succeeds from rescue work that simply replaces one struggling programme with another. None of them are exotic. They are unglamorous, sometimes uncomfortable, and consistently the difference between a stabilisation that holds and one that does not.
Stabilise before reshape
The first instinct in rescue work is often to redesign the programme. The discipline that holds up is the opposite: stabilise the current state first, get delivery moving again, then make structural adjustments from a position of momentum. Programmes that try to redesign before stabilising usually accumulate more drift before the new design lands. Programmes that stabilise first often discover that less redesign is needed than was initially assumed.
Respect what came before
Rescue teams that walk in critical of the original work face two problems. The original team and stakeholders close ranks defensively, which slows access to the information rescue needs. The advisory firm that brought the rescue partner in loses face, which weakens the relationship. The discipline is to treat existing work as the starting point, even where the starting point has problems. Most original specifications, plans, and architectures contain genuine value; the question is what to keep, what to adjust, and what to set aside, not whether the previous team was capable.
Move from blame to outcome
The faster the rescue conversation moves from "what went wrong" to "what gets us delivering again," the faster the rescue itself moves. Blame conversations have their place, but they happen later, separately, and are usually owned by the client rather than by the rescue team. The rescue team's value is in delivery restoration, not in retrospective analysis. Programmes where the diagnostic phase becomes a finger-pointing exercise typically take twice as long to stabilise as those where it stays focused on forward action.
Set the team up for handback
The rescue is not a long-term position. The objective is to stabilise the programme, restore delivery cadence, and hand the work back to a sustainable steady-state team. Rescue teams that build for indispensability create their own follow-up problem. The discipline is to document, transition, and exit cleanly, leaving behind a programme that the original advisory firm and client team can continue to run without rescue dependency. This builds trust with the advisory firm and makes the next rescue engagement easier to win when the call comes.
The Numbers
The Stabilisation Pattern Inside a 90-Day Window
Rescue engagements vary materially by programme size, sector, and the specific patterns of drift involved. The shape of the first 90 days, however, is reasonably consistent when the rescue is done with discipline. The objective is not to fix everything in 90 days. It is to move the programme from drift to stabilised delivery, with the structural conditions for ongoing forward motion restored.
| Window | Focus | Output |
|---|---|---|
| Weeks 1-2 | Diagnostic and pattern identification. Listening to the team, the advisory firm, and the client. No interventions yet. | Drift pattern map. Top three structural conditions to restore. Stakeholder alignment on the diagnostic. |
| Weeks 3-4 | Stabilisation interventions. Change governance reset. Specification gap closure. Decoupling of blocking dependencies. Lighter governance cadence introduced. | Programme moving forward at a reduced but predictable cadence. Backlog re-baselined. Decisions queued for the right authority and resolved. |
| Weeks 5-8 | Re-foundation. Specification debt closure on critical paths. System map reconstruction across vendor zones. Premise review where regulatory or environmental drift has occurred. | Build foundations stable. Cross-component decisions possible at programme speed. Premise tested against current environment. |
| Weeks 9-12 | Forward delivery at restored cadence. Handback planning. Documentation of what has changed and why. Steady-state team handover. | Programme running independently. Rescue team transitioning out. Original advisory firm and client team able to continue without rescue dependency. |
The rescue work that holds up in the UAE market is structured rather than heroic. It does not depend on bringing in better people; it depends on restoring the structural conditions for delivery that the programme has lost. The skill is observational, the approach is patterned, and the exit is planned from day one.
How Rescue Work Integrates with Advisory Engagement
The rescue model that has the best outcomes for everyone in the engagement (advisory firm, client, delivery partner) treats rescue as a complement to the advisory relationship rather than a replacement for it. The advisory firm holds the strategic relationship and the steering committee positioning; they brought the work in originally and they will own the long-term direction afterwards. The delivery partner holds the technical and operational restoration; they walk in, do the structured work, and walk out. The client experiences the engagement as continuous rather than as a vendor change.
This configuration requires explicit planning at the start of the rescue. Who owns which conversations, which decisions sit where, what gets reported to whom, and what handback looks like - all of this is more useful as a written agreement between the advisory firm and the rescue partner than as an implicit understanding. Rescue engagements that proceed without that explicit configuration usually produce friction even when the technical work goes well, because the relationship between the advisory firm and the rescue partner gets renegotiated under pressure rather than under planning.
This is the model BY BANKS is positioned for. We operate as a UAE-based engineering team that can be brought into a struggling programme by the advisory firm running it, with explicit handback planning from day one and a structured rescue approach that respects the work that came before. The advisory firm leads the strategic and client-facing relationship throughout. We focus on restoring delivery. The client experiences a single coherent engagement.
Where Structural Visibility Actually Helps
The conversations where this analysis is most useful are at three moments: an advisory firm with a long-running UAE transformation programme that has started to drift and is considering bringing in delivery support; a client-side transformation director carrying a portfolio that includes a programme not where it should be; or a rescue partner trying to integrate cleanly with an advisory firm holding the original relationship. The honest analysis usually points to the same structured response: identify which drift patterns are present, restore the structural conditions for delivery, and plan for handback from the start.
For broader related work, see our perspective on specialist engineering partners in UAE advisory engagements and our perspective on how discovery has become a sales phase in UAE consulting. The integrated practice sits across our technical consultancy, product development, and operational platforms capabilities. Get in touch if a 45-minute conversation about a specific programme situation would be useful.
Frequently Asked Questions
No, and that framing would miss the point of the analysis. Substantial advisory firms in the UAE produce a wide range of programmes, most of which deliver value, some of which drift. The drift mechanics described here are about the structural realities of long-running transformations in this market: regulatory evolution, multi-vendor cycles, steering committee rotations, scope absorption pressure. They are not particular to any firm. The patterns appear across the work of capable advisory firms and capable client-side teams alike, because the patterns are produced by the operating environment more than by the people in it. Rescue work is normal in long programme portfolios; it is a standard part of how transformation work happens at scale.
Through explicit role agreement at the start of the engagement. The advisory firm holds the strategic relationship, the steering positioning, and the long-term account direction. The rescue partner holds the delivery restoration work, with no parallel relationship-building activity outside the scope of the rescue. Communication channels are agreed: who reports to whom, what gets escalated where, what stays inside the rescue team's working space. Handback plans are written, not implicit. None of this is exotic; it is the same discipline that any sub-contracted delivery model requires, applied to a higher-stakes situation. Rescue partners that follow the discipline build durable relationships with advisory firms because the firms can call them again with confidence. Rescue partners that try to convert the rescue into a direct client relationship lose the advisory firm's trust and find that the next call does not come.
This happens, and the diagnostic moment is often initiated client-side rather than advisory-side. Client transformation directors carrying portfolios sometimes see drift patterns in a specific programme before the advisory firm running it does, particularly when other programmes in the portfolio are running smoothly by comparison. The constructive path in that case is to surface the diagnostic to the advisory firm with options for how to respond, including the option of bringing in delivery support, rather than triggering a confrontational review process. Rescue work that starts collaboratively between the client and the advisory firm produces materially better outcomes than rescue work that starts as an audit. The same six drift patterns apply; the politics of the engagement differ entirely.
Yes, with operational adjustments. Regulated sector rescue work has additional constraints: vendor approval frameworks, security clearance posture, named-resource provisions, audit trail requirements, and stricter governance cadences that cannot simply be lightened. The principles still hold, but the operational mechanics differ. Stabilisation interventions need to fit the regulatory framework. Specification debt closure has to respect approval chains. Premise reviews need to consider whether regulatory positions have moved as well as commercial ones. The 90-day stabilisation window is often closer to 120-150 days in heavily regulated programmes because the operational overhead is higher, but the underlying patterns are the same. The advisory firms with pre-arranged delivery partner structures for UAE banking, CBUAE-supervised work, and government engagements have a meaningful advantage over firms that try to assemble the partnership during a rescue.
Related but distinct. Turnaround work in its traditional sense usually involves replacing the management running a struggling programme. Rescue work as we describe it here works alongside the existing management and advisory structure to restore delivery without replacing the relationship. The difference matters for the politics, the speed, and the long-term outcome. Turnarounds tend to be confrontational and slow because the relationship reset takes time. Rescues tend to be collaborative and faster because the original team and advisory firm participate in the diagnostic and stabilisation rather than being subject to it. Both approaches have their place; in the UAE market, where transformation engagements are usually multi-year and the advisory relationships are long-term, the rescue model has better outcomes for all parties most of the time.
Rescue work in the UAE has a recognisable shape. The same six drift patterns recur across sectors, the same structural conditions need restoring in most cases, and the same disciplines distinguish durable stabilisation from temporary intervention. The advisory firms that handle drifting programmes well are not those who avoid drift entirely (drift is structural, not preventable) but those who recognise it earlier, bring in delivery support before it compounds, and structure the rescue engagement so that the advisory relationship survives intact. The rescue partner's job is to make that possible: to walk in, do the structured work, hand the programme back, and earn the next call when the next programme drifts.
References to advisory firms, rescue engagements, and UAE transformation work are descriptive of typical patterns in the market and do not refer to or imply any specific firm, programme, vendor, or client. Patterns and observations in this article reflect our own perspective on how UAE transformation programmes typically drift and how rescue work is structured. Numbers cited are observational estimates, not measured statistics. Public sources used in this piece are listed on our Sources and Data page.
Ready to Build Something?
If this resonated, let's talk about how we can apply these ideas to your business.
Start a Conversation