There's a lot of AI FOMO right now. It's hard not to feel behind.
Should I have AI-specific roles, like forward-deployed engineers or a chief AI officer? Do we need a company second brain? Should we switch to Claude? Do we need agents? We need more agents!
In reality, AI adoption is similar to other change management initiatives we've been doing for decades — and we can deal with it the same way.
When I led the people function at the first company I helped build, we set aside one hour every month for our managers to talk openly about anything that was getting in their way.
We created 6 cross-functional groups. Each group had a senior leader facilitating, like me, but nobody in the room reported directly to that person. The meetings were built into everyone's regular schedule, with an open agenda. People could bring up challenges, ask questions, and get advice from their colleagues.
After just a few months, those conversations quickly became a huge differentiator in our company. We uncovered problems between departments. We solved them before they cost us time, money, or required someone in leadership. Our managers learned from each other and adopted better ways of working on their own.
Companies adopting AI should adopt this same kind of habit.
In the face of big change, leaders should build out time for questions, doubts and experimentation in their team’s regular workday. They should let employees work through uncertainty without having to seek out permission.
You can put this into practice in the next 30 days.
Here’s what we’re seeing the most successful firms do:
1. Reserve 10 minutes in an existing team meeting.
Make it a standing agenda item for the next month, dedicated to anything new that your team is navigating.
Start the conversation yourself. Share something you're still trying to figure out about AI, then ask your team what's unclear to them.
You can ask:
2. Let people work through the questions together.
When someone raises a concern, resist the urge to immediately provide an answer.
Ask whether anyone else has experienced the same thing. Invite colleagues to share what they've tried. Where people disagree, give them time to explain why.
3. Make sure something happens afterward.
Before the meeting ends, identify one issue the team can resolve or experiment with. Assign someone to own the next step, agree on what they'll do, and revisit it at the next meeting.
If it needs input from leadership, the manager in the room should take responsibility for getting an answer and bringing it back. People need to see that raising questions leads somewhere. Otherwise, they'll eventually stop asking.
I’ll give you an example when this worked for us. I remember sitting in one meeting when a lead technician mentioned a recurring problem that was forcing his team to return to job sites unnecessarily.
Another manager realized the problem was originating in his department. He had no idea it was happening.
They talked through the issue together and went off to fix it. I barely had to say a word.
These things happened with little initiative required from our managers to participate. Nobody had to ask for these meetings or find time for them. They were already on the calendar.
Critically, any time you choose to devote to this should be exclusively set aside — even if it’s just 10 minutes — so the burden isn’t on your employees to initiate the same discussions in other settings or other meetings. This is different from an open-door policy. While “open door” sounds welcoming, it still requires an employee to decide whether their question is important enough to interrupt their boss. (Most people will err on the side of caution and avoid it.)
Right now, lots of CEOs we work with are trying to figure out how to get their employees to embrace AI. Meanwhile, your employees are on the other side wondering whether AI will replace their job, whether they're allowed to use it for certain tasks, or what happens if they experiment and it doesn’t go well.
All that uncertainty consumes energy that could be spent learning and experimenting.
Harvard researchers Robert Kegan and Lisa Lahey described how employees often perform a "second job" alongside their actual work: managing impressions, hiding weaknesses, and trying to figure out what's expected of them.
Instead, give your people an hour a month with colleagues to work through challenges. Start holding regular one-on-ones. Or start with 10 minutes in a standing team meeting. Make it predictable and low effort.
The responsibility for creating these conversations sits with leadership. Your employees should be able to participate simply by showing up to meetings that are already part of their workday.
AI or not, you’ll build a habit that helps your team navigate any big change, whatever the next one turns out to be.
Thanks for reading. See you in three weeks.
— Alex