AI is not the starting point. Analytics is. And for most organisations, getting that order wrong is the single biggest reason AI projects disappoint.

Every week I’m pulled into conversations framed as “AI strategy” that are, in reality, data and analytics problems in disguise. Beneath the ambition — copilots for sales teams, chatbots for customer service, predictive maintenance on the shop floor — you usually find the same things: siloed application data, legacy warehouses built for yesterday’s reporting, data lakes that became data swamps, and spreadsheets filling the gaps.

Until those foundations are solid, AI won’t fix the problem. It will just produce more sophisticated confusion.

This first post in the series makes that case explicitly. Before we argue warehouse vs lake vs lakehouse, we need a shared view of how analytics underpins decision-making — and how AI builds on, not replaces, that foundation.

The analytics spectrum: a ladder, not a leap

Most organisations jump straight to AI use cases while still struggling with the basics. It helps to think of analytics as a spectrum, where each stage depends on the one before it.

Descriptive – “What happened?” Reports, dashboards, KPIs. Revenue by region, tickets by channel, machines that failed by shift. This is where most business decisions are still made today, and where most organisations need the most work.

Diagnostic – “Why did it happen?” Drill-downs, cohort comparisons, root-cause analysis. Why did returns spike in that region? Why did NPS drop after the launch? This is where data moves from a record of events to an explanation of them — and many “analytics projects” live here, without any AI in sight.

Predictive – “What is likely to happen?” Now we step into data science: demand forecasting, churn prediction, time-to-failure estimates. Classical ML techniques — regression, classification, time-series models — let businesses anticipate outcomes and act before issues hit.

Prescriptive – “What should we do?” From prediction to recommended action. Given stock levels, demand signals, and lead times, what’s the optimal replenishment plan? This is optimisation, simulation, and decision engines — again, often without a single line of GenAI.

AI and GenAI – “What can we automate, augment, and generate?” Finally, AI on top of that foundation: ML models embedded in workflows, copilots that explain performance, RAG systems that answer questions over enterprise data. Powerful — but only as powerful as the analytics beneath them.

The dependency chain matters: weak descriptive and diagnostic analytics produce weak predictive models. Weak analytics produces AI that surfaces those weaknesses faster and at greater scale.

What this looks like in practice

Manufacturing: the cost of skipping the basics

A mid-sized manufacturer wanted ML-based predictive maintenance. Reasonable ambition. But when we dug in, OEE dashboards didn’t exist, downtime wasn’t being captured consistently, and maintenance history lived in three disconnected systems. There was no foundation to train a model on — and no way to validate one if you did.

The right first move wasn’t a model. It was centralising OT data from IoT sensors, PLC logs, and work orders, then building basic descriptive analytics: downtime by line, scrap rates by batch, top failure modes by site. That work alone drove measurable improvements. Statistical MTBF estimates followed. ML-based failure prediction came later — and actually worked, because the data beneath it was trusted.

The lesson isn’t that AI is bad. It’s that the sequence matters.

Retail: analytics as the backbone of personalisation

In retail and e-commerce, AI gets a lot of credit for personalisation — but the analytics layer does most of the heavy lifting. Sales trends, basket analysis, promotion effectiveness, seasonality-aware forecasting at category or store level: these are all analytically tractable problems that don’t require a foundation model to solve.

ML propensity models and recommendation engines amplify that foundation. GenAI can summarise performance and suggest campaign tweaks. But retailers who skip straight to AI without first understanding their own sales patterns, customer segments, and channel dynamics tend to automate their confusion rather than their insight.

Financial services: where auditability limits shortcuts

In heavily regulated sectors, the stakes of a weak analytics foundation are higher than embarrassment — they’re regulatory. Descriptive and diagnostic analytics aren’t optional extras here; they’re the basis for regulatory reporting, risk management, and audit trails.

ML fraud detection and GenAI investigation assistants are genuinely valuable in financial services. But they’re layered in carefully, on top of scorecards, delinquency models, and segment-level risk analysis that have been validated and governed over years. The analytics estate isn’t just fuel for AI — it’s the compliance record that makes AI defensible.

AI readiness is analytics maturity

When organisations talk about AI readiness, the conversation often turns to GPU capacity and model choice. For most businesses, that’s the wrong question. The right questions are:

  • Do you have trusted KPIs and shared metric definitions?
  • Can you trace those metrics back to source systems?
  • Are your analysts and business users comfortable challenging assumptions with data?

If the answer is no, adding AI won’t close those gaps. It will expose them at scale.

Two things worth noting for teams at this stage. First, analytics teams are the natural bridge to AI — they already understand the business context, the data quirks, and the stakeholder expectations that make models useful rather than academic. Second, the artefacts analytics teams produce — curated datasets, semantic models, metric definitions — are exactly what AI projects need: feature stores for ML, knowledge bases for RAG. Reusing them avoids rebuilding from scratch in every AI initiative.

The better the analytics foundation, the faster and safer AI can be introduced. Your data platform decision — warehouse, lake, or lakehouse — is an analytics decision first and an AI decision second. I’ll unpack those architecture choices in the next post.

Don’t start with the model. Start with the metrics.

Pick one high-impact decision your organisation makes today. Write down what data is used, how it’s analysed, and what would change if the analytics were more reliable — before AI enters the picture.

That single exercise will tell you more about your AI readiness than any consultant assessment. And it will tell you whether your next conversation should be about models, or about the metrics and data quality that would make those models worth deploying.

Leave a Reply