Agile L&D summary

So what does agile Learning and Development actually look like in practice? Well, it starts with thinking like a product manager. Now, when I say "product," I don't just mean something you can hold or buy online. A product is anything that creates value for a specific group of people who share a common need or challenge – and when you solve their problem, you create value for the broader organization too.

Think about it this way: a commercial product like your smartphone solves multiple problems – communication, entertainment, productivity – and generates revenue for the company. An L&D product works similarly, except it's experiential. It might be a leadership development program, a skills workshop, or even something as fundamental as onboarding.

Imagine a company launching a compliance training program with 98% completion rates. Good, right? Well not when people click through rapidly, retain nothing, and keep making the same mistakes. The training technically "worked" but failed the humans it was supposed to serve.

This is why human-centered design matters in L&D. Traditional training design starts with what the business thinks people need – compliance requirements, skill gaps from annual reviews, or the latest leadership trend. Human-centered design flips this completely. It starts by understanding how people actually work, what frustrates them, and what would genuinely help them succeed. This approach sits within design thinking – that systematic way of solving problems by understanding users first, then testing solutions.

Picture this: four different emails from the same business function land in an employee's inbox within 24 hours. One from talent acquisition about new hiring processes, another from learning and development about mandatory training, a third from compensation about benefits changes, and finally one from employee engagement about a culture survey. Sound familiar? This siloed, dysfunctional communication is epidemic in large organizations. We all complain about it, we know silos are toxic, but what's the alternative?

Enter T-shaped employees working in T-shaped teams.

Here's a quick test: what's the difference between a pilot and an experiment? A pilot assumes success – it's basically a trial run of something you're pretty confident will work. An experiment, on the other hand, is designed to fail safely. And here's the thing – experiments can fail without serious consequences, while pilots really can't.

This distinction matters because iteration – that continuous cycle of building, testing, learning, and adjusting – is absolutely crucial to agile methodology. Agile teams fail fast to learn quickly, but for many L&D professionals, even the word failure triggers panic. By shifting from piloting training schemes to experimenting with learning products, L&D can integrate nimble iterations and instant feedback into everything they do.

If you work in L&D, you work in the people profession. But doesn't it sometimes feel like you're in the people pleasing profession? Trying to be all things to all people, delivering solutions that leave everyone mildly satisfied but no one truly excited? Here's where an agile mindset cuts through the noise: you can't be everything to everyone. Instead, shift focus to delivering maximum impact – what's going to create the greatest value for the biggest number of people?

When you combine all the agile principles we've discussed, delivering with impact becomes the natural result. And how do you get there? Through strategy. Now, strategy isn't some mystical concept –  it's simply a plan to create value. Other metrics like profit and performance are outcomes of good strategy, not ingredients. And crucially, strategy is iterative: constantly reviewed and refined.