Maturity

Most organisations are drowning in cloud data and starving for cloud insight. They have dashboards full of metrics, and yet leadership still can’t confidently answer whether the cloud investment is wise. The data is abundant. The meaning is missing.

This is one of the most common and most frustrating states in enterprise technology finance, and it has a clear diagnosis. The organisation has climbed the first rung of a ladder and mistaken it for the top. There is a well-understood progression from raw data to genuine wisdom, and cloud financial intelligence has to traverse all of it. Each rung requires the one below, and skipping rungs is impossible, no matter how good the tooling.

The DIKW ladder, applied to cloud spend

The progression from data to wisdom is a classic framework, and it maps remarkably cleanly onto cloud financial management. Each stage answers a progressively more strategic question.

• Data answers: What did we spend, where, and when?
• Information answers: Which team or product is driving our spend?
• Knowledge answers: Why are costs changing, and what drives them?
• Wisdom answers: How do we maximise value and invest wisely in cloud?

The trap is that the first stage is the easiest to reach and the most seductive to mistake for success. A dashboard full of spend metrics feels like financial intelligence. But answering “what did we spend” is table stakes. The value lives at the top of the ladder, and getting there is most of the work.

Let’s walk each rung.

Stage 1: Data

The foundation is data: the discrete, objective facts about cloud consumption. This is the what, where, when, who, and how many of spend:

• What you spent — spend, usage, rates, tags.
• Where — which accounts, regions, and services.
• When — hourly, daily, monthly.
• Who — which cloud resources and teams?
• How many — usage units, gigabytes, instance-hours.

The work at this stage is aggregation, tagging, and visualisation, collecting the raw facts and rendering them legible. This is necessary and non-trivial; you cannot build anything without it. But it is also where most organisations stop, because a well-built dashboard of these facts looks complete. It isn’t. It’s the floor, not the building.

The tell that you’re stuck at the data stage: you can produce any chart of spend anyone asks for, but every why question requires a manual investigation, and every strategic question gets a shrug.

Stage 2: Information

Information is data with analysed relationships and connections. This is where raw facts become structured insight by being organised, normalised, and related to the business.

At this stage, you produce:

• Normalised cost views — spend reshaped into consistent, comparable structures rather than raw provider output.
• Owner mapping — costs attributed to team and business-unit owners, so spend has a who in business terms, not just resource terms.
• Business-service context — spend located within the business services it supports, not just the infrastructure it ran on.
• Reporting-period alignment — costs organised into the periods finance actually uses.
• Correlation to business activity — the beginning of connecting spend to what the business was doing when it occurred.

The defining capability of the information stage is cost-to-value metrics and the first real unit economics, rather than infrastructure facts. The question this stage answers is the first genuinely useful management question, because it’s the first one with an owner attached.

The tell that you’ve reached the information stage: you can point at any cost increase and immediately name the team, product, or service responsible, without a manual investigation.

Stage 3: Knowledge

Knowledge is contextual understanding, the stage where you don’t just see that costs changed but understand why, and what drives them.

This stage is owned by the people who connect spend to business reality: product owners and finance partners. The questions it engages are causal and forward-leaning:

• Why are costs changing — what’s the root cause behind a variance?
• When — understood through forecast-versus-actual cycles, so deviations are seen against expectation.
• How — through continuous optimisation and forecasting, so the understanding is dynamic rather than a one-time analysis.

Knowledge is where variance analysis matures from “spend went up 15%” to “spend went up 15% because customer transactions grew 25%, so cost-to-serve actually improved.” It’s where forecasting stops being a static budget and becomes a living comparison against which reality is interpreted. It’s the stage where the organisation can explain itself, to the board, to auditors, to its own leadership, with causal confidence rather than after-the-fact rationalisation.

The tell that you’ve reached the knowledge stage: when a cost moves, you can explain the cause, place it against your forecast, and say whether it’s good or bad news,  quickly and with evidence.

Stage 4: Wisdom

Wisdom is understanding applied to decision-making. The audience here is the most senior: CFOs, FinOps leads, and executives. The question is the one that matters most: how do we maximise value and invest wisely?

The output of the wisdom stage is decisions, specifically, decisions on architecture, commitments, and AI optimisation:

• Architecture decisions informed by the true cost-to-value of different approaches.
• Commitment decisions — how much to commit to multi-year cloud agreements informed by reliable forecasts and a clear view of consumption trajectory.
• AI optimisation decisions — where to invest in AI, which models are worth their cost, how to scale,  informed by AI unit economics and tokenomics.

Wisdom is enabled by continuous optimisation and forecasting, feeding strategic business alignment. It’s the stage where cloud spend stops being a cost to be explained and becomes a lever to be directed, where finance and technology leaders make confident, forward-looking investment decisions because every rung below them is solid.

The tell that you’ve reached the wisdom stage: leadership makes major technology investment decisions, commitments, architecture, and AI scaling, with confidence, citing cost-to-value evidence rather than instinct.

Why you can’t skip rungs

The most important property of this ladder is that each rung depends on the one below. This is why buying a sophisticated forecasting tool rarely delivers wisdom to an organisation still stuck at the data stage — the tool has no solid information or knowledge layer to stand on.

• You can’t reach information without clean, well-structured data. Attribution to owners requires reliable underlying facts.
• You can’t reach knowledge without information. You can’t explain why costs changed if you can’t first see which team or product they belong to.
• You can’t reach wisdom without knowledge. You can’t invest wisely if you can’t explain what drives your costs and how they track against the forecast.

This dependency is liberating as well as constraining. It means the path is clear: there are no shortcuts, but there is a defined sequence. An organisation that knows it’s stuck at the information stage knows exactly what to build next (the knowledge layer), rather than chasing a wisdom-stage capability it isn’t ready to use.

Using the model in practice

The maturity model is most useful as a diagnostic and a roadmap.

As a diagnostic, it tells you where you actually are, not where your dashboards make you feel you are. Run the tells: Can you explain every variance causally? You’re at the knowledge. Can you only produce charts? You’re at data, regardless of how good the charts look. Honest placement is the first step.

As a roadmap, it tells you what to build next. The next rung is always the priority, because skipping it is impossible. If you’re at data, invest in attribution and normalisation to reach information. If you’re at information, invest in variance analysis and forecasting to reach knowledge. If you’re at knowledge, invest in the strategic decision tooling that turns understanding into wise investment.

As a shared language, it gives finance, FinOps, and engineering a common way to talk about maturity. Instead of vague debates about whether the cloud-cost program is “good,” the conversation becomes specific: which rung are we on, and what does the next one require?

The bottom line

The goal of cloud financial intelligence was never to produce metrics. Metrics are the raw material. The goal is meaning, the kind of understanding that lets an organisation invest in cloud and AI wisely, with confidence rather than guesswork.

That meaning is reached by climbing a ladder: from the discrete facts of data, to the related context of information, to the causal understanding of knowledge, to the strategic decision-making of wisdom. Each rung requires the one below, and most organisations are further down the ladder than their dashboards suggest.

The organisations that win at cloud finance aren’t the ones with the most metrics. They’re the ones who climbed all the way to meaning, and who make every major decision from the top of the ladder, where the data finally makes sense.