Allan's Test blog

What happens when L&D stops delivering learning and starts designing for it?

Written by Emilia Åström | Jun 16, 2026 1:17:53 PM

There's a question that keeps surfacing in L&D circles: Are we actually positioned to close the gap between business strategy and daily performance?

On April 23, eighteen senior L&D leaders gathered in Stockholm to explore that question. Three practitioners took the stage to share what they're seeing, trying, and learning. What emerged wasn't just a framework. It was something more useful: a set of honest, forward-looking perspectives from people already doing this work at a high level.

The thread running through all three conversations? The role of L&D is not to deliver learning. It's to design the conditions where learning can happen: in teams, in communities, and in the flow of real work.

These are the three shifts that emerged:

Shift 1: From individual training to team-based capability

Hedvig Mossvall, Chief Growth Officer, GDQ Associates. Former Head of Center of Excellence for Team, Leadership & Skills Development, Spotify

The problem with building around the individual

Most L&D functions are built around the individual. Individual courses, individual development plans, individual performance conversations. The assumption (often unspoken) is that if you develop enough individuals well enough, the organization will follow.

It doesn't. Not reliably, and not at scale.

Where learning actually sticks

Learning is relational. You can develop skills individually up to a point. But the moment that learning meets the reality of other people (other perspectives, other habits, other assumptions) that's when it either takes root or disappears. The team is where knowledge becomes behavior. Where new approaches get tested, challenged, refined and eventually embedded. And if L&D isn't designing for that environment, we're missing the place where real change happens.

What this looked like at Spotify

Hedvig led an initiative to democratize team development, making it available to all teams across the organization, not just leadership teams. Teams entered the process together. Progress was measured at the start, after three months, and after a year. What they found: teams consistently developed, leaders gained a more holistic view, and people were more satisfied with their teams, their leaders, and their own growth. Critically, the development wasn't something that happened to teams from the outside. It was something teams learned to drive themselves.

Why the skills gap persists

The skills every leadership program claims to build (communication, collaboration, psychological safety) can't be taught in a classroom. You can introduce the concepts. But they only take hold in the context of real teams doing real work together.

"No one owns team development." When it's no one's explicit responsibility, it happens by chance. L&D has both the mandate and the capability to change that.

The takeaway: You can't outsource a learning culture. But you can build the conditions for one, and team development is where those conditions take root.