The Slide Deck Problem Nobody Talks About

You have done it. I have done it. We have all sat through a Scrum training where someone walks through 60 slides explaining Sprint Planning, the Daily Scrum, and the Retrospective. The participants nod along, maybe take notes. By Friday, they remember almost nothing.

Here is the uncomfortable truth that most Scrum trainers eventually face: traditional slide-driven instruction is one of the least effective ways to teach a framework that is, at its core, about learning by doing. There is a funny paradox in this. Scrum is built on empiricism – transparency, inspection, adaptation – yet the dominant method of teaching it relies on passive absorption. We lecture people about self-organization. We present slides about continuous improvement. The irony writes itself.

What the Research Actually Says

The often-cited “learning pyramid” (sometimes attributed to the National Training Laboratories) suggests retention rates drop dramatically with passive methods. While the exact percentages in that model are debated, the directional insight holds up: people retain more when they practice, discuss, and teach others than when they sit and listen.

More rigorous evidence comes from David Kolb’s experiential learning cycle. Kolb argues that effective learning requires four stages: concrete experience, reflective observation, abstract conceptualization, and active experimentation. A typical slide-based Scrum workshop hits one stage – maybe two if you include a Q&A. That leaves half the learning cycle untouched.

A 2010 MIT study measuring brain activity in students found that classroom lecture engagement was roughly comparable to watching television. Not exactly the neurological environment you want when people are supposed to internalize a new way of working.

So what happens when you remove the slides entirely?

Techniques That Actually Work

Simulation Games

Simulation is perhaps the most direct way to teach Scrum without explaining it first. Instead of describing what a Sprint Review looks like, you put people through one. Instead of defining the Scrum Master role, you let someone experience the tension of facilitating a team that wants to skip the Retrospective.

The key is choosing a simulation where the “product” is engaging enough that participants care about the outcome but simple enough that it does not require specialized skills. Building with Lego bricks is one well-known approach. Writing a collaborative crime story – as teams do in ScrumTale – is another. The narrative format has an interesting advantage: story writing mirrors real product development more closely than construction tasks do. There are ambiguous requirements, creative disagreements, and the constant question of what “done” actually means when the product is subjective. Participants end up debating Definition of Done not because a slide told them to, but because they genuinely disagree about whether their story’s plot twist makes sense.

Fishbowl Exercises

Set up an inner circle of five people running a simulated Daily Scrum. The outer circle observes. After three minutes, stop and debrief. What worked? What felt awkward? What would they change?

This technique is remarkably effective for teaching Scrum events because it makes the structure visible. Participants see the mechanics from the outside before stepping into them. You can run fishbowls for Sprint Planning, Backlog Refinement, even Retrospectives. The debrief conversations are where the real learning happens – and they require zero slides.

Physical and Visual Materials

Sticky notes on a wall beat a Kanban board screenshot on a projector every time. When participants physically move cards from “To Do” to “In Progress” to “Done,” they develop muscle memory around the flow of work. Some trainers use index cards for Product Backlog Items, letting the Product Owner literally hand them to the team. The tactile experience creates a reference point that outlasts any diagram.

For estimation, actual Planning Poker cards in your hands create a different dynamic than an app on a screen. The physical act of revealing a card simultaneously, seeing the spread, and discussing the gaps – that is where the understanding of relative estimation lives.

Discovery Over Instruction

The most powerful thing about removing slides is what replaces them: discovery. When a team runs through two Sprints of writing a crime story and realizes on their own that they wasted Sprint 1 because they never clarified the acceptance criteria with their Product Owner, they do not need you to explain why Sprint Planning matters. They felt it.

This is particularly noticeable in simulation-based workshops where the facilitator intentionally introduces friction. A stakeholder changes priorities mid-Sprint. A team member “leaves” the project. The Product Owner realizes the market has shifted. These moments mirror real organizational challenges, and participants develop responses through experience rather than theory.

In crime story simulations, this plays out organically. One Sprint produces a brilliant opening chapter. The next Sprint’s team writes an ending that contradicts the first chapter entirely. Suddenly the group is having a genuine conversation about integration, incremental delivery, and why working in small batches matters. No one had to present a slide about it.

The Facilitator Mindset Shift

Running a Scrum workshop without slides demands a different skill set from the trainer. You are no longer the expert dispensing knowledge from the front of the room. You are a facilitator creating conditions for insight.

This means getting comfortable with silence. It means resisting the urge to explain a concept when a team is struggling – because the struggle is the lesson. It means designing experiences that surface the right questions at the right time and trusting that the group will find the answers.

The best Scrum trainers I have observed share a common trait: they talk less than their participants. They ask questions instead of providing answers. “What happened in that Sprint?” is more powerful than “Here is what should have happened.” They create space for the team to articulate their own insights, which is – not coincidentally – exactly what a good Scrum Master does in a real organization.

Rethinking Your Next Workshop

None of this means information has no place in Scrum training. There are moments when a clear explanation of the Scrum Guide is exactly what participants need. But that explanation lands differently when it comes after they have already experienced the problem it addresses.

Consider this for your next workshop: instead of opening with a framework overview, open with an experience. Let the team stumble through a Sprint without knowing the rules. Then introduce the Scrum framework as a response to the challenges they just encountered. The shift from “here is what Scrum is” to “here is why what you just experienced was hard, and here is how Scrum addresses it” transforms passive recipients into active learners.

The slides can stay in your backup folder. Your participants will thank you for it.