That's the story almost everywhere, the work just got quicker. A few teams used the same emerging tools to do things they couldn't do before, and the difference between faster and new is the only one that matters.
Walk into almost any company right now and AI is everywhere and nowhere at once. Your people use it all day, writing the first draft and tightening the deck and turning around in minutes what used to take a week. Everything ships faster. And yet how the business actually works, where growth comes from and how the real decisions get made, looks about the same as it did for the last decade. That's the gap you can feel but haven't quite been able to name.
Because there are two very different things AI can do for a business, and they're easy to confuse. AI can help you do the work you already do quicker and more efficiently. Or it can change what the business is capable of. The first gives you the same playbook at lower cost. The second gives you capabilities you didn't have before, work and outcomes that weren't available at all. Those aren't two speeds of one thing. They're different intentions, and they build very different companies.
Notion's AI maturity model
A study Notion just released makes the split impossible to miss. The research looked at more than six thousand companies across ten markets and sorted them by how deeply AI is woven into the actual work. The report reads like a maturity curve, four rising stages. But look at the middle of it. The bottom two stages are AI doing your team's work. The top two are AI doing work your team couldn't do on its own. The line that cuts the curve in half, between stage two and stage three, has nothing to do with technology, since every company on the chart has the same tools. It's whether someone decided to change what the work is.
The four stages of AI maturity. Find where your function or business unit sits. Then decide to cross the line.
1. Thought Partner (57%). People draft and brainstorm on their own.
2. Assistant (31%). AI taps your data and speeds up real tasks.
The line that matters. Stages 1 and 2, AI does your work. Stages 3 and 4, it does work you couldn't.
3. Teammate (10%). Agents run recurring workflows; people check them.
4. System (2%). AI runs critical work end to end.
Notion Global AI Transformation Study, 2026. Almost everyone is below the line, which is exactly where the opportunity is.
Almost everyone sits in the bottom half of that curve, in stages one and two, below the line. More than half are at the first stage, using AI the way your team probably did this morning, as a smart helper on the task in front of them. Only a few have crossed into stages three and four, where AI runs the work itself. The study is pretty direct about why that feels surprising: the loudest stories come from the edges. A small handful of companies are doing the disruptive work, loudly enough to convince everyone else they're falling behind. Most of the market isn't behind at all. It's just below the line.
The most revealing thing in the study is what happens as companies cross that line. The reason they give for using AI flips. Below it, the goal is efficiency: do the same work for less. Above it, that goal fades away and a bigger one takes over: take on work the team couldn't do before, and create what wasn't possible. That flip isn't a byproduct of maturity. It's the crossing. Moving up means your team stopped using AI to do its existing work more cheaply and started using it to do what it never could.
Below the line, AI makes your team faster. Above it, it does work your team never could.
Who's allowed to cross the line
The reason that line is so hard to cross comes down to who's allowed to cross it. Using AI to make the existing work faster is something anyone on your team can do. Someone on the team can pick up a tool and speed up their own job tomorrow, no permission required. But changing what the work itself produces means redesigning what your company or function actually does, and nobody on the team can authorize that. It's your call. The study shows it plainly: owners and senior leaders are several times more likely than their teams to have AI running real work. Not because they're better with the tools. Because they're the only ones allowed to change the work.
But permission only explains who can cross the line. It doesn't explain why so few of the people who can, actually do. The honest reason is harder to say out loud. Making the existing work more efficient is the safe move: it asks for no vision and risks nothing, and you can do it for years and look completely responsible the whole time. Changing what the work is means committing to a view of where things are headed and being the one who's wrong if it doesn't land. That exposure is the real barrier, and it isn't technological. The distance between the few who cross and everyone who doesn't was never mainly about tools, or even strategy. It's a courage gap. AI didn't create it. It just stripped away the last excuse for not facing it.
Look at what that means for your business or function. If your team is stuck below the line, it isn't because they aren't using AI. They use it constantly, to move faster. It's that moving faster is the most they can do without you. The ceiling on what AI actually changes in how you grow is you, the most senior person willing to rethink how the work gets done.
It was never a technology gap. It's a courage gap.
The scaffolding beneath the crossing
The barrier isn't only courage. There's a practical one beneath it that trips up even teams with the will to cross. The everyday tools that got you this far, a ChatGPT, Copilot, or Claude, are probabilistic: brilliant guessers, which is exactly what you want for a draft you're going to read and fix. That's stages one and two. But running real work end to end needs something a raw model can't give you on its own, reliability you can trust without standing over it. That comes from the deterministic scaffolding built around the model, the guardrails and expert prompting that turn a good guess into a dependable system. Most teams never see that gap, which is why a chatbot subscription gets mistaken for transformation, and the confusion runs all the way up, from the person typing the prompt to the C-suite signing the budget. What actually crosses the line looks less like a chatbot and more like a harness around the model. Something like FifthRow: expertly prompted, model-agnostic, built to run the work rather than just help with it.
We've seen this exact lag before. When factories first got electricity, most owners did the obvious thing and swapped the steam engine for an electric motor. They got a modest bump and wondered what the hype was about. The ones that actually won spent years on something harder. They redesigned the whole floor around what electricity made newly possible, and changed what the factory could make. The motor was available to everyone. The redesign was a leadership choice, and it took a generation. AI is the same pattern, running faster. The tools are already everywhere. The decision to rebuild how the work gets done is, as it always has been, the rare part.
So you're not behind on AI. The question was never whether your team is using it. It's whether you'll move your business or function across the line on purpose, and that's work you can start this quarter. It begins with being honest about why the team is stuck below it, because the reasons are rarely about the tools.
Crossing starts the moment you point AI at something it has never touched in your world. Have your team use it to learn a new domain in days instead of months, so missing expertise stops being the thing that holds you back. Turn it loose on the bigger problems worth solving, not just the work already in the queue. And aim it at the real areas of disruption you see coming, the ones that actually scare you, instead of the safe edges everyone else is automating. That's what above the line looks like in practice. Getting your whole team there takes a few deliberate moves.
How you cross the line
Four moves, and every one of them is yours to make.
1. Show them what's possible. Most teams can't build a stage-three capability because they've never seen one. Their picture of AI stops at a faster way to write or research, so that's the ceiling they aim for. Don't tell them to think bigger, show them. Pick one company already operating above the line and pull it apart together: what did they actually build, and what would our version of it be? Bring in a peer who's crossed and have them walk your people through how they did it. And get one small proof on the table fast, have someone wire up a single agent to run one real workflow, then demo it, because nothing widens the picture like watching it work. Imagination is the first input, and it's the cheapest one to raise.
2. Take the fear off the table. If your people suspect that AI running the work end to end means fewer of them, they'll keep it parked in stage two, where it helps them and threatens no one. That instinct is rational, and it'll quietly cap your function until you name it. So name it. Tell them plainly that the goal is the same people doing bigger work, not fewer people doing the same, then point the freed-up time at something visible, a play or a launch they've wanted to run but never had the hours for. The study found the companies furthest along didn't shrink their teams, they freed them to do what they never could. Make that the deal, out loud.
3. Get fluent fast at one and two. Mastery of the bottom funds the top. The quicker your team gets genuinely fluent with AI on today's work, the more time and confidence it has to build tomorrow's. So set a real bar, a standard everyone is expected to hit rather than a suggestion to dabble, and give people an easy way to share what's working so the best moves spread fast. Push proficiency at the first two stages hard, not as the destination, but to clear the hours and the headspace that stage three and four demand.
4. Make the portfolio visible. You can't deliberately move what you can't see. Start simple: list every place AI is being used across the team and mark which stage each effort sits at. The moment it's on one page, the imbalance is obvious, and you can shift the mix toward three and four on purpose instead of by accident. That visibility is what turns four good intentions into a plan.
What to do this week
The four moves are the arc. Here's where you start this week. First, place your business or function on the four stages, honestly:
1 · Thought Partner. Someone on your team thinks through a problem in a chat window and gets a faster first draft.
2 · Assistant. AI pulls from your own data and produces real work, a plan or an analysis, that someone still reviews.
3 · Teammate. An agent runs a recurring process end to end and escalates only the calls that need a person.
4 · System. AI runs a core workflow continuously, making the routine decisions, while your team supervises it.
Then commit to the one capability you'd cross the line for, in a single sentence:
Our function is at Stage ___ today. With AI, we could finally ______________________ , something we never could before.
From the portfolio
The fourth move, seeing the whole portfolio, is the one most teams can't do on their own. AI shows up in a dozen places across the organization, a tool in one team, a pilot in another, with no single view of which efforts only add speed and which actually change what the business can do. Without it, no leader can tell which side of the line the business is on, let alone steer it across.
AlignAI gives you that view. It tracks every AI initiative across the business, classifies where each one actually sits, and governs the whole portfolio so it ships and scales instead of stalling in pilots. If a conversation there would help, reply and I'll make the introduction.
Everyone has the same tools now, so efficiency isn't an advantage anymore. It's the default. Aim AI at doing today's work with fewer people and it asks nothing of you, and quietly builds a smaller company. Aim it at making the people you already have capable of work the job never allowed, and it takes the one thing no tool can give you. Where you point it is a confession of what you believe your people are for, and they can read the answer.
Anyone can use AI to need less. It takes a leader to build more.
Talk Tuesday,
Jason Hauer
Founder & CEO, HauerX Holdings
jason@hauerX.com
Jason Hauer is the founder and CEO of HauerX Holdings, where he backs and builds a portfolio of AI-native companies that accelerate how businesses grow, operate, and compete. From mid-market to Fortune 500.
Frequently Asked Questions
What are the four stages of Notion's AI maturity model?
1. Thought Partner (57%): people draft and brainstorm on their own. 2. Assistant (31%): AI taps your data and speeds up real tasks. 3. Teammate (10%): agents run recurring workflows; people check them. 4. System (2%): AI runs critical work end to end. The line that matters cuts between stages 2 and 3.
Why is the line between stages 2 and 3 so hard to cross?
Below the line, anyone on the team can pick up a tool and speed up their own job. Above the line, redesigning what the work produces requires senior authorization. The study shows owners and senior leaders are several times more likely than their teams to have AI running real work. Not because they're better with the tools, because they're the only ones allowed to change the work.
Why is it called a courage gap, not a technology gap?
Making existing work more efficient is safe: it asks for no vision and risks nothing. Changing what the work is means committing to a view of where things are headed and being the one who's wrong if it doesn't land. That exposure is the real barrier, and it isn't technological. AI didn't create the courage gap. It stripped away the last excuse for not facing it.
Why aren't ChatGPT, Copilot, or Claude enough to cross the line?
Those tools are probabilistic: brilliant guessers, which is exactly what you want for a draft you're going to read and fix. That's stages one and two. Running real work end to end needs deterministic scaffolding around the model, guardrails and expert prompting that turn a good guess into a dependable system. That's the harness, not the chatbot.
What are the four moves that get a team across the line?
1. Show them what's possible with a working proof, not a strategy deck. 2. Take the fear off the table by promising the same people doing bigger work, not fewer people doing the same. 3. Get fluent fast at stages one and two, because mastery of the bottom funds the top. 4. Make the portfolio visible: list every AI effort and mark its stage, so the imbalance is obvious and you can shift the mix on purpose.
