The Copilot Plateau
Why Most Organizations Are Stuck at 20% Impact
Over the past months, I have seen the same pattern repeat itself across many conversations with customers and organizations.
Last week, while teaching at a University of Applied Sciences as part of the CAS Strategic Office Management program, this pattern showed up once again: different roles, industries and levels of AI experience. A story I hear more and more on the market.
“I know Copilot can help. I just don’t really know how to start.”
Most participants already had access to Copilot. Many had tried it a few times. But when it came to using it in their own day-to-day work, hesitation set in. They knew Copilot could be helpful, but they were unsure how to start in a way that felt natural and reliable. (especially in super busy moments)
So people experimented a little, often without a clear direction. Sometimes the results were helpful, sometimes confusing. And without a sense of progress, many quietly stopped using Copilot again.
Not because Copilot did not work. But because it never became part of their daily flow.
This is what I increasingly see across the market as the Copilot plateau.
Organizations do not fail at Copilot adoption. They stall. The license is there. The capability is there. But the expected productivity impact never fully materializes. Instead, you see a few power users pushing ahead, many employees staying cautious, and a growing gap between promise and reality.
Why More AI Does Not Break the Plateau
When organizations notice this plateau, the instinctive reaction is to look at the technology.
Maybe the models are not good enough yet.
Maybe the features are still missing.
Maybe the next release will finally unlock the value.
That reaction is understandable. Most public AI discussions still focus on what is technically possible next. But better AI increases potential. It does not automatically increase impact.
Over the past year, Copilot has improved significantly. Models have become stronger, integrations deeper and the pace of innovation faster than most organizations can absorb. And yet, everyday usage often remains inconsistent and fragile.
The reason is simple: new capabilities do not change behavior by default.
If Copilot remains something people try occasionally, better AI will only improve those occasional moments. It will not turn Copilot into a natural part of the working day.
Without repetition, there is no familiarity.
Without familiarity, there is no confidence.
And without confidence, people fall back to the habits they already know.
This is where the problem is often misdiagnosed. Copilot adoption is treated as a capability challenge, when in reality it is a habit challenge. People are not asking for more features (ok, sometimes they do 😁); they are looking for clarity. They want to understand when Copilot is actually useful, how it fits into their flow, and how to rely on it without feeling slowed down or disappointed.
As long as that clarity is missing, adding more AI will not break the plateau. It may even make things harder, because more options without guidance tend to increase uncertainty rather than confidence.
To move beyond this point, the question needs to shift. Instead of asking what Copilot can do next, organizations need to ask how Copilot becomes a consistent part of everyday work. That is the moment when the plateau stops being a technical problem and starts becoming a design problem.
The Three Real Causes of the 20% Plateau
Once you stop framing the problem as technical, the plateau becomes easier to understand. It is not (only) driven by lack of interest or resistance. It is driven by the fact that Copilot never becomes a stable part of how people think and work. In practice and with my experiences, I see three underlying gaps show up again and again.
The first gap is that Copilot has no fixed place in the working day. For many employees, it remains optional. Something they might use if they remember, if they have time, or if the task feels important enough.
But optional tools always lose against urgency.
When pressure increases, people fall back to familiar habits. Without a clear default moment for using Copilot, consistency never has a chance to form.
The second gap is not about tooling. It is about AI-mindset.
Most people were never trained to work with AI. They were trained to use software. That difference matters. Using AI requires a different mental model: how to frame a task, how to think in outcomes instead of steps, and how to collaborate instead of control. (and to make it clear, processes need also this reframing) Without that mindset, Copilot feels unpredictable and exhausting, even when the underlying capability is strong.
If people approach Copilot with a traditional tool mindset, they expect precision and repeatability. When AI behaves differently, frustration sets in. Not because Copilot fails, but because expectations were never recalibrated.
The third gap is trust.
Many employees are unsure where Copilot is safe to use and where it is not. Can they rely on it for sensitive data? Are they allowed to use it in customer-facing work? What happens to the information they share? When these questions remain unanswered, people default to caution.
Uncertainty kills adoption faster than technical limitations. If employees do not trust the system, or do not trust themselves to use it correctly, they will keep usage shallow and defensive.
These gaps reinforce each other. Without a fixed place in the day, there is no routine. Without the right mindset, there is no confidence. And without confidence and trust, there is no depth of usage.
This is why so many organizations remain stuck at the same level of impact. (btw. the 20% are just a random number from myself 😁 not science based, but for make it clear) The plateau is not a Copilot / AI problem. It is a human and organizational one.
Breaking it requires more than better AI. It requires better preparation for working with AI.
How Organizations Break the Plateau
Breaking the Copilot plateau starts in most cases with everyday work.
Organizations that move beyond the 20% mark do not ask their people to use Copilot more often. They design their environment so that using Copilot becomes the natural choice in specific moments of the day. Instead of making AI optional, they give it a clear role in the flow of work.
This begins with mindset, but it does not stop there.
Helping people understand how to work with AI is essential, but that understanding needs to be grounded in reality. Without a clear connection to their own daily challenges, mindset training remains abstract. People may understand the concept of AI collaboration, but they still struggle to apply it when the workday gets busy.
That is why organizations that break the plateau start one step earlier: they seek to understand the real pain points in a typical day. Where does work feel repetitive, frustrating, or unnecessarily slow? Where do people lose time, context, or energy? Only then do they translate the AI mindset into day-in-the-life workflows.
Instead of showing feature after feature, they design role-specific scenarios that address these concrete challenges. Copilot is not presented as something new to learn, but as a way to remove friction from work that already exists. A manager preparing for meetings, a project lead summarizing updates, an assistant handling recurring coordination tasks. Each scenario starts with a familiar problem and ends with a noticeably easier outcome. This is where real “aha moments” are created.
When people experience AI solving a problem they recognize immediately, the value becomes tangible. It is remembered, because it is felt. That moment of relief and clarity does more for adoption than any generic demo ever could.
When Copilot is tied to a role, a pain point, and a specific moment in the day, repetition becomes possible. And repetition is what turns understanding into habit.
Trust is addressed in the same practical way. Clear guidance on where Copilot can be used, how sensitive data is handled, and where human judgment remains essential removes a major source of hesitation. When boundaries are explicit, people feel safer experimenting within them. Trust grows not from blind confidence, but from clarity.
None of this requires perfection. Organizations that move forward do not wait until everything is fully defined. They start with a few well-chosen, pain-point-driven patterns, reinforce them consistently, and refine them over time.
Breaking the plateau is not about pushing harder. It is about designing habits around real problems.
Over time, Copilot stops feeling like a new tool that needs attention. It becomes part of how work gets done. That is when productivity gains stop being theoretical and start showing up in everyday results.
Why 2026 is the Moment That Matters
Looking back, 2025 was the year of experimentation. Organizations explored Copilot, tested use cases, and tried to understand what was possible. That phase was necessary, and for many, it was even exciting. 2026 will be different.
The question will no longer be whether Copilot can create value. That has largely been answered. The question will be whether organizations are able to move beyond isolated experiments and turn Copilot into a consistent part of how work gets done.
This is where the plateau becomes decisive. Organizations that remain stuck at 20% will continue to see Copilot as something promising but optional. Usage will stay uneven, benefits will remain difficult to measure, and frustration will quietly grow. Not because people resist AI, but because it never fully fits into their way of working.
Organizations that move past the plateau will look different. Not louder or more experimental, but calmer. Copilot will feel less like a tool that needs explanation and more like an invisible layer that supports everyday work. The difference will not come from smarter models or more advanced features, but from clearer decisions about how AI is meant to be used.
In 2026, that difference will start to compound. In 2026, Frontier Firms will emerge and move better and faster.
Teams that have built habits, trust, and role-based patterns will move faster, adapt more easily, and create more room for higher-value work. Those who have not will struggle to scale, even as the technology continues to improve.
Breaking the Copilot plateau is not a one-time initiative. It is a design choice. A decision to focus less on what AI can do and more on how people work.
The organizations that make that shift will not just use Copilot more effectively. They will work differently. The become a Frontier Firm.
On a Personal Note
What encourages me most is not how fast the technology is moving, but how honest conversations around AI have become (at least in 1-to-1 conversation). More people openly admit that they feel unsure or stuck and that is a good thing.
Progress does not start with having all the answers. It starts with being willing to rethink habits. That is the journey I see organizations on right now, and the one I will continue to share here.
Ready to tackle the Copilot Plateau? Subscribe this newsletter ✨