The average manager saves twice as much time with AI as the people doing the actual work

A VP of Operations I work with told me last month that AI had "given her back Fridays." She drafts emails in half the time, generates meeting summaries without taking notes, and auto-creates project status updates from Slack threads. Her senior developer, sitting ten feet away, said AI saves him maybe 20 minutes a day. He still writes his own code, still debugs by hand, still reads documentation nobody has fed into a chatbot.

That gap is not anecdotal. It is the single most consistent finding in this year's workplace AI research.

The numbers

Business.com's 2026 SMB Workplace Study surveyed 1,009 U.S. workers at companies with 2 to 250 employees. The headline: managers save 7.2 hours per week using AI tools. Individual contributors save 3.4 hours. That is a 2.1x gap.

The average across all roles is 5.6 hours per week, which sounds impressive until you realize how unevenly distributed those savings are.

A separate survey from AI consulting firm Section, covering 5,000 white-collar workers, found the same pattern but sharper. More than 40% of executives reported saving upward of eight hours weekly. Two-thirds of non-management workers said they save less than two hours, or nothing at all. Gallup's Q4 tracking data showed that 69% of leaders use AI at least a few times a year, compared to just 40% of individual contributors.

The pattern is consistent across studies: the higher you sit in an org chart, the more time AI gives back to you.

Why the gap exists (and it is not about intelligence)

The explanation is structural, not cognitive. Managers and ICs do different types of work. AI is better at some of those types than others.

Manager work is text-heavy and formulaic. Emails, status reports, meeting summaries, project briefs, performance reviews, budget narratives, stakeholder updates. Most of this writing follows predictable patterns and templates. A well-prompted language model can draft 80% of it in seconds.

IC work is judgment-heavy and tool-specific. A developer choosing between two database architectures, a designer making spacing decisions in a UI, a data analyst deciding which variables to include in a model. These tasks require domain expertise, context that lives in someone's head, and tool proficiency that AI can assist with but cannot replace.

The Business.com study backs this up. The top AI use cases in SMBs cluster around text generation: 84% of AI users rely on chatbots (ChatGPT, Gemini, Claude), 67% use AI-powered search, and the most automated business functions are customer service, marketing, and documentation, all text-forward domains.

This table is not scientific. It is a rough model based on the studies cited and patterns I see with clients. Your mileage will vary. But the direction is consistent: text-heavy, template-adjacent tasks compress the most.

The rework tax

Before managers start celebrating their recovered Fridays, there is a catch. Workday's 2026 "Beyond Productivity" report found that 37% of time saved through AI gets consumed by reviewing, correcting, and rewriting AI-generated output. For every 10 hours of efficiency gained, nearly four hours go to rework.

That ratio hits ICs harder than managers, but not for the reason you might think. When a manager sends an AI-drafted email that is 90% right, fixing it takes two minutes. When a developer accepts an AI-generated function that compiles but handles edge cases wrong, finding the problem can take hours. The cost of being wrong scales with the complexity of the domain.

Only 14% of employees in the Workday study consistently reported net-positive outcomes from AI use. The rest experienced a muddled mix of time saved and time spent cleaning up after the tools.

AI is still worth using. But the time savings numbers from surveys are gross, not net. The actual productivity gain is smaller than the headline, and it depends on how well you match the tool to the task.

What managers should automate first

If you manage people, start with the repetitive text tasks that eat your calendar:

Email triage and drafting. Not every email. The ones that follow patterns: status requests, scheduling coordination, acknowledgments, FYI forwards with context. Most managers send 30-50 of these per week. AI can draft them in bulk if you build a handful of templates and review before sending.

Meeting summaries. Every meeting tool now offers AI summaries. The quality varies, but even a mediocre summary is better than "I'll send notes later" followed by silence. The key is picking one tool and using it consistently, not trying three and abandoning all of them.

Status reports and project updates. If your team uses any project management tool with an API, you can automate the weekly status email almost entirely. The AI reads task completion data, open blockers, and upcoming deadlines, then writes the narrative. You review it, add the two sentences of judgment that matter ("We're behind on X because of Y, and here's my plan"), and send.

Performance review drafts. This one makes people uncomfortable, but the first draft of a performance review, the part where you summarize what someone did across six months, is exactly the kind of structured recall that AI handles well. Feed it the person's completed tasks, 1:1 notes, and peer feedback. Let it organize the material. Then write the actual evaluation yourself.

What ICs should automate first

If you are an individual contributor, the playbook is different. Your work has less text surface area for AI to compress, but there are still high-value targets.

Documentation and comments. Writing docs is the tax that nobody wants to pay. AI is genuinely good at taking rough notes or code and producing readable documentation. Not perfect documentation, but a draft that you can edit in 10 minutes instead of writing from scratch in 45.

Boilerplate code and config files. Not the interesting code. The boring code. Test scaffolding, API endpoint stubs, configuration files, data migration scripts. The kind of work where the pattern is well-known and the implementation is just typing. Let AI do the typing.

Research synthesis. When you need to evaluate three competing libraries, read through 15 GitHub issues, or understand a new API, AI can compress the reading time. Feed it the docs, ask specific questions, verify the answers. This is not a replacement for reading, but it is a reasonable first pass.

Communication upward. ICs often underinvest in communicating their work to managers. AI can help draft brief weekly updates, summarize what you shipped, or prepare talking points for 1:1s. This is one place where ICs can borrow from the manager playbook.

The adoption gap is also a perception gap

The Business.com study found something worth sitting with: 22% of individual contributors view AI as "anti-worker," compared to only 11% of managers. Meanwhile, 37% of managers prefer a 50/50 human-AI balance in operations, versus 27% of ICs. And 53% of all workers still favor "mostly human-led" operations.

These numbers suggest the time-savings gap is self-reinforcing. Managers save more time because their tasks are more automatable, which makes them more enthusiastic about AI, which makes them push for more adoption. ICs save less, do more of the rework, and end up more skeptical. They are not wrong to be.

The risk is that organizations optimize AI deployment for the people who benefit most (managers) while underinvesting in use cases that would actually help the people doing the core work (ICs). Gallup's data already shows this: frequent AI usage among managers has doubled from 15% to 30%, while IC usage grew from 9% to 23%. The gap is widening.

The question to ask yourself

Stop thinking about AI in terms of average hours saved. Averages hide more than they reveal when the distribution is this uneven.

Instead, audit your own week. Write down your tasks for five days. Next to each one, mark whether it is primarily text generation, information synthesis, or applied judgment. The first two categories are where AI saves real time today. The third is where it mostly does not.

If 60% of your week is text and synthesis (common for managers), you are probably leaving 5+ hours on the table if you are not using AI tools. If 60% of your week is judgment and tool-specific skill (common for ICs), your realistic ceiling is closer to 1-2 hours, and pushing beyond that creates rework.

This gap is structural and it will persist until AI gets meaningfully better at judgment-heavy work. We are nowhere close.

Stop chasing someone else's time-savings number. Figure out which parts of your specific role compress well, automate those, and leave the rest alone.