Driving Cloud Transformation via CAF Alignment

Overview

One of the biggest challenges in consulting is that recommendations can quickly become framed as personal opinion. Phrases such as “I think” or “in my view” can unintentionally open the door to long discussions, disagreement, and internal friction - particularly when the recommendation involves costly improvements, platform changes, or cloud migrations.

In my work across Databricks and Azure infrastructure, I found the Microsoft Cloud Adoption Framework particularly useful for avoiding this. Rather than positioning recommendations as subjective advice, using existing frameworks allowed me to anchor conversations in established guidance, proven patterns, and recognised cloud adoption principles. This helped shift discussions from personal preference to objective assessment, making it easier to build trust and focus on delivering change.

The Cloud Adoption Framework does what it says on the tin: it provides a structured approach for scaling cloud adoption across an organisation. One of its most useful concepts is the identification of anti-patterns — common behaviours, processes, or architectural decisions that can limit return on investment from cloud platforms. These anti-patterns are especially powerful in client conversations because they provide a neutral way to highlight issues: “Here is the pattern we are seeing, here is why it creates risk or inefficiency, and here is the recommended path forward.”

This approach was particularly effective in the early stages of client relationships. By identifying low-hanging fruit and framing improvements through recognised cloud guidance, we could build credibility quickly and demonstrate value without appearing critical or opinion-led.

At 4most, many of our conversations naturally started at Chief Risk Officer level. This was valuable, but we also wanted to engage with the stakeholders responsible for broader cloud strategy and implementation. The Cloud Adoption Framework provided a useful route into those conversations through the concept of a Cloud Centre of Excellence, or CCoE: a cross-functional team responsible for governing, guiding, and accelerating cloud adoption across an enterprise.

Where a CCoE already existed, it created a natural forum for discussing cloud maturity, governance, data platforms, and implementation challenges. Where one did not exist, recommending the creation of a CCoE became a constructive way to help the client improve their cloud operating model. Importantly, asking “Do you have a Cloud Centre of Excellence we could speak with?” landed very differently from simply asking for access to the CTO. It positioned the conversation around governance, alignment, and best practice rather than sales or escalation.

Through these conversations, we were able to move beyond our initial risk-focused engagements and build relationships across the wider technology organisation. By using established frameworks, identifying practical anti-patterns, and building trust early, we positioned ourselves as a credible cloud implementation partner rather than just an external consultancy.

Pushing back against a clients requirements is another way to build an empowering relationship. A client came to us with a clear ask: they wanted Gen AI built into their platform. Rather than taking the brief at face value, we challenged the requirement - and what emerged was a far simpler, far cheaper solution that actually solved the problem. The real need was text-to-SQL: the ability to query data in plain language without writing code. Built on Databricks Genie with a clean, purpose-designed table structure, the solution was delivered in a matter of days at a fraction of the cost of a full Gen AI implementation. The ROI was immediate and tangible. The willingness to push back — to sell what the client needed rather than what they asked for — is what built trust effectively. It demonstrated that our goal was the right outcome, not the largest engagement. This decision enabled us to build a long standing relationship with this client as opposed to a one-off engagement.

Key Achievements