Your Team Uses AI. You Don't. Now What?
Maybe you're part of the problem
Everyone talks about AI adoption challenges. Data readiness, governance, licensing, ROI measurement. All valid. But after dozens of Copilot implementations, I can tell you the number one blocker is none of these.
It’s the manager.
Not all managers. But enough of them to slow down entire organizations. And most of them don’t realize they’re the problem. They think they’re being responsible. In reality, they’re protecting a leadership model that AI is making obsolete.
This episode is about what changes for managers when their team starts using AI. And what needs to change in how we think about leadership.
If you’re a manager and you haven’t opened Copilot in the last 10 days, you’re not leading an AI transformation. You’re watching one. And your team knows it.
Three Manager Archetypes That Kill AI Adoption
I can usually spot the management problem within the first few workshops. It falls quite often into one of three patterns.
The Blocker
The Blocker isn’t really blocking AI because they want to. It’s more because they’re protecting their position.
This manager built their career on knowing more than their team. More experience, more context, better answers. That’s how they got promoted. That’s their identity as a leader. And now a tool comes along that gives a (junior) team member access to the same knowledge, the same analysis capability. Suddenly that junior produces a client brief in 30 minutes that used to take the senior two days. That’s rather a identity crisis, than a technology problem.
So they don’t say “I’m afraid of losing my relevance.” They say “the quality isn’t reliable enough” or “we need a review process for AI-generated content” or “let’s wait until IT gives us clearer guidelines.” Sounds reasonable. But the intent is self-protection. The team stops using Copilot. It was never banned, but the friction became higher than the benefit
The Delegator
The opposite problem. This manager read an article, attended a conference, heard the CEO talk about AI. Now they tell their team: “We should all be using Copilot. Make sure you integrate it into your workflows.” Then they go back to their own work. Without Copilot. Without ever opening it. (Sometimes, they don’t realize that they don’t have a Copilot license, only Copilot Chat. 😁)
People are smart. When the boss tells you to use a tool they don’t use themselves, it sends one message: this isn’t really important. The Delegator creates the illusion of AI adoption without any leadership behind it. When results don’t come, they blame the tool.
The Time Traveler
This one might be the most common. And it’s dangerous because it sounds rational.
The Time Traveler tried Copilot. Maybe early 2025, maybe late 2024. They opened it, asked it to draft a presentation, got a weak result, closed it. “I tried it. Wasn’t useful.” The Copilot they tried doesn’t exist anymore. Early 2025, Copilot ran on GPT-4 Turbo. One prompt, one output. No memory. Limited access to organizational data.
Today? GPT-5.2 (or even GPT-5.3) with a Thinking Mode selector. Agent Mode in Word, Excel, and PowerPoint where Copilot iterates with you over multiple steps. Researcher that does deep search across the web and your organization. WorkIQ and Memory that remembers your preferences and work context. Claude from Anthropic as a second model already accessible in Agent Moden and Researcher. And even Grok is coming to Copilot Studio. Implicit grounding that automatically uses the email you’re looking at. 36 new features in February 2026 alone. Microsoft reported 3x more positive feedback, 17% higher satisfaction, and half the negative feedback compared to six months ago. That’s not an improvement. That’s a different product.
Judging Copilot 2026 based on a 2024 experience is like test-driving an electric car in 2015 and deciding you don’t need one in 2026, because of the range.
Knowledge is no longer Power
Ok so these three archetypes are the visible symptoms. The real issue is deeper and most people don’t want to talk about it. And most managers don’t want to hear it.
For decades, management authority had one big pillar: the manager knows more. From experience to information in the right context. The team comes with questions, the manager has answers. That’s how promotions worked. That’s how org charts got justified. AI breaks this now.
When a junior with Copilot and Researcher pulls together a market analysis in 30 minutes that used to take a senior two days, the information gap closes. When a project controller uses Agent Mode in Excel to build a variance report that previously only the finance director could produce, something shifts.
Knowledge is becoming a commodity. Anyone with a Copilot license has access to the same organizational data and the same analysis tools. (Of course depending on the permissions 🔐) And that’s uncomfortable for people who built their entire career on being the person who knew things.
But knowledge was never the real job. It just felt that way because access to knowledge used to be limited. The real job was always something else. AI is just making that visible now.
What AI can’t do: tell you which pricing strategy your specific client will respond to, given the political dynamics you observed in last week’s meeting. Summarize every email from the last month? Sure. Tell you that the tension between sales and product is really about a leadership conflict from six months ago, which you gained through trust and during a coffee talk? No chance. Generate 20 things your team could work on? Easy. Decide which three actually matter for Q2 given a strategic pivot nobody put in a spreadsheet? That’s you.
AI is great at answering questions. It’s not yet good at knowing which questions to ask, especially combined with empathy. And that’s becoming the most important leadership skill.
The shift: leadership authority moves from “I know the answer” to “I know what and how to ask, and I know what to do with the answer.”
The AI Leadership Shift
I see three shifts in how managers need to operate. Not theory. This is what I observe in organizations that get this right.
Controller to Enabler
The old way was reviewing every output, approving every step. The new way is creating the conditions in which your team can use AI well. Define what good looks like. Set guardrails. Then trust your people. This doesn’t mean zero oversight. It means you shift from checking every prompt to checking the final deliverable. You’re not approving the tool. You’re coaching the human who uses it.
Knowledge Advantage to Judgment Advantage
You used to be valuable because you knew things your team didn’t. Now you’re valuable because you can evaluate and decide better than the tools can. And your are even better in combination with the AI tool. So use it 🤝. AI gives everyone access to information. Your job is turning information into decisions. And you need to use AI yourself to know when it’s right, when it’s close, and when it’s confidently wrong.
Task Distributor to Capacity Architect
You used to assign tasks on Monday morning. Now AI is doing parts of your team’s work. Some people save 20% of their time. What happens with that 20%? If you don’t answer that deliberately, the time disappears into inbox management. Frontier Firm managers think about saved time the way product managers think about roadmaps. It’s reinvestment capacity. And deciding where it goes is the manager’s job.
What Frontier Firm Managers Actually Do
I see three concrete behaviors that Frontier Firm Managers actually do.
They use Copilot themselves.
Not because they need to be power users. Because their team needs to see that this is how we work now. When a manager opens a meeting with “I asked Copilot to prep a summary of our last three project reviews, here’s what stood out,” that does more for adoption than any training session. Leadership is behavior, not policy.
They set AI ground rules for their team.
Not the vague stuff from IT. Specific rules. “First drafts with Copilot, fine. Final client-facing documents need human review.” “Meeting summaries go to the project folder within 24 hours.” “If you’re not sure about something Copilot produced, flag it in our Teams channel.” These rules reduce uncertainty. And uncertainty is what actually kills adoption.
They care about output.
They don’t ask “did you use Copilot for this?” They ask “is this good?” If the deliverable meets the standard and was delivered on time, the tool doesn’t matter. If it doesn’t meet the standard, the conversation is about quality. Not about AI.
On a Personal Note
I think about leadership a lot. In my Copilot workshops, in how I manage my team at Campana & Schott, even at the gym at 6am.
Something from my years in ice hockey keeps coming back to me: the captain doesn’t stand behind the bench and shout instructions. The captain is on the ice. Doing the work. Setting the pace. And is talking to the referee when needed to protect the time.
If you’re a manager and you haven’t opened Copilot in the last 10 days, you’re not leading an AI transformation. You’re watching one. And your team knows it.
Start today. Open Copilot. Try it on your own work. Make mistakes with it. Learn where it helps and where it doesn’t. And next Monday morning, show your team what you found.
That’s leadership. Everything else is just managing.