In partnership with

Most companies believe they are making progress with AI. A closer look suggests they are barely scratching the surface.

This week, we are digging into a framework that cuts through the confusion around AI adoption in organizations. Whether you run a team, manage a startup, or work independently, the three-part model below applies directly to how you compete and grow over the next few years.

Let's get into it.

Why Individual Wins Don't Add Up to Organizational Gains

Here is the tension that almost every company is sitting inside right now. Workers are quietly using AI tools, seeing real improvements in their own output, and saying nothing. Meanwhile, company-wide results look flat.

Four research-backed facts help explain what's going on:

4 Facts Reshaping How Work Gets Done

Fact 1 — Performance gains are real

A study of Danish knowledge workers found users believed AI cut their working time in half for 41% of their tasks. A separate survey of Americans found workers reported tripling their productivity, turning 90-minute tasks into 30-minute ones. Controlled experiments in sales, consulting, coding, and legal work back this up.

Fact 2 — Adoption is already widespread

Over 65% of marketers and 64% of journalists in Denmark reported using AI at work. In the US, 40% of workers reported using AI at work by April 2025, up from 30% just four months earlier. ChatGPT is now the fourth most visited website on the internet.

Fact 3 — The bigger gains are still untapped

Deep research tools can complete hours of analytical work in minutes. Early AI agents are beginning to handle real tasks autonomously. The ceiling of what's possible with today's tools is much higher than most organizations are currently reaching.

Fact 4 — Companies aren't capturing these gains

Despite strong individual results, companies are reporting only small to moderate gains. As of the end of 2024, there is no measurable impact on wages or hours worked at the organizational level.

The gap between personal gains and company outcomes isn't a technology problem. It's an organizational one.

What do these names have in common?

  • Arnold Schwarzenegger

  • Codie Sanchez

  • Scott Galloway

  • Colin & Samir

  • Shaan Puri

  • Jay Shetty

They all run their businesses on beehiiv. Newsletters, websites, digital products, and more. beehiiv is the only platform you need to take your content business to the next level.

🚨Limited time offer: Get 30% off your first 3 months on beehiiv. Just use code JOIN30 at checkout.

What closes that gap? Three forces working together: Leadership, the Lab, and the Crowd.

Leadership: The Part That Has to Come First

Two high-profile memos went viral this year. The CEO of Shopify and the CEO of Duolingo both sent clear signals to their organizations that this shift is serious and immediate. That kind of urgency matters.

But urgency alone doesn't move people. Research from Wharton professor Andrew Carton shows that workers are not motivated by abstract statements about efficiency gains. They respond to concrete, vivid pictures of what the future actually looks like. What will my job involve next year? Will the time I save get used to grow the team or reduce it? Will I be rewarded for finding better ways to work, or quietly resented?

Leaders don't have to have every answer. But they need a direction they're willing to share out loud.

What Good Leadership on This Looks Like

  • 01 Paint a vivid picture of what work looks like in the future, not just a promise of productivity gains.
  • 02 Define safe zones for experimentation. Workers need to know where it is permitted to try things without risk of punishment.
  • 03 Build real incentives for sharing discoveries. Some companies are offering vacations, promotions, and significant cash rewards for employees who surface transformational opportunities.
  • 04 Model the behavior yourself. Leaders who use tools openly and talk about what helps them create the permission for everyone else to do the same.

The Crowd: Where Innovation Actually Happens

The employees inside your organization are not waiting for a playbook. They are already experimenting. The problem is that many of them are doing it quietly.

Studies suggest that about 20% of workers use officially sanctioned tools at work, while over 40% admit to using their own. The gap points to something significant. Workers who have found real performance gains are hiding them, either to protect their reputation, avoid extra work being loaded onto them, or stay out of range of cost-cutting decisions.

This is sometimes called the "secret cyborg" problem, and it represents a significant loss for any organization trying to learn faster than its competitors.

Why Workers Stay Silent

The incentives to hide productivity gains are often stronger than the incentives to share them.

Fear of punishment

Vague policies make workers unsure what is and isn't allowed.

No upside to sharing

If gains become expectations without rewards, there's no reason to reveal them.

Reputation concerns

Workers fear managers will devalue their work if they know a tool helped.

Job security fears

Demonstrating efficiency can feel like marking yourself for elimination.

Experienced workers, specifically those who understand their domain well, are the best positioned to figure out where new tools are actually useful. They can tell when output is good and when it falls short. The goal for any organization is to make it safe and worthwhile for those people to share what they're learning.

The Lab: Building Things Before They're Ready

The third piece is a dedicated internal group focused entirely on figuring out what's possible and building it quickly. This isn't a traditional research and development function. It operates more like a startup inside the organization: rapid prototyping, constant testing, and a direct pipeline to the Crowd.

One of the Lab's most underrated responsibilities is building internal benchmarks. Almost every standard test for evaluating new tools measures things like math, trivia, or code. None of that tells you which tool is best at writing the kind of memos your team actually produces, or analyzing the financial models specific to your industry.

A useful example: the author of the source framework tested an agent called Manus, built on Claude, by giving it a fictional startup brief and a detailed financial model from a Wharton business simulation. The agent produced a 45-page business analysis, a pitch deck, a test of the financial assumptions, and a draft website, all from a short prompt and a spreadsheet. The output wasn't flawless, but it was more thorough and accurate than what most students produce in hours of work. That kind of test tells you something real about what a tool can and can't do. The Anthropic benchmarking guide is a practical starting point for building your own.

What the Lab Should Be Building

Rapid product releases

Take workflows the Crowd discovers and turn them into simple, usable tools fast. Test, release, measure, repeat.

Internal benchmarks

Build evaluation tests specific to your organization's actual tasks. Know which tools perform best on your work, not generic tests.

Prototypes that don't fully work yet

Build the version of a key process that runs on agents and see where it breaks. When models improve, you'll have a prototype ready to plug them into.

Provocations and demos

Show people what's coming. A well-designed demo that makes people slightly uncomfortable is worth more than hours of abstract discussion about strategy.

How Jennifer Aniston’s LolaVie brand grew sales 40% with CTV ads

The DTC beauty category is crowded. To break through, Jennifer Aniston’s brand LolaVie, worked with Roku Ads Manager to easily set up, test, and optimize CTV ad creatives. The campaign helped drive a big lift in sales and customer growth, helping LolaVie break through in the crowded beauty category.

The Bigger Rethink

There is a deeper question underneath all of this. Every process, structure, and workflow inside an organization was built around the assumption that intelligence is scarce and expensive. Research took weeks. Analysis required specialists. Content required production time.

None of those bottlenecks work the same way anymore. When research takes minutes, the constraint becomes knowing what to research. When code can be written quickly, the limitation is knowing what to build. When content can be produced instantly, what matters is knowing what will actually reach people.

The organizations that adapt fastest are the ones building feedback loops between all three layers: Leadership setting the direction, the Lab testing what's possible, and the Crowd discovering what actually works in practice. Together, they learn faster than any one piece could on its own.

Waiting for things to settle down before starting is not a strategy. The companies pulling ahead now are the ones willing to experiment while the picture is still blurry.

Worth Your Time This Week

Keep Reading