What we help with
Every organisation’s situation is a little different, but the same themes come up again and again. Here is how we think about three of them.
Transformations
Transformation is hard to get right because it touches everyone, and everyone is also busy doing their day job.
Start with the people at the top
Transformations go well when leaders pull in the same direction and say the same thing. If the chief executive talks about transformation while somebody senior still asks for the old reports, the whole thing quietly fades. People also need to feel change happening around them, not just read about it in a monthly email.
Expect it to land in waves
Change rarely hits everyone at once. Sales might move first, operations follow as the results trickle through, with technology underneath it all. Keep everyone in the loop on what is changing and what you are learning, even when a change is not theirs yet, so they can see that things are moving.
Time the story carefully
If you tell someone they are about to be hit by a car ten times and it never arrives, they stop believing you by the tenth. For the programme team, transformation is the whole job. For someone in operations, it may not touch them for years. So do not announce a grand transformation while you are still in the strategy phase. Build the story as the impact gets closer.
Pick a destination, then work back
A good roadmap describes where the organisation needs to be, and by when. That horizon is whatever the change naturally calls for: two years for a focused programme, perhaps ten for a huge overhaul, or set by something outside your control, like a system going out of support. Then break it into sensible interim stages, so you can miss a milestone, replan and recover long before the finish line.
Make each stage visible with a target operating model
For each stage, describe what the organisation looks like: systems, data, processes, people and structure. It shows you do not have to change everything at once. You might modernise a system first and add some AI support, leaving processes and structure alone. That puts you in a good place to rebuild the processes, and then the organisation around them. If AI takes over the monthly reconciliations, for example, the job becomes oversight, and you can redeploy that time or adjust the team.
Developing new services
A new service is exciting, and it nearly always takes more effort than anyone expected.
Count the real cost of change
Budgets usually cover the system and any outside help. They often miss the time your own people spend, and the drag on the teams they are pulled away from. If you have not built the capability to deliver change, you end up borrowing it from operations and management. That works for a while, then it hurts. Plan for it up front.
Governance: only what you need
Good governance means different groups each answering a different question: is this the right thing to do, is the technology fit for purpose, can we maintain it, does the business case stack up. That is healthy. The trouble starts when layer after layer of seniority asks the same question in turn. Each layer adds weeks without adding insight. Have the governance you need, each piece with a clear job, and no more layers than that.
A small team with the right skills
The fastest way to launch something new is usually a small, dedicated team inside the organisation, with the right skills pulled in from finance, commercial, supply chain, technology and operations, full time or part time, reporting straight to a senior sponsor or investment board. It costs your organisation some people’s time, and it pays back by catching dependencies before they bite.
Start smaller than you want to
Most people want to launch the beautiful, finished thing on day one. Try a prototype, a trial, or a simpler version for the customers who are easiest to serve, and build out the complicated versions afterwards. Break the work into use cases and build only what day one needs. It may be a bit rough at first, but it gets you live, buys breathing space and builds momentum.
Keep invested people close
When your stakeholders are already invested, whether that is government, investors or a board, you do not have to win them over. Your job is to keep everyone travelling the same road, in the same direction, at the same speed. That does not need heavy reporting. Share what you are working towards, how you are getting there and what you are learning along the way. Then if the plan shifts, they have come with you. And if something starts to slip, tell them early, before they hear it somewhere else.
Turnarounds
Turnarounds rarely announce themselves.
What it looks like from the inside
You do not often hear “we are three months late”. You hear that the plan has been re-planned, and then re-planned again. Delivery teams are stressed and unsure. Bad news does not reach governance, because the last person who brought it was turned away. Leadership ends up with one picture while the team on the ground sees another, and the wider business is told the leadership version. Small issues turn into blockers because the list of unresolved ones only ever grows.
Make it visible
The first job is a difficult conversation with leadership and governance: this is not working yet, and here is why. We frame it as “what is blocking the outcomes?”, never “who has not delivered?”. You cannot fix a problem until everyone can see it, and broadly agrees what it is.
Decide what to flex
Once it is visible, you decide what gives: scope, timeline, cost, quality or the work products themselves. Usually it is a combination, and usually it is more than one. It is far better to choose than to pretend nothing has to give.
Unblock in slices
Sometimes the answer, at least for a while, is to take a chunk off a big waterfall programme and deliver it iteratively, so some value lands and the pressure eases. It does not always work, but it often helps.
Face the big structural things
Every programme has a few dependencies that everything else hangs off: long-term funding, policy direction, a major system implementation. Build the plan around them. If a big technology rollout is already overrunning, ask honestly why. Maybe the processes do not fit the system, maybe there is a capability gap, maybe the business is too busy to engage, or maybe the designs for finance, logistics and operations do not join up. None of that is about blame. It is about finding what stands between you and the outcome.
Sound familiar?
Whether you are planning something new or trying to rescue something in flight, we would be happy to talk it through.