The AI adoption curve you have read about is a curve of organizations, and your company is one point on it. It plots how many firms, or how many adults, have started using the technology. It does not plot anything that happens inside your building, and that internal curve is the only one you can change or that your AI enablement budget is judged against.
Reading one as the other is why the curve gets quoted in planning meetings and helps nobody. Knowing that a fifth of US firms use AI says nothing about why 40 of your 180 people have stopped opening the assistant they were given in March.
Three different curves answer to the same name
Three unrelated measurements share this phrase, and two of them differ by a factor of nearly three.
The first is a count of firms. The Census Bureau’s Business Trends and Outlook Survey put current AI use at 19.8% of US firms as of May 3 2026, with 37% among firms of 250 or more employees and 32% at 100 to 249. One assistant in one department counts the same as a rebuilt operation. Your company is a yes or a no, nothing more.
The second is a count of people. Bick, Blandin and Deming’s nationally representative survey put generative AI use among US adults aged 18 to 64 at 54.6% overall and 37.4% for work in August 2025, against 19.7% for the personal computer in 1984 and 30.1% for the internet in 1998 at the same distance from launch. That is the curve behind the “faster than any prior technology” headline, and it counts your own staff on their personal accounts.
The third curve is the one nobody publishes: how much of your own work is done differently than last quarter. It counts workflows rather than firms or logins, and it is the only one your spending moves. The case for treating it as the real measure runs through our argument that buying licenses is not the same as building capability.
Why the classic adopter percentages break at 200 people
Everett Rogers’ adopter categories are the backbone of almost every page on this topic: innovators at 2.5%, early adopters at 13.5%, early majority at 34%, late majority at 34%, laggards at 16%. Those numbers are not a survey result. They slice a normal distribution of adoption times at standard deviations from the mean, describing the population that eventually adopts.
Three things follow, and most pages quoting the split miss all three.
They say nothing about who never adopts. They allocate eventual adopters across time. The share of your staff who will still not use an assistant in two years is not in the model, and that is what a head of operations wants to know.
At your headcount they stop being statistics. Sixteen percent of a 200-person company is 32 people, with names, job titles and reasons, no two of which respond to the same fix. A distribution is the right tool for a market of two million buyers and the wrong one for a roster you could read aloud in four minutes. Treating 32 colleagues as a predicted tail is how a program sends another all-hands email instead of asking six people what blocked them.
The decision itself is a different kind of decision. Rogers’ categories came from adoptions that happen once: the farmer plants the new seed, the doctor prescribes the new drug. Using an assistant is decided again every week, per task, and it reverses quietly. People migrate backward across the categories without announcing it, which a one-way curve cannot represent. What is still in place six months after a session is a property of your own company, not of the technology.
The categories remain useful vocabulary. They are not a forecast.
The internal curve bends by function, not by personality
The best evidence on adoption inside a company is not a vendor survey. It is a Census working paper, The Microstructure of AI Diffusion: Evidence from Firms, Business Functions, and Worker Tasks, published April 2026 by Bonney, Breaux, Dinlersoz, Foster, Haltiwanger and Pande and covering November 2025 to January 2026.
Two of its findings reframe the question. Among firms using AI, 57% use it in three or fewer business functions, and 65% confine task-level use to three or fewer tasks. Adoption inside a company is narrow almost everywhere, including at firms that would call themselves adopters on any survey.
Where it lands is consistent too. Sales and marketing leads at 52% of adopting firms, strategy and business development at 45%, IT at 41%: the functions whose output is text, produced on a short cycle, reviewed by someone who can spot a bad draft on sight. The flat ones are where work is numerical, regulated, or trapped in a system the assistant cannot see.
So the internal curve is not one bell across your staff. It is separate curves, one per workflow, at different stages. The same person is an early adopter on client email, a late starter on proposal drafting and absent on variance commentary, in the same week. Sorted by personality type that person is a contradiction. Sorted by workflow they are the normal case.
Which means your adoption number has a denominator problem before it has an engagement problem. “42% of staff active” averages workflows with nothing in common, and choosing the denominator deliberately moves the reported figure more than any training you could buy.
What the national numbers do tell you
National data is useless as a target and useful as a diagnosis, because of one gap.
The Federal Reserve’s FEDS Notes review of AI measurement, published April 3 2026 by Jeffrey S. Allen, sets the two sides side by side. About 18% of firms had adopted AI at year-end 2025. Around 41% of the workforce reported using generative AI for work as of November 2025, with 35.2% having used it in the prior week and 12% using it daily.
That is not a contradiction to resolve. It describes most companies, including yours.
| Reading | Figure | What it means inside one company |
|---|---|---|
| Firms that have adopted AI | ~18% | The official yes-or-no, set by whoever signed a contract |
| Workers using AI for work | ~41% | Use is already happening, sanctioned or not |
| Used at least once last week | 35.2% | Weekly habit sits close to the headline number |
| Used daily | 12% | Daily dependence is roughly a third of weekly use |
Worker use running ahead of firm adoption means your first session is rarely an introduction. It is a correction: people have formed habits on personal accounts, and some are why your legal review is nervous. Your curve started before your license did, so the baseline you need is behavioral, not contractual.
Read the 12% daily figure as the honest target band: a program promising that most of your staff will use an assistant daily is promising something no measured population has produced. Our guide to what good looks like at six and twelve months sets out the levels.
The shape you will see is a staircase
A smooth S-curve needs a large population of independent decisions. You do not have one. At 50 to 500 people, adoption arrives in steps, because the events that cause it are dated.
A session happens and 30 people start in the same week. A manager makes it the expected way to produce a weekly report and a department moves at once. Somebody shares a template and a flat workflow jumps. Between those events nothing moves, and the line is flat not because the technology stalled but because nothing happened.
So a flat month is the default state, not a warning. What deserves attention is a flat month following an event, which means the event failed, and a step down, which means something was withdrawn: a tool change, a policy memo, the departure of the one person who knew how.
Plot weekly rather than monthly, and mark every event: sessions, policy changes, tool updates, reorganizations. A curve without those markers cannot be read, and separating your training’s effect from a vendor’s product update depends on them.
Reading a plateau: three stalls that look identical
Most pages treat a plateau as a late-majority problem and prescribe more communication. Three conditions produce the same flat line, and two get worse.
| What you see | What it probably is | The test | The move |
|---|---|---|---|
| Flat at 35-45% for a quarter, depth still rising | Saturation of the workflows the tool fits | Count workflows per person. Rising while headcount is flat means nothing is stalled | Stop recruiting users. Open a new workflow |
| Flat headcount, flat depth, usage shallow | A capability ceiling: people do the one thing they learned | Ask five users for their last three uses. All three the same is a ceiling | Hands-on work on a harder deliverable, using their own documents |
| Flat dashboard, but managers report change | A measurement artifact from counting seats | Compare activation against use on one named task | Fix the metric before spending |
The third row is the common one and the cheapest to fix: activation reports a login, and a company can sit at 90% with nothing changed about how work gets done, which is the subject of our case against seat-license reporting. The first row is the one most often misread as failure, since a program that has reached every suitable workflow has succeeded.
Four series worth plotting
Four lines make an internal curve readable. Three come from data you already hold.
- Active users on one named workflow, weekly. One line per workflow, never a company average, because the average hides which curves are moving.
- Workflows per active user. The depth line, and the one that keeps rising after headcount flattens. Flat headcount with climbing depth is a program that is working.
- Days from session to first use. A cohort with a median of 14 days is in a different condition from one at two days, and that lag predicts the six-month result better than any satisfaction score.
- One timed baseline on that deliverable, taken before training. The only input here that cannot be rebuilt later. Our guide to the week before a session treats that window as a gate, and once it passes it does not reopen.
The full instrument is set out in our measurement guide for AI enablement, and what it costs to run a program with none of these lines is covered in our piece on unmeasured training.
Starting takes no new software. Pick three workflows by name, one from a function already moving and two from flat functions, pull weekly active users per workflow from the consoles you already pay for, mark the dated events, then run the plateau test on each line. What comes out is a list of workflows that are moving, workflows that are stuck, and a reason for each.
What the curve looks like when enablement works
A good result is not a curve that shifts upward along its whole length. It is two specific changes.
Time to first use compresses. Participants who would have drifted for a month start inside a week, because the session used their own documents and left them with something half-finished they wanted to finish.
Function count widens. A company using AI in sales and marketing adds two functions that were flat. With 57% of adopting firms nationally at three functions or fewer, moving from three to five is a real change in position, visible in a count you can run in an afternoon.
Neither change needs the headcount line to reach 90%, and a program sold on that promise is selling the metric rather than the result.
The flat stretch is worth pricing. The Bureau of Labor Statistics put employer costs for civilian workers at $49.46 per hour worked in its June 2026 reference period, released September 9 2026. Sixty licensed people spending 20 minutes a week on one shallow task is not a software loss but a payroll line whose work has not changed, against market rates of roughly $2,000 to $15,000 for hands-on fluency work.
Frequently asked questions
What is the AI adoption curve?
It is the shape of adoption over time. Published versions plot how many organizations or people have started using AI: about 20% of US firms and 41% of workers in the latest official readings. The version that matters to one company plots how many of its own workflows changed, which no survey measures for you.
Where is my company on the AI adoption curve?
The national curve records you as a yes or a no, so it has no useful answer. The answerable version is per workflow: which named deliverables are now produced with an assistant, by how many people, and how deeply. That gives a list rather than a position.
Do the classic adopter percentages apply to a workforce?
Not as a prediction. The 2.5 / 13.5 / 34 / 34 / 16 split slices a distribution of adoption times among people who eventually adopt. At 200 employees those shares resolve to a handful of named colleagues, and the model says nothing about who never adopts.
Why has our adoption rate stopped rising?
Three causes produce the same flat line. The tool has reached every workflow it fits, so nothing is wrong. People have hit a capability ceiling and repeat the one thing they learned. Or the metric counts seats, not work. Test depth per user and usage on one named task before calling it failure.
Is a 40% adoption rate good or bad?
Without a denominator it is neither. Nationally, 35.2% of workers used generative AI in the prior week and 12% daily, so a weekly 40% is unremarkable and a daily 40% exceptional. Which one your dashboard reports is usually undocumented.
How long does AI adoption take inside a company?
There is no predictable period, because it moves in steps tied to dated events rather than diffusing smoothly. Behavior change on a named task is visible within 30 days of a session when a baseline exists. A flat quarter with no events in it is normal.
Should we worry about the people who have not started?
Find out what they do first. Someone whose work is numerical, regulated, or locked inside a system the assistant cannot read is not resisting, and training will not move them. That is a tooling question, so save persuasion for text-shaped work.
What is the difference between adoption and capability?
Adoption counts whether the tool was opened. Capability describes whether output got better or faster at a named task. The two diverge routinely: a team can sit at 90% activation with no change in a deliverable, which is why scoring a team’s fluency before and after is the harder and more useful exercise.
Key takeaways
- Three measurements share the name: a count of firms (about 20%), a count of people (about 41% of workers), and your own count of workflows. Only the third responds to your budget.
- The classic adopter percentages slice a distribution of adoption times. They are not a workforce forecast, and at 200 people the laggard share is 32 named colleagues with 32 reasons.
- The internal curve is narrow and function-shaped: 57% of adopting firms use AI in three or fewer business functions, concentrated in sales and marketing, strategy and IT.
- Inside one company the curve is a staircase, not an S. Flat stretches are the default; a flat stretch right after a dated event is the signal.
- A plateau has three causes, and only one is fixed by more communication. Test depth per user and the dashboard’s denominator before spending another dollar on the program.
If your usage chart has flattened and nobody can say which of the three causes you are looking at, that is the ordinary position rather than an unusual one. We run a free AI-readiness call that works through your workflow list, the denominator your dashboard uses, and what a readable curve would need to show. Book a time here.
Arthur Wandzel