AI is saving workers up to an hour a day—but Goldman Sachs says 80% of companies aren’t using it yet
The productivity gains are real and measurable. So why are most businesses still sitting on the sidelines?
You’re probably sick of reading about artificial intelligence, maybe especially from this byline. But amid all the discussion, hype, and hysteria, Goldman Sachs economists Sarah Dong and Joseph Briggs have a sobering dose of reality in the data: Fewer than 19% of U.S. establishments have adopted it.
The Census Bureau’s Business Trends and Outlook Survey, as reported in Goldman’s March 2026 AI Adoption Tracker, shows that the figure is essentially flat from the prior month, though it is expected to rise to 22.3% over the next six months. It shows that adoption, while growing, has yet to reach the tipping point that would make AI a standard workplace tool rather than a competitive advantage reserved for early movers. But the data also suggests that, when used correctly, it saves a huge amount of time.
Enterprise workers who use AI are getting back nearly an hour a day, according to data from OpenAI dated December 2025. Specifically, Goldman reported that employees at companies with ChatGPT enterprise accounts save an average of 40 to 60 minutes per day thanks to AI, and 75% say they can now complete tasks they previously couldn’t do at all. The catch, of course, is that almost no one is doing this yet.
“We continue to observe large impacts on labor productivity in the limited areas where generative AI has been deployed,” the Goldman economists wrote, going on to essentially agree with the OpenAI disclosure. “Academic studies imply a 23% average uplift to productivity, while company anecdotes imply slightly larger efficiency gains of around 33%.”
Put simply: The companies using AI are pulling ahead, and most of their competitors aren’t even in the race yet.
The adoption gap is widening
The adoption divide isn’t just between industries—it’s also stark by company size. Firms with more than 250 employees report an AI adoption rate of 35.3%, more than double that of smaller establishments. But smaller businesses are starting to close the gap: Companies with 20 to 49 employees saw the largest recent increase in adoption, jumping 2.1 percentage points to 21.5%.
The sectors leading adoption are predictable—information services, professional services, finance and insurance, and education. Computing and web hosting firms top the list at 60% adoption. But broadcasting companies are expected to see the biggest surge over the next six months, according to Goldman’s analysis of Census Bureau data, signaling that the media and content industries are on the verge of a significant AI-driven transformation.
What most companies are missing
To be sure, the picture isn’t uniformly rosy. As Fortune reported last month, AI tools are also adding significant cognitive load for many workers, with time spent on some tasks increasing by as much as 346%, and deep-focus work hours dropping 2%. The time savings, it turns out, are often immediately reinvested in more work, not less.
Fortune also previously reported that some firms deploying AI are now completing product cycles that previously took 24 to 36 months in as little as six months—a compression of time-to-market that’s difficult to reverse once a rival has achieved it.
For the roughly 81% of U.S. firms not yet using AI, the data suggests they are leaving a substantial productivity dividend on the table. OpenAI’s enterprise figures show that its business users are now sending 30% more messages than they were just months ago—a signal that once workers start using the tools, engagement compounds quickly.
These stakes aren’t lost on the C-suite. A Fortune survey of CFOs published last week found that executives privately expect AI-attributed layoffs to be nine times as high in 2026 as current public figures suggest—even as many of those same CFOs acknowledged a persistent gap between the productivity gains they expected from AI and what they have actually measured so far.
The Goldman Sachs data, which shows real productivity acceleration in industries with higher adoption rates, suggests that the gap may be closing—but only for firms that have actually deployed the tools and done so correctly. To that point, Fortune reported last week that 77% of enterprises are actively pursuing AI initiatives—but many don’t know how to evaluate, procure, or deploy the tools effectively, leaving significant spending without measurable return.
The barriers to adoption are well-documented: insufficient employee skills, data security concerns, and difficulty identifying the right use cases, according to surveys from Deloitte, Gartner, and Bain & Company. But those barriers are softening. Bain found that more than 80% of reported AI use cases now meet or exceed expectations—a figure that undercuts the skepticism still common in many boardrooms.
For executives still evaluating whether to invest in AI tooling, Goldman Sachs’ data offers a clear warning: Firms that have already deployed AI are beginning to show measurable productivity gains relative to those that haven’t.
The 40 to 60 minutes a day that AI saves isn’t just a worker convenience. Across a team of 50, that’s roughly 33 to 50 hours of recovered productivity—every single day. The companies already capturing that aren’t waiting for the technology to mature. They’ve decided the risk of waiting is greater than the risk of moving.
There’s a more human dimension to that calculus, too. As Fortune reported in January, many workers whose productivity has genuinely improved with AI still describe a quiet sense of loss—of craft, of autonomy, of the slower rhythms that once defined skilled work. That hour they’re getting back, some say, doesn’t quite feel like it belongs to them anymore.
Fortune Tech
https://fortune.com/2026/04/01/ai-worker-productivity-adoption-goldman-sachs-saves-60-minutes-per-day/Sign in to highlight and annotate this article

