Simple rules for digital transformation

Mark Aikman • July 15, 2020

The four key questions to ask

I’ve spent my entire career in transformation. And I’m beginning to notice that in many ways, it’s getting simpler, rather than more complicated – I now recognise the key features on which the success of any programme depends. So to keep focused, I’m currently running transformation programmes in response to just four very specific questions:


1) Is our vision one that everyone can believe in?

Bottom line: there’s no success without vision and delivery. But large bespoke digital transformations can take a long time and are incredibly complex. They contain an infinite number of opportunities to become side-tracked. They can be hijacked by ever-changing technologies; they are often subject to organisational regime changes; and they serve colleagues with widely differing priorities.

I’ve learned that it’s critical to solidify the vision of what we want to achieve – and do this very quickly. It’s then essential to create a simple message about the vision that people can remember; and which makes the benefits of the programme crystal clear. Then, everyone working on the programme will have an easy-to-remember yardstick that will help them decide on whether something is a necessity or a priority – instead of just a nice-to-have.

When you have intelligent and capable people who understand and rate the vision, they do not need anyone to tell them every day precisely what to do. These people will feel that they are making a contribution and that they have opportunities for creativity and autonomy. They experience the satisfaction of being both permitted and encouraged to think for themselves.

Therefore, a clear vision and understanding of the benefits of the programme will encourage better and quicker decision making; reduce wasted effort; and create a productive and engaged delivery team.


2) Are we responding quickly to what the customer now wants?

In commercial organisations, the customer needs to be the central point of focus. Obvious enough. But in digital transformation, this has to be coupled with a rapid response to that customer’s ever-changing needs. And those needs do change quickly – for example, nobody knew they needed a app to call a cab instead of making a phone call, until Uber showed them how handy it would be….

So the customer needs to be central. We need accurate information, constantly updated, on what the customers are thinking. And the transformation activity needs to be buzzing around these views and needs, working very quickly and nimbly.

Clearly then, waterfall development, with the supplier sitting way outside the business and producing phased development that takes weeks or months, is probably dead and cremated. Agile and hybrid development are a much better option, as these methods are closer to the customer and quicker to make responsive progress. This rapid development will be successful, as long as the vision is clear, and everyone is conditioned to repeatedly ask……


3) Is it really right for this business?

Successful innovation isn’t always about the bleeding-edge. Of course, everyone wants to out-run obsolescence but it’s essential not to be diverted by hot-off-the-press technologies and solutions. They’re sexy, sure – but are they what this business really needs?

I learned early that the newest solution isn’t by definition the best. Instead, it’s essential to balance the technology specification, design and build against those business benefits we truly need. So if the business needs bells but not whistles, I’ve always taken care not to get distracted by using whistles, just because they’re there.

My rule for selecting technology has been: does it benefit the customer? If it doesn’t benefit the customer directly, does it help the smooth running of the business (which in turn will benefit the customer in the long run)? This question-sequence has always been invaluable in helping select a suite of technologies that perfectly fit the programme’s stated needs.


4) How is everyone feeling about the programme today?

Finally, back to people. We started by ensuring everyone bought-into the vision. But we can’t just wash our hands of them once they have an understanding of the vision: we have to bring them along through the whole experience too. As everyone knows, significant change of any kind can be a challenging and often even a threatening experience. And most people don’t react well to being threatened!

So Question 4 ensures we keep a keen eye on how positive and engaged people are, 24/7. We have to have everyone firmly on the bus to achieve programme success.

In a digital transformation, there is a very important virtuous circle that can very easily become a vicious circle. It’s the relationship between digital change and cultural change. Digital change absolutely inevitably forces cultural and behavioural change on the organisation’s people – things are just plain done differently. But equally, cultural change will be needed if the digitisation is to become wholeheartedly adopted.

So we need continuous work to keep all the people keen on the digital improvements we’re making. That means every programme needs massive effort directed towards building and maintaining workforce engagement. And so, speaking from the viewpoint of a CIO, I will always believe that communication is more important than technology…

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