# Agile L&D by Natal Dank - Blinkist

What’s in it for me? Bring your L&D up to speed.

We live in a world where everything feels like it's moving at breakneck speed – markets shift overnight, technology evolves before we can master it, and global events reshape our landscape faster than we can adapt.

Most business functions have responded by embracing agility and flexibility.

But Learning and Development often remains stuck in the slow lane.

Why?

Well, L&D traditionally operates in silos – whether that's a standalone team buried within HR, individual specialists focusing on narrow areas, or external consultants.

This old-school approach is too slow to respond to urgent needs, delivers one-size-fits-all solutions that can't be easily adjusted, and overwhelms employees with a confusing array of disconnected programs.

The traditional siloed approach to L&D just doesn't work for today's complex, fast-moving business challenges.

It's time for L&D to catch up and embrace the agile methodologies that have transformed other areas of business.

This Blink is full of tactics that L&D professionals need to steal from the agile playbook.

So, let’s get into it.

What is agile, anyway?

Throughout history, businesses have weathered massive paradigm shifts – from the Industrial Revolution to Ford's manufacturing model, through world wars and the COVID pandemic.

But today's challenges feel different.

We're dealing with AI acceleration, rapid technological innovation, tangled global supply chains, climate emergencies, and geopolitical tensions all at once.

It's a perfect storm of complexity.

One piece of good news is that this is precisely the kind of environment agile methodology was designed for.

Agile emerged in the early 2000s within software development, where teams needed to respond quickly to changing requirements rather than follow rigid, long-term plans.

At its core, agile focuses on putting the customer at the center and moving through continuous cycles of planning, doing, reviewing, and adapting.

Think of it this way: traditional "waterfall" methods are like building a house – you design everything upfront, then execute the plan step by step.

Agile is more like gardening – you plant, observe what's working, adjust your approach, and keep iterating based on what you learn.

Now, here's what's interesting – agile has spread far beyond its software origins.

Marketing teams use it for campaign development, HR departments apply it to recruitment processes, and finance teams leverage agile for budget planning.

Why?

Because it works for any environment where you need to stay responsive and adaptive.

So why haven't Learning and Development teams jumped on this bandwagon?

Well, that's the million-dollar question.

L&D is still largely operating like its 1995 – lengthy needs assessments, annual training calendars, one-size-fits-all programs rolled out company-wide.

Meanwhile, the business challenges L&D needs to address are becoming more complex and fast-moving every day.

The disconnect is obvious.

If agile methodology can transform software development, marketing campaigns, and budget planning, imagine what it could do for how we develop people and build organizational capabilities.

It's time for L&D to catch up.

Creating your L&D product

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.

In fact, let’s take onboarding as an example.

Traditional L&D might create a generic week-long orientation program and call it done.

But agile L&D starts by asking: what are the real pain points here?

Maybe new hires feel overwhelmed, managers don't know how to support them, or people are taking months to become productive.

An agile approach would create targeted "onboarding products" that solve these specific problems – perhaps a digital buddy system, manager toolkits, or role-specific learning paths.

Here's how the agile L&D product development lifecycle works: First, you identify the business challenge and analyze the strategic value of solving it.

Then comes research and discovery – what problems are we actually solving for people?

Next, you agree on scope and create a product vision – how will we solve it?

The magic happens in co-creation and incremental delivery, where you deliver value early and often, testing and refining as you go.

Finally, there's ongoing product maintenance and portfolio management.

This approach transforms L&D from a "build it and hope they come" mentality to a customer-obsessed, value-driven function.

Instead of annual training calendars filled with generic programs, you're continuously developing, testing, and refining learning products that solve real business problems.

The result?

Learning experiences that people actually want to engage with because they're designed around genuine needs, delivered in digestible chunks, and constantly improved based on feedback.

That's the power of product-led thinking in L&D.

Put your people at the centre of your design thinking

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.

So when you're facing a specific business challenge, where do you start?

With deep research into your actual users.

Try creating personas, but make them laser-specific.

Instead of designing for "all managers," create "Sarah, the first-time supervisor juggling client demands while learning to lead.

" These detailed profiles force you to design for real people with real constraints, not abstract categories.

Once you've gathered all this research, you need to synthesize it into actionable insights.

Gallery walks work brilliantly for this – imagine your team posting sticky notes with research findings across the walls.

"Managers avoid difficult conversations," "People want peer mentoring," "Current tools don't fit remote work.

" As everyone walks around reading, patterns start jumping out organically.

Maybe three different personas all struggle with confidence, or multiple journey maps reveal the same enrollment friction point.

But here's the critical thing to watch out for: our brains love confirmation bias.

We unconsciously gravitate toward findings that support what we already believed, or we let the most vocal complainers drive all our design decisions.

Force yourself to look for contradictory evidence and quiet voices too.

This research synthesis leads you to the crucial final step: defining the problem with surgical precision.

Compare these two problem statements: "People need leadership skills" versus "New supervisors struggle transitioning from peer to manager, creating team tension and productivity gaps.

" The first is vague and leads to generic competency training.

The second is specific and actionable.

It points directly toward peer transition workshops, conflict navigation tools, or manager buddy systems.

That precise problem definition becomes your north star.

Instead of building learning products based on what we think people need from our L&D offices, you're now solving real challenges that people face in their actual workflow.

The difference in engagement and impact is dramatic.

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.

