Digital transformation and change programmes naturally create pressure to move. 

Once an organisation has identified an opportunity, committed investment or set a target date, the instinct is understandably to start delivering. Progress matters, stakeholders want to see it and teams are keen to turn plans into something tangible. But after years of working across large-scale digital integration and transformation programmes, the ARRT team has learned that sometimes the best way to accelerate change is to spend a little more time understanding the starting point. 

Not because something has necessarily gone wrong. 

Technology estates evolve. Businesses grow. Priorities change. New applications are introduced. Suppliers change. Regulation moves on. What was the right decision at one point in an organisation’s journey may simply not be the right foundation for what it wants to do next. 

We sat down with ARRT’s Alistair Mackenzie, Tony Bennett and Dan Bovenzi to explore some of the patterns they have seen throughout their careers, and why an impartial view of the current environment can be so valuable before the next phase of change begins. 

A transformation programme usually begins with an outcome in mind. There may be a platform to replace, a process to improve, a growth target to support or a wider transformation objective to deliver. 

Once that destination has been established, attention naturally turns towards getting there. The challenge is that the scale of what sits beneath an objective often only becomes fully visible once the detail is explored. 

Dan points to the amount of work that can sit behind what initially appears to be a relatively straightforward change, while Alistair has seen how frequently programmes begin with a target date before every element of the journey towards it has been fully defined. 

Tony sees the same challenge from a delivery perspective: 

“There is always a desire to see progress quickly. The challenge is making sure you understand enough upfront to ensure that progress is taking you in the right direction.” 

That means understanding more than which systems need to connect. 

Business processes, requirements, data, dependencies and non-functional requirements all influence what the right solution looks like. Even the less visible scenarios matter. What happens when something doesn’t work as expected? How is state synchronised between systems? How does the process recover? 

Creating space to understand those things doesn’t mean slowing a programme down. It can help avoid discovering them when delivery is already underway. 

Most technology estates are the result of perfectly rational decisions made at different points in an organisation’s history. A new application solved a particular requirement. A direct connection between two systems got an important process moving. A manual workaround allowed a team to meet a deadline. A supplier provided capability that wasn’t available internally. 

Each decision can make complete sense in context. Over time, however, businesses change around those decisions. Growth can increase transaction volumes. New platforms are introduced. Regulatory requirements evolve. Processes that were once manageable become more complex. New ambitions around automation or AI place different demands on data and existing systems. 

The question isn’t whether previous decisions were right or wrong. It is whether the environment that exists today supports what the organisation wants to achieve next. 

Dan describes the purpose of establishing that position simply: 

“It’s about understanding where you are today, where you’re trying to get to, and the gap between the two.” 

That distinction is important. Existing technology and processes may have served an organisation successfully for years. A constraint can become visible simply because the business has moved beyond the circumstances they were originally designed for. 

There is another very human factor involved. When people work with the same applications, processes and suppliers every day, they naturally become familiar with how everything fits together. Workarounds become established processes. Dependencies become part of normal operations. Teams become very good at working within the environment they have. 

That knowledge is incredibly valuable. 

But there can also be value in occasionally stepping outside that environment and looking at the whole picture with fresh eyes. The benefit of an external perspective isn’t that arrt knows an organisation better than the people running it. Quite the opposite. 

The organisation brings the deep knowledge of its business, customers, systems, constraints and ambitions. ARRT brings experience from working across complex digital integration and transformation programmes and an impartial perspective that isn’t tied to the history of how the current environment developed. 

The Health Check brings those two perspectives together. 

The arrt Health Check is designed to establish a clearer picture of where an organisation is today and how well its existing foundations support where it wants to go next. 

Depending on the organisation and its objectives, that can involve looking across areas including digital integration, architecture and design, data architecture and governance, environments and platforms, software development lifecycle, support and monitoring and, increasingly, AI platforms and the agent lifecycle. 

Alistair uses a simple analogy to describe the thinking behind it: 

“For us, it comes back to the foundations. Are you building on sand or solid foundations? But that assessment has to be made in the context of what the organisation is actually trying to achieve.” 

The purpose isn’t to find fault. It is to understand which foundations are already strong, where there may be gaps or dependencies and which of those things actually matter for what the organisation wants to do next. 

That last point is important. An arrt Health Check isn’t a generic technical checklist designed to compare every organisation against the same idea of maturity. 

Context matters. 

Every organisation is different, and something that represents a significant constraint for one may have little or no impact on another. A supplier dependency might be relatively unimportant in one environment but more significant in another where speed and greater internal ownership are strategic priorities. That’s why the starting point is understanding the organisation’s business and technical objectives. 

