Brent Colescott

At the intersection of learning, talent, and the future of work.

The Strategic Moment L&D Has Been Waiting For Is Here. The Question Is Whether It’s Ready

The Strategic Moment L&D Has Been Waiting For Is Here. The Question Is Whether It’s Ready

The conversation about AI, L&D, and organizational strategy is loud this week. It should have been loud years ago.

The question L&D has been fighting for two decades: strategic asset or overhead dressed up with a competency model? The argument was always the same — more than compliance, more than the team that books the leadership retreat. The organizations that treat us strategically will outperform the ones that don’t.

Most of the time, that argument got polite acknowledgment. Then the next budget cycle arrived. Or the next CHRO.

Something shifted in the past 18 months. The skills organizations are scrambling to build — judgment in the face of AI-generated output, knowing when the model is wrong — aren’t technical. They’re learning skills. They’ve always been. The business now feels the cost of not having them every quarter, in a way it simply didn’t two years ago. The old pitch was “trust us, we’re strategic.” Nobody needs to pitch that anymore.

Last week I wrote about how AI is eliminating the entry-level roles where critical thinking traditionally gets built. That’s real. But there’s a flip side that deserves equal attention.

The early-career professional who grew up in an AI-native environment doesn’t approach a new tool the way someone with fifteen years of established workflow does. The leader who spent years building a process for a task that AI now handles in seconds has a complicated relationship with that change — some version of loss is in there, even when the efficiency gains are obvious. The person who never had that workflow? They’re already past that conversation. They pick up the tool, test its edges, rebuild the process around it, and move on. That’s not a junior hire doing a junior job faster. With structure, guidance, and a clear objective from L&D, it’s a different category of contribution entirely. The 10x productivity number attached to AI doesn’t come from giving a veteran a new interface. It comes from someone whose frame isn’t constrained by how things worked before.

I’ve been testing this myself — working with AI to ask questions I didn’t know how to frame, without defaulting to the patterns I’ve spent twenty years relying on. What changed wasn’t the interface. It was the willingness to not start with what I already know. That’s a learnable posture. L&D can build it intentionally, at scale.

The departments that got labeled overhead weren’t deficient in craft. They were pointing their expertise inward, measuring the quality of the process rather than the outcome the process was supposed to produce. There’s nothing wrong with having rigorous frameworks. The problem is when the framework becomes the product. The L&D functions I’ve watched earn real strategic credibility didn’t abandon their principles — they stopped treating design methodology as the deliverable and started treating business performance as the standard.

That’s the retasking available right now. The designers, facilitators, and platforms that L&D already owns don’t need to be rebuilt. They need to be redirected. AI enablement is a learning design problem. Building judgment under uncertainty is what facilitation exists for. Organizations need both, urgently, and L&D already has the people who know how to solve them.

Critical thinking was always what L&D was supposed to develop. The gap was always proving it. AI closes that gap — because now there’s a business outcome everyone can see: can your people use this tool and know when it’s wrong? That question has a measurable answer. And it has an owner, if L&D decides to claim it.

The field has been waiting for a problem the business urgently needs solved and can’t solve without us. That problem is here. The only question left is whether we lean into it — teaching people how to think, not just what to think.

Leave a Reply