A few years ago, most employees had ideas about how to improve their work. They just didn’t have the ability to do much about it.
If you wanted a new tool, you submitted a request. If you wanted to automate a process, you waited for IT. If you wanted to redesign how work happened, you hoped someone with authority agreed.
Today, a marketing manager can build an AI assistant before lunch. A salesperson can automate proposals. An HR director can redesign onboarding. An operations manager can create an entirely new workflow. They can do it rogue, without asking permission and without telling anyone.
The Inheritance Problem
Most leaders see this as a technology story. I see it as an inheritance story. The industry has a name for it: shadow AI, tools built and used without anyone in IT or leadership ever signing off. But calling it a security problem undersells what’s actually happening. Every tool an employee quietly builds becomes something the whole organization has to live with, whether or not anyone chose it. There’s no security review. No consistency, because five teams can end up solving the same problem five different ways, each with their own tool, their own logic, and their own version of the truth. No record of what the tool does or how it makes decisions. And when an employee leaves, the tool often leaves with them, or the knowledge of how it works and whether anyone can safely turn it off does.
Imagine a company with 300 employees. Marketing builds custom GPTs for campaigns. HR builds its own interview workflows. Finance automates reporting. Sales creates proposal generators. Operations builds project trackers. Every one of those tools might be excellent on its own. Together, they can create chaos: different assumptions, different terminology, different data structures, different security practices, different customer experiences. And it doesn’t stop at the department level. Three people on that same sales team might each build their own version of a proposal generator, none of them aware the other two exist, each one trained on slightly different assumptions about what a good proposal looks like. People aren’t just bringing their own devices anymore. They’re bringing their own intelligence systems, one person at a time, and that’s a leadership challenge organizations haven’t had to solve before.
This isn’t a hypothetical. Start with individual behavior: Microsoft and LinkedIn’s 2024 Work Trend Index found that 78 percent of AI users already bring their own AI tools to work rather than wait for a corporate-sanctioned option, a habit the report calls “Bring Your Own AI.” That figure doesn’t measure how many people use AI. It measures how the people who already use it behave once they do.
Now layer in how fast that pool of people is growing. Gallup’s latest quarterly tracking shows individual AI use at work has grown from 21 percent to 52 percent in three years, and organizational adoption jumped six points in a single quarter this year, from 41 percent to 47 percent. The Federal Reserve found that 78 percent of the U.S. labor force now works at a firm that has adopted AI in some form. Put those trends together, and the math gets uncomfortable fast. If even a fraction of that same bring-your-own-AI habit holds as adoption climbs, the number of employees quietly building with tools nobody sanctioned isn’t holding steady. It’s compounding in step with adoption itself.
The tools are already inside your organization. The real question isn’t whether anyone can see them. It’s what they’re already doing to your organization’s future.
The Readiness Gap
Recently, I was listening to Fareed Zakaria’s interview with Microsoft CEO Satya Nadella on CNN when he described how he’s “developing” again. When he thinks of a tool that would make his work easier, he simply builds it with AI.
That reminded me of a conversation I had with Salil Kulkarni, founder of Virima. When I asked him about his patents, his answer wasn’t about technology. He noticed friction. He built something that made the work easier. Then he moved on to something more meaningful.
That’s what innovators have always done. AI didn’t invent that mindset. It just made the tools to act on it available to millions more people.
The readiness gap and the inheritance problem are the same issue seen from two different angles. Readiness means the thinking ability, courage, and training to act on what they see. Inheritance is what happens to what they build once it’s out in the world, and right now most organizations don’t have a plan for either.
Here’s the thing. Handing everyone the same AI tool treats it like software, not intelligence, and that limits what’s actually possible. Software is something you install once and expect everyone to use the same way. Intelligence adapts to the person using it, which is exactly what a single standard deployment can never capture. Employees will keep building their own personalized solutions anyway, because no single tool fits how everyone thinks. Leadership’s job isn’t to stop that. It’s to give it a sanctioned path, so personalization happens in the open instead of in the shadows.
But a sanctioned path isn’t enough on its own. AI removes the technical barrier to building something. It doesn’t give anyone the thinking ability to spot the right problem, the courage to question how things work, or the training to build something that holds up. That’s the real difference between an employee who owns a problem and one who’s just been handed a tool. For most of the Industrial Age, organizations trained people to follow a process, not question it. Now they need to train people to be innovative and creative in a way they never were before. Skip that step, and the readiness gap turns into inequality between employees, along with real inefficiency and lost productivity across the organization.
That’s the part most organizations haven’t reckoned with. Access to AI is now nearly universal inside a company. The readiness to use it well is not, and neither is a structured way for one person’s good idea to become something the whole team can use. Some employees will look at a clunky process and immediately see three ways to fix it. Others will use the same tools to do the same work slightly faster and stop there, not because they lack access, but because no one ever taught them to see their work as something they’re allowed to redesign, or gave them anywhere to bring the redesign once they had it.
AI democratizes building. It does not democratize systems thinking, and it doesn’t build a sanctioned path that turns a person’s fix into everyone’s advantage. Someone can build a workflow that saves them four hours a week while quietly making life harder for everyone downstream, and that’s classic local optimization: the organization grows more fragmented even as each individual becomes more productive. Without a sanctioned path, personalization and fragmentation are the same thing. With a sanctioned path, personalization becomes the source of the organization’s best ideas instead.
A real plan starts with an honest assessment of where the readiness gap actually sits, team by team, instead of assuming everyone crossed the same starting line the day the AI tools arrived. From there, it means building training that teaches people to question a process, not just prompt a chatbot. And it means creating an actual intake channel, a place where a personal build gets reviewed and tested. Some of it will be worth adopting org-wide. Some of it will only ever help the one person who built it, and that’s fine too, as long as it has the guardrails that protect the company.
Why the Gap Is Visible Now
For years we’ve told people to own their careers, keep learning, build their networks, develop new skills, and stay relevant. We shifted the responsibility for growth from the organization to the individual, and people accepted it. Now AI hands them the means to act on that responsibility. Some people were already prepared to use it. Others were told to think like an owner without ever being given the training or the room to practice it.
That gap used to be invisible. When building a tool required an engineering team and a budget line, almost nobody could act on their ideas, so the gap between people who noticed problems and people who didn’t rarely showed up in results. Now it shows up everywhere. Two people with identical access can produce wildly different outcomes, and the difference has nothing to do with the technology. Both of them have access to the same AI, the same tools to build with, the same ability to create their own solution. Technology plays a role here, but it isn’t the deciding one. What separates them is curiosity and the courage to act on it: whether anyone ever taught one of them to question the process in front of them instead of just accepting it, and whether either of them has anywhere to take a good answer once they find one.
That’s the inconsistency leaders need to plan for. It isn’t a rollout problem you fix by buying more licenses. It’s a capability gap that existed before AI arrived and that AI is now making visible inside every team.
The Trust Problem
For most of the Industrial Age, organizations hired people to execute work. Today, they’re increasingly hiring people to improve the work. Execution requires compliance. Improvement requires ownership, and ownership requires both trust and preparation. An organization that hands out AI tools without building the thinking skills and the psychological safety to use them is just widening the gap.
I think of healthy organizations as ecosystems of partners rather than hierarchies of employees. Employees complete assigned work. Partners build something together, challenge assumptions, and improve the system because they believe they’re creating something larger than themselves. That partnership only works when the organization invests in giving people the judgment to act, not just the software to act with.
Closing the Gap
The technology is not the constraint. The organization is, and that means the fix isn’t a better tool. It’s a different definition of what leadership does.
That comes down to three deliberate moves.
- Build readiness before access. Teach people how to spot the right problem, question how work currently gets done, and know when to stop optimizing their own corner of the business and think systemically instead. Access without that training just produces more people building the wrong things faster.
- Claim the inheritance before it claims you. Define what problems are worth solving, what standards everyone builds to, and what data gets shared instead of siloed. Give employees a visible, sanctioned path for building and sharing what they create, so nobody has to go rogue to get something built. A good experiment becomes an organizational capability instead of staying one person’s personal productivity hack, and the work stays inside the organization instead of walking out the door with whoever built it.
- Build trust before you ask for ownership. Partnership only works in both directions. You can’t ask people to challenge assumptions and build like owners while treating their judgment as optional the moment it’s inconvenient. Trust is what turns access into ability, and it’s the one part of this that no amount of structure can manufacture on its own.
AI isn’t changing organizations because it writes better emails. It’s changing them because it exposes a gap that was always there between employees who were ready to build and employees who were only ever asked to follow instructions. AI didn’t create that gap. It just made it visible and impossible to ignore. Leadership’s choice now is simple: close that gap deliberately, or watch it widen on its own.
Your employees are already building the future of your company. The question is whether you’ve given all of them what they need to build a successful one.
If you’re not sure where your organization’s readiness gap actually sits, let’s talk.
Oh, and one more thing…
Each week I like to share something practical alongside these ideas. This week, it’s my resource library: a growing collection of tools, assessments, books, and videos organized around the challenges leaders are actually facing right now, including a full collection on AI readiness and adoption. Take a look at amplifiedconcepts.com/resources.