LO
Get told when a verified record lands on this occupation →
Management consultant
Is brought in to answer a question the client could in principle answer themselves, and delivers a recommendation whose correctness will not be knowable for a year.
This is not a probability of losing your job. It combines how much of the role's task load is exposed to automation with how far adoption has actually gone — useful for comparing occupations on one consistent basis, and for nothing else.
Covers generalist advisory work — strategy, operations, organisation. Implementation consulting, where the deliverable is a working system rather than a recommendation, is a different exposure and closer to the engineering pages here. The single biggest variable is whether the firm sells hours or outcomes, because that decides whether cheaper analysis is a margin gain or a revenue loss.
The evidence base holds verified records for other occupations, but not one for this one yet. Until it does, the analysis below is reasoning about task structure and known technical capability — for this job in particular it is not backed by traceable sources, and we would rather say so than cite things we have not verified. An empty section here is a gap in our coverage, not a finding about the work.
What is actually changing#
The unit of analysis is the task, not the job title. A role is not replaced — its task mix shifts.
Is this your job? Say so and this page narrows to your share of it.
A job title is a bundle of tasks bought together, and no two people hold the same bundle. Nothing is sent anywhere — it stays in this browser.
Building the deck
Automating≈ Platform inferenceResearch, benchmarking, market sizing, the analysis, and turning all of it into forty slides that make an argument.
This is the most exposed professional task on this site after documentation, for a reason that is structural rather than about quality: the inputs are public documents, the output is a known format, and the intermediate steps — summarise, compare, chart — are exactly what models do cheaply. Producing it was the junior pyramid's entire economic function.
The deck was never the product; it was the evidence of effort that justified the fee. What is at risk is therefore the billing model rather than the advice — and the firms most exposed are the ones selling hours, because cheaper production converts directly into less revenue for the same work. Nothing here says the advice gets worse or better.
Finding the question behind the question
Still human-led≈ Platform inferenceWorking out that the client asking how to cut costs is really asking how to justify a decision they have already made, or how to move a person without saying so.
The input for this is what is not said in the room and who did not attend the meeting — information that exists only in a physical setting and is never written down. A model given the brief inherits the stated question, which is exactly the thing an experienced consultant's first week is spent refusing.
This being human does not protect the pyramid beneath it. Firms are structured as a small number of people who do this task supported by many who build the deck, and removing the second does not create more of the first — it removes the route by which anyone learned to do it, which is a problem for the firm five years out rather than this quarter.
Being the outside voice
Still human-led≈ Platform inferenceSaying the thing three people inside the company have been saying for a year, and having it land because it came from outside.
The mechanism here has never been analytical, which is why it is unaffected by cheaper analysis: an outside recommendation carries authority the same words do not carry internally, and it also carries blame if it fails. Both properties require an accountable party that can be dismissed, and a model cannot be fired.
This is the most durable task in the occupation and the least defensible one to describe out loud, and it does not scale: it is worth a partner's fee for a few conversations, not a team's fees for six months. A firm whose durable value is this cannot be the size it is today.
Getting three departments to move
Still human-led≈ Platform inferenceRunning the workshops, chasing the owners, and holding a programme together across teams that do not report to each other or to you.
This is influence without authority performed in person over months, and it is the half of consulting that clients most often say they actually paid for. There is no artefact to generate — the work is a sequence of conversations whose purpose is to change what people do next week.
Durable and unpriced at the same time: it is billed as days of a consultant's time, which is exactly the unit that gets cheaper to supply and easier for a client to question when the analysis it used to come bundled with is free. The task survives the technology and may not survive the pricing.
Which technologies matter here#
Four separate signals. They are deliberately not added together — a job exposed to two technologies is not twice as exposed.
How it got here#
The index is not a static number. This is where it would have sat at each capability checkpoint since ChatGPT — reconstructed, and labelled as such.
The second-steepest professional curve on this site after documentation, and for a structural reason rather than a judgement about quality: the deck's inputs are public documents, its output is a known format, and the steps between — summarise, compare, chart — are what models do most cheaply. Producing it was the junior pyramid's entire economic function. It flattens where the tasks have no artefact: finding the question behind the stated question, which depends on what is not said in the room; being the outside voice, which works because an accountable party can be dismissed; and moving three departments that do not report to each other. Read the height as the billing model rather than the advice — and note that every task that holds is one that does not scale.
A flat line is not a forecast of safety. It says which tasks automation has reached so far — the occupations that moved least here are the ones where the constraint is physical or regulatory, and both of those can change.
Recent changes#
No verified events recorded yet.
This section will fill from the monitoring pipeline as events are collected, de-duplicated, graded and linked to the tasks above. An empty list here means we have not verified anything — it does not mean nothing is happening.
"We found no news" is not the same as "you are safe."
What this means for you#
The pyramid you are joining exists to produce the deck, and the deck is the most exposed part. That is a structural problem for the firm and an immediate one for you: the years of deck-building were how people learned to find the real question, and nobody has designed a replacement. Optimise for time in the room with the client over time in the model, even where the second is what gets rated.
The task that holds is the one that cannot scale, and that is the uncomfortable arithmetic of this profession right now. A practice whose durable value is judgement and outside authority is a much smaller practice, and the transition is a pricing conversation rather than a technology one — worth starting before the client starts it.
Your options#
Four directions, each with its real constraints and one thing you can test this week. Continuing as you are is a legitimate choice — it just has to be a chosen one.
Sell the outcome, not the hours
Cheaper analysis destroys an hours-based fee and leaves an outcome-based one intact, because the client is buying the change rather than the effort.
Outcome pricing moves the risk onto you, and it only works where the outcome is measurable within the engagement.
Take your last engagement and ask what the client would have paid for the recommendation alone, with no deck. That gap is the exposure.
Move to implementation
Where the deliverable is a working system rather than a recommendation, correctness is checkable and the client cannot get it from a document.
It is a different skill and usually a pay cut on the way in, because you are junior again in the thing that matters.
Look at your last three projects and note which recommendations were actually implemented. That ratio is the honest measure of your own output.
Common questions#
The deck is the most exposed professional task on this site after documentation, and for a structural reason: the inputs are public documents, the output is a known format, and the steps between are summarise, compare and chart. But the deck was never the product — it was the evidence of effort that justified the fee. So what is actually at risk is the billing model, most sharply at firms selling hours, and the tasks that hold are the ones that do not scale.
No date. The signal here is a question you can ask about your own last engagement: what would the client have paid for the recommendation alone, with no deck attached? The gap between that and the fee is your exposure, and it is a pricing fact rather than a technology one. The firm-level signal is whether anyone is redesigning how juniors learn, because the deck years were the training and removing them is a five-year problem nobody is budgeting for.
Three things, and it is worth being blunt that only one of them scales badly enough to matter. Finding the question behind the stated question depends on what is not said in the room, which is never written down. Being the outside voice carries authority and blame that the same words do not carry internally — and a model cannot be fired, which is half of why the mechanism works. And getting three departments that do not report to each other to move is influence without authority, performed over months. None of those is analysis, and none of them supports a pyramid.
Different rather than simply safer, and the difference is worth naming precisely. When the deliverable is a working system, correctness is checkable — which cuts both ways: the client cannot get it from a document, and equally the automatic referee that makes code migrations move so fast is present in that work too. The honest version is that implementation trades exposure to cheap analysis for exposure to cheap code, and which is worse depends on what you build.
Method and sources#
- Assessment date
- 2026-09-14
- Basis of the task judgements
- 0 evidence-backed · 4 platform inference · 0 not enough evidence
- Verified events
- 0