Monday morning, the finance dashboard refreshes and the headline number is ugly: revenue down 12 percent against last month. By the time the leadership call starts, three people have three versions of what to do, and none of them are wrong exactly, because they are answering different questions. One wants to know where the drop landed. One wants to know why. One wants to know whether next month gets worse. One wants to know what to actually change.
That is not a meeting problem. It is the four types of analytics, sitting in one room, mistaken for a single thing. Descriptive, diagnostic, predictive and prescriptive analytics each take that same 12 percent and do something different with it. Most teams are fluent in the first, competent at the second, and quietly stuck below the third. This post walks the revenue drop through all four, so the line between them stops being fuzzy.
Origin: a ladder Gartner drew, and what it was for
The four-tier framing is not folklore. Gartner formalised it as the Analytic Ascendancy Model in 2012, and it spread because it answered a question every executive was asking that decade: we bought the data warehouse, where is the payoff. The model gave a shape to the answer. Four rungs, each defined by the question it answers. Descriptive: what happened. Diagnostic: why did it happen. Predictive: what will happen. Prescriptive: what should we do about it.
The clever part was the second axis. Gartner did not just stack the four; it plotted them against value and against difficulty, and drew both lines climbing together. Reporting yesterday's number is cheap and worth a little. Recommending tomorrow's decision is expensive and worth a lot. The framework is often split down the middle: descriptive and diagnostic are hindsight, predictive and prescriptive are foresight. The first half explains the past. The second half changes the future.
The model is a simplification, and worth treating as one. The rungs are not strict prerequisites, the order is not sacred, and climbing it for its own sake is a known trap. But as a way to see that "we do analytics" is four claims, not one, it has held up for well over a decade. Use it as a diagnostic tool, a way to locate where your team actually is, not as a maturity score to chase.
Present: the same drop, four times over
Descriptive: what happened
Start with the 12 percent. On its own it is almost useless, because "revenue" is an average laid over dozens of moving parts. Descriptive analytics is the work of pulling that average apart until the drop has an address.
So you cut it. Revenue by region: the drop is concentrated in two markets and the rest are flat. By product line: subscriptions fell, one-time purchases held. By customer segment: new-customer revenue is steady, existing-customer revenue is down sharply. By week: the slide started in week two and got worse. None of this is a clever model. It is exploring, summarising and visualising historical data, the layer Gartner put at the bottom because it is the foundation everything else stands on.
The methods are dashboards, reports, slicing by dimension, period comparisons, a clean star schema underneath so the cuts are fast and consistent. This is by far the most used tier, and for good reason. It is also where most organisations stop. The standard analytics-maturity research, including Deloitte and MHI supply-chain surveys, keeps finding the same shape: near-universal use of basic reporting, then a steep drop as you move up the rungs. Descriptive analytics is not boring or beneath you. A drop you cannot locate is a drop you cannot fix. But notice what it has not told you: not one word about why.
Diagnostic: why it happened
Descriptive analytics ends at "existing-customer subscription revenue in two regions fell, starting week two." Diagnostic analytics treats that sentence as the start of an investigation.
The core question is causal, and the methods are built to chase it: drill-down, correlation analysis, root cause analysis, cohort comparison, anomaly detection, the plain discipline of the five whys. You drill into those existing customers and segment by acquisition channel, by tenure, by plan. A churn analysis is exactly this. The pattern shows up constantly: a blended churn number looks unremarkable until you split it by cohort. One documented case involved a deep-discount Product Hunt campaign that spiked signups and then saw churn surge by month two, because segmented analysis revealed most of those signups were freelancers rather than the target small-business buyer. The average was hiding the story.
In our case the drill-down lands somewhere similar. The lost revenue traces to a specific cohort of subscribers, and the timing of their cancellations lines up with a price change that went live in week two. That is the candidate cause. The hard part of diagnostic work, and the reason it is the most skipped rung, is the discipline not to stop early. Correlation is not causation. The price change correlates with the churn; a competitor also ran a promotion that month, and a billing bug also shipped in week two. Good diagnostic analytics keeps pulling threads until one of them is load-bearing, instead of grabbing the first plausible story and moving on. Teams jump straight from descriptive to predictive constantly, and a forecast built on the wrong "why" just predicts the wrong thing faster.
Predictive: what happens next
Now you know roughly what happened and why. Predictive analytics asks where this goes if nothing changes.
It runs on history and statistics. Regression, time-series methods like ARIMA and exponential smoothing, classification models, gradient-boosted trees, neural networks: all of them learn a pattern from the past and extend it forward. Here it does two useful jobs. First, trajectory. Given the cancellation rate in the affected cohort and normal seasonality, what does revenue look like in 30, 60, 90 days on the current path. That converts a one-month drop into a forecast you can plan against, or panic about with evidence.
Second, and more valuable, it gets specific about people. A churn model scores every customer who has not cancelled yet and ranks them by probability of leaving next. The output is not a vague worry; it is a ranked list of at-risk accounts plus the factors driving each score. That is the difference between "we might lose more subscribers" and "these 1,400 accounts are most likely to go, and the price change is the top signal for most of them." One analysis of predictive-analytics retention programs puts the typical gain at cutting churn by 15 to 25 percent, because early warning buys time to act. Treat that as a vendor-side benchmark rather than a guarantee, though the direction is sound. Hold onto the limit, all the same: a forecast is still not a decision. It tells you the building is on fire and roughly which floor. It does not tell you which door to use.
Prescriptive: what to do
Prescriptive analytics is the rung where analytics stops describing the world and starts recommending a move. It takes the descriptive picture, the diagnostic cause and the predictive forecast, adds your constraints and goals, and returns an actual recommendation.
The methods change character here. This tier runs on optimisation, simulation and decision analysis: linear and integer programming, what-if scenario modelling, increasingly machine learning on top. For the revenue drop, prescriptive analytics does not just say "churn is up." It evaluates options against an objective. Roll the price change back fully. Roll it back only for tenured customers. Hold the price but offer the at-risk cohort a three-month discount. Hold and spend the money on a retention campaign instead. Each option has a modelled cost, a modelled effect on churn and a modelled effect on revenue, and the system simulates them and returns the one that best protects margin without overcorrecting. Fraud detection shows the same move at scale: where a predictive model only flags a transaction as suspicious, a prescriptive layer weighs the cost of a false alarm against the cost of a missed fraud and recommends the proportionate response, from a silent allow to a step-up verification. Stripe reports JPMorgan Chase using prescriptive analytics in fraud detection to cut false positives by up to 30 percent. The win is not detection, it is choosing the action with the least collateral damage.
This is the rung almost nobody reaches. It needs the three below it working first, it needs optimisation skills most marketing and product teams do not staff, and it concentrates in industries like logistics, aviation, finance and clinical care where the decision space is well defined and the payoff is enormous. It is also the rung where trust gets hard. A prescription is only as good as the model behind it, and a recommendation you cannot interrogate is a decision you are taking on faith.
Future and impact: AI is pushing everyone up the ladder
For a decade the ladder had a natural gravity. Descriptive was easy so everyone did it; prescriptive was hard so almost nobody did. AI is changing the slope, and it is changing it from the bottom up.
The bottom two rungs are being automated first, because they are the most well-defined. Conversational analytics in tools like Tableau Pulse, Power BI Copilot and ThoughtSpot already lets a non-technical user ask in plain language and get the descriptive cut back, charted and written up. Diagnostic analytics is following: agents that watch metrics, catch the anomaly, run the drill-down and surface the likely cause without anyone opening a dashboard. Predictive is quietly becoming a default feature rather than a project, with forecasts and anomaly detection shipping inside the BI tool.
The real shift is at the top. Agentic analytics aims to close the loop, an agent that reads the data, reaches a prescription and then executes it, reallocating budget or triggering a retention offer with a human supervising rather than driving each click. Gartner expects 40 percent of enterprise applications to embed task-specific AI agents by the end of 2026, up from under 5 percent in 2025. MarketsandMarkets pegs the prescriptive analytics market at USD 14.3 billion by 2026, a 24 percent compound annual rate from 2021. The hard rung is getting cheaper to stand on.
The honest risk sits exactly where the value does. A descriptive chart that is slightly wrong wastes a glance. A prescriptive recommendation that is wrong and gets executed automatically is a bad decision made at machine speed. The serious vendors draw the line carefully: the agent can orchestrate the workflow and execute inside set limits, but the statistical model and the guardrails stay human-controlled, with high-stakes calls escalated and every action logged. Climbing the ladder faster only helps if you can still see which rung you are on.
For teams building this out, the practical move is the same as it has been: get descriptive analytics genuinely decision-grade, refuse to skip diagnostic, and treat predictive and prescriptive as capabilities you earn rather than buy. At Perform Digital, the agentic-analytics work we do for clients sits on that order deliberately, because an agent that recommends actions on top of a shaky "what happened" just automates the original confusion. The four types are not a competition. They are one question, asked four ways, and the 12 percent only becomes a decision once it has been all the way up.
Council summary
The post argues that "we do analytics" is really four separate claims, and it proves the point by carrying a single fact, a 12 percent revenue drop, up Gartner's 2012 Analytic Ascendancy Model one rung at a time. Descriptive locates the drop, diagnostic finds the price change behind it, predictive forecasts the damage and ranks who leaves next, and prescriptive weighs the fixes and recommends one. The running example does its job: each tier ends with the precise question it cannot answer, which is what hands the reader off to the next. The takeaway for a decision-maker is to know which rung a given question needs and to refuse to skip diagnostic, because a forecast or an automated recommendation built on the wrong "why" just makes a bad call faster. The council verified the model's origin, the Gartner agent forecast, the prescriptive market size, the churn-reduction range, and the JPMorgan Chase fraud figure, and replaced three claims whose original citations did not support them.
Comments