As Alistair explains: 

“We’re not assessing something against our opinion of what ‘good’ should look like. We start with what the organisation has told us it wants to achieve, and look at whether the current environment supports that.” 

It creates a much more useful question: 

Does your current environment support where you want the organisation to go next? 

Rather than arriving with a predetermined answer, the Health Check provides a way of considering the technology environment in the context of the organisation’s own ambitions. 

The process itself is deliberately focused.  A typical Health Check takes around two to three weeks, although the scope naturally depends on the organisation and what it wants to understand. It is largely an interview and evidence-led process. 

For each of the agreed areas, arrt identifies the people best placed to help build the picture. Depending on the organisation, that might include technical leads, architects, developers, data and BI specialists, security specialists and members of the management team. 

The technical conversations help us understand how the environment works today. The wider business conversations establish where the organisation is trying to go and what the technology needs to enable. 

Relevant documentation is reviewed too. 

Both what exists and what doesn’t can be informative. For example, if an important process relies heavily on knowledge held within a team rather than documented standards or processes, that may simply be an area worth exploring as the organisation plans for future scale or resilience. 

The aim is to build a rounded picture, not to run through a rigid checklist. 

Digital integration is a good example of how this happens. Connecting two systems directly can be an entirely sensible response to an immediate business requirement. As an organisation evolves, however, more applications, processes and suppliers are introduced. Several individually sensible connections can gradually become an environment in which making a change to one system has consequences elsewhere. 

Nobody necessarily designed that complexity. It accumulated as the organisation evolved. 

In some environments, different connections may involve different technologies, different suppliers and different support arrangements. Introducing change can then require coordination across several parties and an understanding of dependencies that extend beyond individual systems. 

The arrt team has encountered this pattern in different forms across its experience. It is often only when you look across the technology landscape as a whole that the cumulative impact becomes apparent. 

Alistair describes the principle ARRT applies to digital integration as one of reducing and managing those dependencies: 

“The aim is to isolate dependencies and manage them in a way that abstracts some of that complexity from the wider business.” 

That can help create an environment where changing one application doesn’t unnecessarily create a chain of changes elsewhere. 

Once the assessment is complete, the output needs to be practical. The intention isn’t to produce an enormous technical report that is difficult for the wider business to consume. Instead, the Health Check provides an executive summary of the overall position, supported by more detailed findings across the agreed areas. 

A RAG status helps identify where foundations are strong, where there are areas worth watching and where something may need to be prioritised. Importantly, it highlights what is working well too. That matters because a Health Check shouldn’t create the impression that everything needs to change. Often, the most valuable finding may be that an existing capability is working well and should be retained or built upon. 

The result should give the organisation a clearer answer to three questions:

• Where are we now? 
• Where are we trying to get to? 
• What should we prioritise to help us get there? 

The Health Check report is a starting point rather than an end product.  Once the priorities are understood, the organisation can decide how it wants to address them. That doesn’t necessarily mean launching a large remediation or transformation programme. Findings can be broken into manageable areas of work, with each addressing a particular priority and building on what is already there. arrt’s role can vary too. 

Tony explains: 

“Sometimes the right role for us is to help deliver the change, sometimes it’s to work alongside the existing team, and sometimes the most useful thing we can provide is the advice and a clear route forward.” 

Where digital integration is identified as a priority, one potential route may be to introduce more reusable foundations rather than continuing to solve each connection independently. This is where capabilities such as the arrt Integration Brain can become relevant. The principle is to create reusable digital integration patterns and capabilities that can support multiple processes as the organisation continues to evolve. 

As Tony explains: 

“If you can develop something once and then reuse that pattern elsewhere in the business, you’re getting much more value from that original investment.” 

It is not about replacing everything that already exists. It is about building on the current environment in a way that makes subsequent change easier. 

Perhaps the most important point is that a Health Check isn’t an exercise in identifying what an organisation has done wrong. Businesses evolve, and technology evolves with them. The decisions and capabilities that helped an organisation reach one stage of its journey won’t always be the same ones it needs for the next. 

An impartial Health Check creates an opportunity to look across that environment with fresh eyes while keeping the organisation’s own ambitions at the centre of the assessment. 

• What are you trying to achieve? 
• What is already working well?
• What could make that ambition harder?
• What could make that ambition harder? 
• And where would focused change create the greatest value? 

For arrt, that is ultimately what the Health Check is about. Not slowing transformation down, but creating the clarity and foundations that allow an organisation to move forward with greater confidence and accelerate the journey ahead. 

And the question we haven’t answered yet: what does an arrt Health Check cost? 

Can you believe it? Nothing.