Customer interface

Mark Aikman • June 8, 2021

Tips for risk-reduced customer involvement in transformation design

We all know now that the customers, or “service users”, or whatever you call the people who need the outputs of your organisation, should be the key beneficiaries of your Programme. I’m always banging on about the importance of collecting their views and requirements.

But risk creeps in very quickly around the topic of “customers”. Here are some tips for handling the challenges of getting the customers’ views first-hand:

G atekeepers

The first problems arise if other parts of the organisation become protective about customers: “They’re ours” say Sales. “If you lot talk to them, you’ll only go and upset them.” That might be Sales or another part of the organisation - typically, gatekeeping comes from the department that usually speaks directly to your customers/service users.

These people are right, of course, to an extent. It is a very dainty path you need to walk to discuss your offer with customers without inviting criticism or raising expectations you cannot fulfil. You shouldn't do it: it's a definite case of Do Not Try This At Home.. But equally, Sales shouldn't do it either. You are going to need Professional Listening to do this.

To gather customers' views using facilitated customer interviews or focus groups, I would always advise using experienced professional intermediaries. They will have the conversation with representatives of the customer base on your behalf (btw: Ignition Transformation has talented people who can do this for you). These people will be skilled at not judging, agreeing or promising. But you’ll still need to sell that idea to Sales.

So involve Sales – or any other resistant colleagues – in the discussions about how the customers will be approached and reassure them about how expectations will be managed. Be entirely transparent about what will be discussed and what will happen if customers express negative opinions or frustration. Persuade them of the benefits of being seen to listen to the clients. And always, before you approach any customers, make sure any resistant colleagues are on your bus.

Over-promising

Other customer-centred problems can arise when you are using particular delivery methods. Imagine the scene: you consult with the customers; they state their expectations; you assure them that these can be included in your programme, almost immediately. Everyone gets very excited. Fireworks, champagne, rejoicing.

And then, on reflection, you select a waterfall development mechanism with the supplier sitting way outside the business and producing phased development that takes weeks, or months, or even years. Customer delight = zero.

This isn’t necessarily solved by changing your delivery method to suit one stakeholder – yes, agile delivery may produce quicker visible results, and that would be attractive here. However, you nonetheless need to balance your decision with other significant considerations (e.g. budget, culture, capacity) and use the method that’s best overall for your stated purpose. So if it’s going to be a while, you need to manage customer expectations throughout the build. You need to do so right at the start – when you’re gathering their ideas - and then all the way through the process as you develop a solution. And again, Do Not Try This At Home. Instead, ask your Communications Team to set up a plan with Sales on how we keep customers excitedly patient. And that way, everyone stays in the loop...


This is based on an extract from Mark Aikman’s book Uncommon Sense: Alternative Thinking on Digital Transformation

Amazon location: https://www.amazon.co.uk/Uncommon-Sense-Alternative-Thinking-Transformation-ebook/dp/B08KSG513Q

Apple location: https://books.apple.com/gb/book/uncommon-sense/id1536877985

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