
TLDR: Generative AI makes specific tasks faster, but the gain shrinks a lot by the time it reaches company-wide output. Measure it on your own work instead of trusting averages:
Your AI vendor's dashboard says each user saves several hours a week. Your finance team sees the same headcount producing about the same output. Both can be true at once.
This guide is for HR, people analytics, operations and IT leaders who need to know whether generative AI is paying off. It covers what the research agrees on, why task gains shrink at company level, and how to measure the effect in your own teams.
Studies of generative AI at work fall into two groups, and they point in different directions.
For coding tools in particular, see how to measure the real impact of GitHub Copilot on your team.
Forecasts run far ahead of results. In June 2023, McKinsey estimated that generative AI could add $2.6 trillion to $4.4 trillion a year across the 63 use cases it analyzed. That is potential, not measured output. In October 2024, a BCG survey of 1,000 executives in 59 countries found that 74% of companies had not yet shown tangible value from AI. For the cost side, see how to track and prove ROI from AI investments.
Company comparisons need care too. PwC's yearly AI Jobs Barometer, for example, compares companies by how exposed their work is to AI. A comparison like that can show a link between AI exposure and productivity growth, but not that AI caused it.
A study of one task measures that task under good conditions. Your company's output depends on every task, every person and what people do with the time they save. Three things shrink the gain on the way up.
A 40% gain on one task ends up as about 1% more output for the team. That is why task studies report big numbers while company data barely moves, and why both can be right. The numbers are made up to show the arithmetic. Put your own task shares and usage rates into the same four steps.
A number that cannot answer most of these questions is a claim, not evidence.
You do not need a research team. You need a few specific tasks, a baseline and a fair comparison.
For a deeper method, see how to measure employee AI productivity accurately. To test whether the time saved is real, see is AI actually saving time in your company.
Here is the arithmetic for one comparison, with made-up numbers. Two support teams of similar size handle the same kinds of tickets. Team A starts using an AI assistant in March. Team B starts in June, so from March to May it is the comparison group.
Team B improved by 0.3 tickets an hour without AI, perhaps from a quieter season or better ticket routing, so that part of Team A's gain would have happened anyway. The AI effect is the difference between the two changes: 0.8 minus 0.3, or 0.5 tickets an hour, about 10% of Team A's starting level.
Check two things before you report it. First, quality: Team A's reopen rate is a point higher, so some of the speed may come back as rework. Second, noise: repeat the comparison on other months or teams and report a range, such as 6% to 14%, rather than one number.
Measure in three layers, from who uses AI to whether more gets done. The first two come from usage data. The third needs data from the systems where the work happens. For the metrics behind each level, see which AI adoption KPIs actually matter.


Usage logs from AI tools can show who uses AI, how often, with which tools, and how that differs by team, role and tenure, without reading anyone's prompts or documents. Worklytics is one example. It reads usage and log data from corporate AI tools such as ChatGPT, Claude, Gemini, GitHub Copilot, Cursor and Microsoft 365 Copilot. Its metrics include days AI was used, number of uses and the share of workday blocks with AI use, by type of tool. Worklytics says it pseudonymizes the data, reports at group level and does not store or analyze work content. The AI usage checker shows what a team-level view looks like.

Usage data also has limits. It cannot show whether the output was good, whether saved time became useful work, or whether AI caused a change. Some tools expose more detail than others. Use usage data to find where to look, then confirm with the five steps above. It does not replace a fair comparison.
It speeds up or improves specific tasks, such as drafting text, answering support questions, summarizing documents and writing code. How much that adds up to depends on how much of someone's week those tasks take, and on whether the time saved goes into more or better work.
At the task level, controlled studies mostly find that it has. At the company and country level, the measured effect so far is small and harder to see, because a gain on one task is diluted by everything else people do.
It can. When checking and fixing AI output takes longer than doing the work, or when people use it on work they already do quickly, tasks can take longer. This is one reason to measure results rather than rely on how fast people feel.
Newer and less experienced workers tend to gain the most on routine, well-defined tasks, because AI gives them some of what experienced colleagues already know. Experienced people often gain less on work they already do well.
Pick specific tasks, record time, output and quality before and after rollout, track real use from tool logs instead of surveys, and compare AI users with similar non-users or with teams that start later. Report a range, check quality and side effects, and repeat each quarter.
Compare what the tools and rollout cost with the value of the work that was actually completed or improved, not with hours saved on paper. Saved time only counts as value when it turns into output. In an October 2024 BCG survey, 74% of companies had not yet shown tangible value from AI.
Use usage and log data from the AI tools, such as how many days people used AI, how many times, and which tools, reported at team level. This shows adoption without reading prompts or documents. It does not show whether the output was good, so pair it with outcome measures from your own systems.
If you want to see these usage measures for your own organization, the AI adoption page shows what Worklytics tracks and how it handles privacy.