Objective perspective

Mark Aikman • February 23, 2021

How do you restart a stalled transformation?

We’re all sick to the furry little mintballs of hearing the line: “80+% of all transformations fail”. Clearly, transformation isn’t easy, but in IT, we do rather surround major change with an air of always-doomed-from-the-start gloominess. I think we should shift our perspective to be more on the lines of “80+% of transformations stall” – and then have a long hard look at why this is the case. For me, there’s one very clear answer.

I’ve looked at the ways in which transformations can go wrong. Typically, they hit the buffers when:


  • They become extremely complicated, with multiple strands all developing at once and competing to be the priority workstream, with nothing being completed due to thousands of demands on capacity
  • The senior team gets cold feet at the cost/time it will take/direction of travel
  • Sub-teams are developing disconnected standalone projects within the overall programme
  • A catalogue of mission creepage – sometimes going back years – has changed the content of the programme beyond all recognition
  • And as for culture… well, it can be broken, bullying, bullish or backbiting…

In some stalled transformations, you’ll see all of the above. By the shedload.

There’s a very simple starting point which will begin to address all the above problems; refocus everyone; and restart the programme. You just revisit the programme objective.

Successful programmes depend on there being a clearly stated objective. This needs to be simple; agreed, believed and sponsored by the leadership team; and oft repeated.

The programme objective is the yardstick by which any activity is ruled in or out. By making the objective clear and memorable, it becomes the litmus test by which anyone working on the programme can judge whether or not to pursue any particular activity.

So for example, if your programme objective is “to merge two operational systems after an acquisition”, everyone will know what we’re trying to do. Therefore, if only one of the original companies had a CRM system, there’s no excuse for the Marketing Department to try to sneak in a cheeky CRM upgrade - because no merging is required. It’s add-ons like these, the might-as-well-do-it-while-the-bonnet’s-ups, that cause chaos, confusion and creep.

Keep the objective as simply worded as possible: e.g. “to separate”, “to replace” or “to make more secure”. Avoid woolly stuff – e.g. “to enhance customer experience” – because people can make anything fit inside the transformation remit if it’s open to interpretation. You’ll meet people who will argue that upgrading payroll software enhances customer experience, because it frees up capacity in Finance for improved invoice checking!

Most “failed” transformations are just “stalled” or “over-complicated” exercises, and therefore most can be stripped back and restarted. Ignition Transformation’s Blue Light service can bring an objective perspective and support you to get back on track – see more at:

https://www.ignitiontransformation.co.uk/problems-we-solve-getting-back-on-track

May 9, 2025
Many companies initially believe they can handle complex ERP implementations internally. After all, who knows their business better? Grant du Preez of Ignition Transformation looks at what to consider before deciding to go it alone: and he’s a guy who’s seen all the elephant-traps. He advises:  Don’t underestimate how complicated it will be Enterprise Resource Planning implementations are challenging under normal circumstances. When layered onto major business transformations like carve-outs or mergers, they become exponentially more complex. These scenarios introduce unique challenges, such as: · Multiple legacy systems that must be harmonised · Interdependent business processes needing careful redesign · Data migration requiring deep technical expertise · Compressed timelines driven by business imperatives · Organisational resistance amid broader change And all that is needed simultaneously… At best you might see missed business opportunities if you can’t make the speed: at worst, you’ll spend too much or possibly even see a failed implementation. Remember Transition Service Agreements (TSAs) are real rules TSAs present some of the most significant challenges during carve-outs and acquisitions. These agreements typically impose strict and legally-binding deadlines for transitioning from parent company systems. There are substantial financial penalties for delays. Hard cash. To work within TSAs, you will need: · Proven strategies for meeting TSA deadlines · Templates for identifying and prioritising critical path items · Tactics for negotiating more favourable terms when necessary · Experience balancing short-term TSA requirements with long-term system needs It’s a Matterhorn-steep learning curve if you haven’t done it before. Make sure you have just one source of truth During business transformations, competing narratives inevitably emerge. Typically, there are strands on requirements, data structures, and implementation approaches. It soon becomes 3D chess. You will need to establish what we call a "single source of truth" – authoritative references for decisions that prevent revisiting settled issues. This includes: · Documented design decisions with clear ownership · Master data governance frameworks · Process models validated by business owners · Requirements traceability matrices Without this discipline, projects often circle Heathrow, cycling through the same decisions repeatedly, wasting valuable time and resources. You need to know what’s going on You will need complete transparency across all aspects of an ERP programme. Every day, you have to be in a position to give your stakeholders an unvarnished view of: · Project status against critical milestones · Resource allocation and utilisation · Emerging risks and mitigation strategies · Budget consumption and projections This transparency creates accountability and enables early intervention when issues arise. But it can’t be a hefty administrative burden that slows progress. Get the top corridor on board You will need to secure the right level of commitment from organisational leadership and key stakeholders. You will have to be clear about the specific involvement needed at different stages. Most importantly, you will need to be listened-to when you communicate these needs to busy executives. Executive steering committees, dedicated business process owners and carefully structured sign-off procedures will help ensure decisions are made by the right people at the right time. Without this orchestration, ERP implementations often stall waiting for critical decisions or proceed with insufficient business input. Remember DIY may only LOOK like the cheaper option Whilst engaging experienced consultants requires investment, the return is substantial. Looking at dozens of implementations we've led or observed, those with experienced consultants consistently: · Complete on time or with minimal delays · Stay closer to budgeted costs · Deliver more of the promised business benefits · Create less disruption to ongoing operations Organisations embarking on ERP transformations during carve-outs, mergers, or other significant business changes face a choice: invest in experienced guidance upfront or pay far more in delays, overruns, and missed opportunities later. DIY-er, beware!
May 7, 2025
Five questions to ask providers of business transformation programmes
By Mark Aikman November 7, 2022
How to write reports that busy people will read
By Mark Aikman March 7, 2022
Thanks to our good friends at Future Processing for inviting us to make a guest appearance! On their blog, I've shared some ideas about what to consider in order to get best-fit suppliers: https://www.future-processing.com/blog/selecting-a-supplier-natural-selection/
By Mark Aikman October 19, 2021
IT's supplier relationship need to stop using the master-servant model. Partnership gets more done - and to a much higher standard.
By Sharon Gregory September 7, 2021
Ideas for analysing and dealing with resistance to change in transformation programmes
By Mark Aikman August 10, 2021
Considerations when transitioning from development to BAU
By Mark Aikman July 20, 2021
Support for surviving and thriving after the pandemic from Ignition Transformation
By Mark Aikman July 8, 2021
Three different leadership styles to steer you through a crisis
By Mark Aikman July 1, 2021
How to have better and/or fewer meetings
Show More