Conversation starters
Daily AI Digest
Get the top 5 AI stories delivered to your inbox every morning.
More about
product
Anthropic Executive Blames Claude Code Leak on ‘Process Errors’
Anthropic PBC’s accidental release of source code for its popular AI coding agent was the result of “process errors” related to the startup’s fast product release cycle, according to a senior executive at the company.

Developers Are Designing for AI Before Users Now
<p>A quiet shift is happening in modern web development.</p> <p>For years, developers designed applications with one priority: users.</p> <p>UI came first.<br><br> User flows came first.<br><br> User experience came first. </p> <p>Backend, APIs, and integrations were built around that experience.</p> <p>But today, something has changed.</p> <p>Developers are increasingly designing systems with <strong>AI in mind before users</strong>, and this is reshaping how frontend, UX, and fullstack engineering work.</p> <h2> The Old Way of Building Applications </h2> <p>Traditional product development looked like this:</p> <p>Design UI → Build frontend → Connect backend → Launch</p> <p>The focus was simple:</p> <ul> <li>What does the user need?</li> <li>How will they interact?</li> <li>What is the ea

The Hidden Cost of Copy-Pasting Code Into ChatGPT
<p>AI coding tools promise faster development. The <a href="https://metr.org/blog/2025-07-10-early-2025-ai-developer-study/" rel="noopener noreferrer">METR study</a> found the opposite: experienced developers were 19% slower on complex tasks when using AI, even though they perceived themselves as 20% faster. The biggest contributor wasn't bad code generation. It was the workflow around it.</p> <p>Every time you alt-tab from your editor to a chat window, paste a function, explain what it does, describe the bug you're seeing, read the response, mentally translate it back to your codebase, switch back to your editor, and apply the changes, you're paying a productivity tax that compounds across a day of work. <a href="https://www.microsoft.com/en-us/research/uploads/prod/2022/07/Disrupted_and_
Knowledge Map
Connected Articles — Knowledge Graph
This article is connected to other articles through shared AI topics and tags.
More in Products

Anthropic Executive Blames Claude Code Leak on ‘Process Errors’
Anthropic PBC’s accidental release of source code for its popular AI coding agent was the result of “process errors” related to the startup’s fast product release cycle, according to a senior executive at the company.

Developers Are Designing for AI Before Users Now
<p>A quiet shift is happening in modern web development.</p> <p>For years, developers designed applications with one priority: users.</p> <p>UI came first.<br><br> User flows came first.<br><br> User experience came first. </p> <p>Backend, APIs, and integrations were built around that experience.</p> <p>But today, something has changed.</p> <p>Developers are increasingly designing systems with <strong>AI in mind before users</strong>, and this is reshaping how frontend, UX, and fullstack engineering work.</p> <h2> The Old Way of Building Applications </h2> <p>Traditional product development looked like this:</p> <p>Design UI → Build frontend → Connect backend → Launch</p> <p>The focus was simple:</p> <ul> <li>What does the user need?</li> <li>How will they interact?</li> <li>What is the ea

What Is New In Helm 4 And How It Improves Over Helm 3
<p>The release of <strong>Helm 4</strong> marks a massive milestone in the <strong>Kubernetes</strong> ecosystem. For years developers and system administrators have relied on this robust package manager to template deploy and manage complex cloud native applications. When the maintainers transitioned from the second version to <strong>Helm 3</strong> the community rejoiced because it completely removed <strong>Tiller</strong>. That removal drastically simplified cluster security models and streamlined deployment pipelines. Now the highly anticipated <strong>Helm 4</strong> is stepping into the spotlight to address the modern challenges of <strong>DevOps</strong> workflows. This comprehensive blog post will explore exactly what is new in <strong>Helm 4</strong> and how it provides a vastly

Promoting raw BG3 gameplay bundle previews in the TD2 SDL port
<h1> Promoting raw BG3 gameplay bundle previews in the TD2 SDL port </h1> <p>Today's checkpoint was small in code size but important in interpretation.</p> <p>The late gameplay bundles in the project already had useful <code>BG1</code>, <code>BG2</code>, <code>OBJ</code>, and screenshot-derived support surfaces, but they were still weak on one practical question: when design flagged the sky/horizon side of gameplay, were we looking at a missing asset, or were we looking at a composition problem?</p> <p>I closed that ambiguity by extending the gameplay bundle builder to emit first-class <code>BG3</code> artifacts next to the existing layer outputs:</p> <ul> <li><code>bg3.ppm</code></li> <li><code>bg3.png</code></li> <li><code>bg3_render.json</code></li> </ul> <p>Then I refreshed the promote

Discussion
Sign in to join the discussion
No comments yet — be the first to share your thoughts!