The best teams are T-shaped

We all complain about it, we know silos are toxic, but what's the alternative?

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

Think of the letter T.

That horizontal stroke represents broad generalist skills where you have solid, working-level capacity across multiple areas.

The vertical stroke?

That's your deep specialist expertise where you're the go-to expert.

In today's people profession, you need both: the flexibility to work across diverse challenges and the depth to provide expert leadership when needed.

Take Chitra, an HR business partner.

Her horizontal skills span employment law basics, project management, data analysis, and change management – enough to collaborate meaningfully across functions.

Her vertical expertise?

Organizational development and culture transformation.

She can facilitate a restructuring conversation, interpret employee survey data, and design culture change initiatives.

More importantly, she understands how these pieces connect.

Now imagine Chitra’s part of a T-shaped L&D team.

Everyone shares core horizontal skills – design thinking, stakeholder management, basic data analysis, and business acumen.

But each person brings different vertical expertise: one specializes in leadership development, another in digital learning platforms, a third in performance consulting, and Chitra focuses on organizational development.

This structure makes teams naturally agile.

When a complex business challenge emerges –  say, supporting a merger – the team can quickly reconfigure.

The leadership specialist handles executive coaching needs, the digital expert creates integration platforms, the performance consultant addresses productivity concerns, and Chitra manages the cultural integration.

They're not waiting for approvals or handing off between departments.

T-shaped teams eliminate silos because everyone speaks enough of each other's language to collaborate seamlessly, while still bringing deep expertise when needed.

Instead of four confusing emails, employees get one coherent strategy delivered by people who actually understand how all the pieces fit together.

Don’t pilot, experiment

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.

So how do you build an L&D experiment?

Keep it ruthlessly simple.

Don't overcomplicate with multiple variables, and be crystal clear on what you're actually testing.

Here's the trap: you might have a whole solution in mind, but you're not testing that yet.

In initial stages, you're simply testing whether your core assumption is correct.

Every experiment needs a clear structure.

Start with your aim –  what business problem are you solving?

Then identify your assumption –  what you believe to be true.

From there, craft your hypothesis around what should happen if that assumption is correct.

Define your testing method and measurement criteria, then plan your next steps based on results.

Let's say your organization struggles with internal mobility.

People want to move roles but don't know what's available, so your team wants to develop an internal job marketplace product.

Your first experiment might test whether employees actually want more visibility into internal opportunities.

You'd hypothesize that sharing weekly job alerts will generate strong engagement – maybe forty percent open rates.

So you send alerts to fifty volunteers for four weeks and measure response.

If that works, experiment two might test whether people want peer insights beyond job descriptions, so you'd add employee testimonials to those alerts.

Experiment three could explore career pathway guidance.

Each experiment builds on the last, gradually developing a robust marketplace through rapid, low-risk iterations.

This approach transforms L&D from risky big-bang launches into continuous improvement engines that actually work.

Maximize impact

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.

Your strategy follows three phases: identify, prioritize, and deliver value.

First, identify through regular diagnostics.

Extract business priorities by liaising with managers about burning issues.

Track employee experience health through people dashboards, monitoring key touchpoints in the employee journey.

Assess culture and capability gaps.

This creates your list of problems to solve and products to develop.

Next, prioritize using value-versus-effort mapping.

Consider value drivers like strategic priority, time-criticality, impact level, risk, and employee pain points.

For effort, factor in dependencies on other functions, complexity, required capabilities, timeframes, and resource constraints like tools and budget.

Finally, delivery.

Visualize work at portfolio level for the big picture and detailed backlogs for each initiative.

Most L&D teams juggle multiple projects simultaneously, each with different cycles.

Rather than tracking individual projects, establish a monthly strategic cadence to coordinate releases and maintain big-picture coordination without meeting overload.

Once delivered, measure impact through four data types: operational data like turnover and vacancy rates from your people dashboard; experience data from exit interviews and feedback ratings; innovation data tracking cost per experiment and testing results; and product data measuring employee lifetime value – similar to how companies track customer lifetime value against acquisition costs.

Now let’s see this in action.

Picture an L&D team facing high sales turnover.

Their diagnostics reveal new hires struggle with product knowledge and feel unsupported.

Using value-effort mapping, they prioritize a mentorship program as high-value, medium-effort.

Their delivery plan coordinates manager training, peer matching systems, and progress tracking through monthly strategic reviews.

Success is measured through reduced turnover, improved new hire feedback, mentorship experiment costs, and increased employee lifetime value.

This systematic, agile approach turns L&D from a back-office function into a true driver of business results – proof that learning done right doesn’t just train people, it transforms the organization.

Final summary

The main takeaway of this Blink to Agile L&D by Natal Dank is that Learning and Development teams need to abandon traditional siloed, slow-moving approaches and embrace agile methodologies that put people at the center of design thinking.

This means shifting from annual training calendars to product-led thinking, where L&D creates experiential “products” through continuous cycles of research, experimentation, and iteration – grounded in real user needs rather than assumptions.

The ultimate aim is to build T-shaped teams capable of delivering maximum impact by strategically prioritizing initiatives, moving beyond people-pleasing to addressing genuine business challenges with measurable outcomes.

Okay, that’s it for this Blink.

We hope you enjoyed it.

If you can, please take the time to leave us a rating – we always appreciate your feedback.

See you in the next Blink.