A senior marketing leader told me something recently that I haven't stopped thinking about.
His team was a few weeks into a major AI rollout. Enthusiasm was high. A small cohort of internal champions had been trained. Core work processes were being reimagined. By every early measure, it was going well.
Then he paused and said: "The people who are going to struggle are the ones who've been hiding behind the process."
He wasn't being harsh. He was being precise.
I've coached enough leaders through transformation to know what he was describing. Every team has people whose contribution is real — but whose visibility comes from managing the machinery of work rather than driving the outcomes of it.
- Coordinating.
- Formatting.
- Shepherding.
- Moving things from one inbox to another.
That work isn't nothing. But it isn't the job.
When the machinery gets automated, what's left is the actual thinking. The judgment. The ability to look at a business problem and know which question to ask before anyone else has figured out what the question is. And for a lot of people, that exposure is uncomfortable — not because they're bad at their jobs, but because they've never had to prove they're good at the part that matters most.
This is the Talent Trap in its most modern form. Leaders build teams around task completion, then wonder why the team can't think strategically. The tasks were never the job. They were the camouflage.
The Clarity Problem
Here's what most leaders get wrong about this moment: they treat it as a technology problem. It isn't. It's a clarity problem that technology is finally forcing you to solve.
The leader I spoke with had already started solving it — a year and a half before the rollout. His team had gone through a talent assessment process. Everyone was required to create their own development plan. Not a plan handed down from HR. A plan the individual owned.
That decision, made long before anyone was talking about AI, is what made the transformation possible. He didn't know it at the time. But he'd already built the container his team would need.
Most leaders haven't. They're launching new tools into organizations where no one has ever been asked to articulate what they're actually trying to get better at. The tools surface the gap. The culture has no way to hold it.
Three Pre-Rollout Priorities
If you're leading your team through any kind of significant change — AI or otherwise — three things are worth doing before the rollout, not after:
- Name the skills that will matter. Critical thinking. Business acumen. The ability to connect your team's work to the outcomes the business actually cares about. If your people don't know these are the skills that determine their future, they can't prioritize building them. Say it out loud. Say it early. Say it more than once.
- Make development something people own. The moment you hand someone a development plan, you've made growth your problem. The moment you require them to create one, you've made it theirs. That's not a small distinction. People who own their development are far more likely to lean into change than resist it.
- Separate the work from the worker. Look honestly at what your team spends its time on. Ask which tasks require genuine judgment and which are process-dependent. The answer will tell you more about your team's real skill distribution than any performance review ever has.
The leaders who navigate transformation well aren't the ones who move fastest. They're the ones who were already building the right foundation — and had the clarity to see what change would expose before it arrived.
What would a hard look at your team's work reveal about the skills you've actually been developing?