1. Understanding the opportunity

Sometimes, you know something is off but don’t know what’s wrong. At other times, you see competitors adopting tools or processes you have yet to explore and get that FOMO feeling. Before jumping into action, the priority is diagnosis.

Take one client in the airline industry. They had an agile culture but were hampered by outdated HR processes and a labyrinth of legacy systems. The result was poor employee experience, duplicated effort, and compliance risks. We worked with their People team to assess what was working, what was not, and what to tackle first. That diagnosis paved the way for a transformation roadmap that made sense of the mess.

See this case study: Building a digital HRIS strategy in the airline industry

2. Designing the future

New strategies often demand new structures. Whether it is a capability you need to build or a shift in how the organisation operates, design matters.

When a global chemical firm acquired a pipeline network, it needed to design and digitise more than 400 business processes from scratch. We worked with their in-house teams to map these processes, clarify responsibilities, and develop repeatable approaches they could apply to future changes.

See this case study: Case Study: Mapping and digitalising business-critical processes for INEOS FPS

3. Building the business case

Plenty of good ideas never get off the ground because they lack a compelling business case. A solid cost-benefit analysis does more than win funding. It aligns stakeholders and makes benefits explicit.

This might include both hard and soft elements. Tangible costs like software licences, implementation, or support, and intangible benefits like engagement, experience, or risk reduction. We help clients clarify what is in scope and what is not so that decisions are made based on real numbers rather than assumptions.

When a major supermarket needed funding for an organisational restructure, we used insights from similar programmes and their specific challenges to demonstrate a payback period of less than two years.

See this case study: Driving growth while reducing costs in retail

4. Choosing new technology

Technology often enables transformation, but picking the right one is rarely simple. We have supported clients selecting complex HR, payroll, and finance systems by helping them clarify requirements, run structured RFPs, and interrogate supplier assumptions.

With one global organisation, the brief was to choose a new HR system. The challenge was balancing functionality, supplier culture, and internal readiness. We worked closely with Procurement and HR to run a selection process that gave the team confidence in their final decision.

See this case study: Guiding system selection in the aviation sector

5. Implementation

Once a change is funded and planned, the real work begins. Implementation needs structure, sequencing, and the right people at the right time. It also requires a plan for how people will adopt the change.

For example, we supported a global payroll separation programme across 80 countries. The detail required was significant. The team created a plan that ensured every payroll was transitioned without missing a pay cycle. In another case, a client struggling with system adoption saw usage increase sixfold after we revised the implementation approach and refocused change activity.

Sometimes implementation means building new capabilities in-house. We have helped clients set up shared services, Centres of Expertise, or PMO functions to carry transformation forward.

See this case study: Consolidating global payroll systems for Kyndryl

And this case study: Helping Pandora make a success of SAP SuccessFactors

6. Post-implementation support

Going live is not the end. It is the moment when reality sets in. Systems need to be supported, processes need to evolve, and people need to stay engaged.

We often help clients assess whether benefits have been realised, provide extra support while new teams find their feet, or source expertise to run key systems. In one case, we partnered with a client long after their Workday system went live, helping them extract more value through structured support, training, and planning.

See this Preos case study: The IFCO Journey with Workday Enhancement Services

7. Optimisation

Sometimes, replacing a system feels like the only option. But is it? Before investing in something new, it is worth exploring whether the current solution can be improved.

For a healthcare provider using a basic version of Workday, we helped identify ways to tailor the system more effectively to their needs, avoiding a costly re-implementation. For a car hire firm struggling under the weight of rapid growth, we reviewed 80 processes and provided the internal team with a clear improvement plan.

See this case study: Helping Zipcar accelerate into new markets with operational effectiveness 

8. Extending scope

Initial transformation efforts often focus on a specific geography or function. But as the organisation evolves, there may be a need to extend that change.

When a fashion retailer needed to roll out its new HR system from the US to Greater China and Australia, we supported both technical configuration and local engagement. A cookie-cutter rollout would not have worked. Understanding local practices made the difference.

See this Preos case study: How Capri schieved a 97% Workday adoption rate in China

9. Change management

No transformation succeeds unless people make it real. The more a programme depends on new behaviours, the more change management matters.

At Change Associates, this is core to our work. We do not bolt on change at the end. We help embed it from the start. For one automotive client, this meant supporting franchise dealers across the UK to understand, own, and implement a new customer experience strategy.

See this case study: Transforming customer experience in a major car retailer

Ten things we’ve learned about transformation

If you’re thinking about where to start, here are some principles we’ve seen make a real difference:

  1. Diagnose before you deliver: Rushing into action without understanding the issue wastes time and money. A good diagnosis saves both.
  2. Design with purpose: Whether it’s structures, processes or systems, make sure the end state is clear before you begin the work.
  3. Make the case: A solid business case helps get buy-in, set expectations, and clarify what success looks like, financially and beyond.
  4. Choose tech with care: The right tool matters. So does the process you use to choose it. Take your time, test assumptions, and don’t fall for the demo.
  5. Execution matters: Plans don’t deliver themselves. Make sure you’ve got the right people, the right sequence, and a clear view of adoption.
  6. Going live is just the start: Every new system or process needs time to bed in. Expect issues, plan for support, and keep listening to users.
  7. Don’t always rip and replace: Sometimes improvement beats reinvention. Optimising what you’ve got might give you more value, faster.
  8. Keep evolving: Transformation isn’t a one-off. Priorities shift. Keep building the internal capability to adapt, improve, and respond.
  9. People make it real: Change doesn’t work without engagement. Bring people with you from the start — and keep them with you all the way through.
  10. Simplicity beats complexity: Big ideas need clear steps. Avoid overengineering; the best solutions are often the most straightforward.

So, where does this leave you?

Transformation is not a single decision. It is a pattern of adjustments, choices, and commitments over time. Whether you are rethinking your strategy, fixing broken systems, or just trying to make things work better, the question is the same: where should we focus first?

You might recognise one or more of the scenarios above. If so, we hope this blog has helped you think more clearly about what transformation might look like in your context.

If you want to talk your transformation through, we are always happy to help.

contact us
Helena Miles