When I was in Malaysia recently, someone from a Digital Transformation Team at a large company asked me:
“How do I convince my boss to accept a move to the cloud?”
This isn’t hyperbole. It’s a real question I got asked. And you might be surprised to hear that question from a Digital Transformation team who need to…transform digital? But this is such a common struggle for people in large companies, particularly in the energy industry.
And actually it does make sense. The team on the ground see the benefits of cloud in their everyday work. Flexibility, scalability, speed, cost. But often they are held back by leadership who are cautious, sceptical, and sometimes outright hostile to the idea. In a legacy industry such as energy and in markets where data residency laws and regulatory complexity create real concerns, this probably shouldn’t have surprised me as much as it did.
So, how do you make the case for cloud when the person you are trying to influence does not “get it”?
Understanding the fear
First, let’s acknowledge that the fears are real. Data residency is a legitimate issue in many countries. Leaders worry about security breaches, loss of control, and being locked into a vendor. They also see headlines of failed cloud migrations and do not want their name attached to the next one.
Like with anybody you are trying to convince, dismissing their fears does not work. You need to respect them, then show a path forward that manages risk rather than ignoring it.
Why leaders resist
Most objections to the cloud come from three places:
- Legacy mindset (“If it isn’t broken, don’t fix it”)
- Risk perception (cloud feels unsafe because it is unfamiliar)
- Lack of experience with cloud (many senior leaders built their careers on-premise, so cloud is outside their comfort zone).
This is why presenting a new tool or platform rarely gets traction. You need to translate the technology into language leadership understands. And that is the business impact.
One framework that helps here to show you understand the risk is the Problem → Impact → Solution → Risk → Mitigation framework. Instead of talking about “containers” or “latency,” frame your pitch like this:
Problem: “Our reporting takes three weeks.”
Impact: “That means executives make decisions on out-of-date data, which slows production and costs us money.”
Solution: “Cloud automation could cut that to hours.”
Risk: “Migration could cause temporary disruption.”
Mitigation: “We can run a pilot in parallel before switching fully.”
This approach shows respect for the leader’s concerns while offering a balanced, business-first argument.
Cut the noise!
Too often, cloud conversations get bogged down in jargon. Leadership does not care about “serverless architecture.” They care about outcomes. So the goal here is to cut the noise! Faster response to regulation changes. Lower total cost of ownership. Cloud is a means to those ends.
It also helps to present decisions using the ROI + Risk equation: What do we gain if we move? What do we risk if we do not? Often, the risk of staying put, rising maintenance costs, growing security exposure, outweighs the perceived risk of moving.
Sell painkillers, not vitamins
This is where the 3P’s come in. Pain, Proof, Pilot.
Pain: Start with a business problem your boss already feels. Maybe compliance reporting takes too long, or IT spend is spiralling.
Proof: Bring evidence and show what competitors or peers have achieved. Share industry benchmarks.
Pilot: Do not ask for a wholesale move. Ask for permission to try one small, low-risk project and measure results.
And do not underestimate the power of storytelling. Analogies often work better than arguments. Like “We don’t build private roads to get to work, we use the shared infrastructure that’s already there. Cloud is the same idea for computing: shared, reliable, always maintained.”
Build allies before the pitch
In most companies, your boss is not the only gatekeeper. Finance, procurement, compliance teams, and operations leaders all influence the decision. If you only focus on the person at the top, you are likely to hit a wall. This is where stakeholder mapping comes in. Ask yourself who benefits if this change succeeds and who might block it? Who has the most sway with decision-makers? Then build allies in advance. If the CFO already buys into the cost savings, your boss is less likely to shoot the idea down.
Equipping yourself for the conversation
When you do get in front of leadership, make it easy for them. Do not bury them in technical detail. Tie every point back to business goals. One tool that works is the One-Page Business Case. Distil your pitch into a single sheet:
- Problem
- Cost of the status quo
- Solution
- ROI and risk
- Pilot proposal.
This shows you have thought through the essentials, and it respects their time. You can leave it behind after the meeting, and it stands on its own without you there to explain it. You can go into more of the details we explained above during the meeting.
Take the first step
You do not need to win the whole argument on day one. Start small. Build evidence. Let results speak louder than PowerPoints. Cloud conversations are rarely about technology alone. They are about trust, risk, and control. When you show you understand those concerns, and when you can frame cloud as the safer, smarter, more resilient choice, you give your leadership permission to take the next step.
If you are struggling with an old-school leader who just does not “get it,” you are not alone. In energy, that resistance is common. Do not just tell them cloud is the future. Show them the pain it solves, prove it works, and pilot something small. Translate technology into business language. Respect the fear, then show a practical way through it. And make the change!
