Skip to content
Nerdy beta

Experiential Learning

Add to Space
 Team Dynamics Learning

Training attempts (and usually fails) to teach people what to think. Experiential learning changes how they work, because the learning happens inside the work itself.

Overview

Experiential learning, as we run it, is a time-boxed engagement where coaches embed with a product team and work alongside them on real deliverables. You’ll also hear it called immersive learning, or the dojo. That last name is the origin: a dedicated practice space, borrowed from martial arts, where skills are developed through repetition and feedback, not lectures.

A typical engagement runs 6-12 weeks. The team brings its actual product roadmap, not a training exercise. Coaches pair with team members daily, teaching techniques in context as the work demands them. It’s realtime adaptation of abstract concepts aimed with better delivery as the goal.

The approach rests on a few principles that separate it from conventional training:

  • Real work, not simulations. The team ships production code, runs real discoveries, and solves actual problems. Learning and delivery happen simultaneously.
  • Dial down delivery pressure. Stakeholders agree up front that the engagement prioritizes learning velocity over feature throughput. This is the negotiation that makes the rest possible.
  • Safety first. Coaches create the conditions for psychological safety so people ask questions, admit gaps, and try unfamiliar techniques without fear. The Skills Matrix exercise explicitly frames skill gaps as coaching opportunities, not performance issues.
  • Work small. Short iterations (typically 2.5 days), limited WIP, and continuous feedback loops. The team practices flow at a pace that allows reflection.
  • Buddy system. Every team member pairs with a coach or a more experienced peer. Nobody learns alone, and the pairing accelerates knowledge transfer in both directions.
  • Full commitment. The team dedicates 100% of its time for the engagement period. Half-attention produces half-results. Stakeholders, managers, and the team itself sign on before the challenge begins.

The structure follows a predictable arc: consultation (fit and readiness), framing (alignment on purpose, objectives, skills, and agreements), discovery (collaborative mapping and backlog creation), rapid iteration (build-learn-adapt cycles), and exit with a transition plan that sustains the new practices.

What makes experiential learning different from “embedded coaching” or “training with labs” is the combination of duration, intensity, and real stakes. Six weeks is long enough for new habits to take root. Working on real problems means the team cannot dismiss the techniques as academic. And the coach-beside-you model means feedback is immediate, not delayed until a retrospective two weeks later.

The name is borrowed on purpose. Kolb’s Experiential Learning Cycle is the theory: do, reflect, conceptualize, experiment, repeat. This engagement model is that cycle run at team scale, every iteration, for six weeks straight. Each pass builds conviction. By week six, the team isn’t doing new practices because a coach told them to; they’re doing them because they’ve seen the results.

When It Works Best

Reach for experiential learning when an organization needs to change how teams work, not what they know. Adopting Team Topologies, moving from project to product, introducing story mapping and continuous discovery, shifting from big-batch releases to small slices. A two-day workshop can teach any of these. On its own it can’t make them stick. That takes weeks of coached repetition, until the new way is just the way.

Skip it when the problem is purely technical (send them to a course), when leadership hasn’t committed to protecting the team’s time (the engagement will collapse under interrupt-driven work), or when the team itself doesn’t want to participate (coerced learning is an oxymoron).

Resources