The Lunch-and-Learn That Actually Teaches

The lunch-and-learn is the most beloved format in workplace learning and the least examined. Everyone likes it: the expert gets an audience, the team gets pizza, the calendar gets a recurring block that feels like culture, and leadership gets to say learning happens here. The only party poorly served is the learning. Because the default format — an expert talks through slides for forty minutes, questions at the end, recording posted for the people who skipped — is a podcast with worse acoustics. Ask attendees a week later what changed in how they work and you get the answer the format was built to produce: it was interesting.

“Interesting” is the tell. Interesting is what content achieves; different-on-Thursday is what training achieves, and the gap between them isn't the speaker's skill or the topic's fit — it's structure. The good news is that the fix doesn't need more time, budget, or a reluctant SME to become a performer. Forty-five minutes is genuinely enough, restructured around three commitments: one decision, one practice rep, one artifact.

One decision, not one topic

The default session is scoped as a topic — “intro to our data pipeline,” “security basics” — and topics are bottomless, which is why every deck runs long and shallow. Scope it instead as a decision the audience actually faces: not “security basics” but “when you get an unexpected file-share request, what do you do in the first minute?” Not “intro to the pipeline” but “how to tell whether your dashboard is stale before you present it.” A decision scope does three jobs at once: it forces the SME to cut (the slides that don't serve the decision visibly don't belong), it guarantees relevance (the audience recognizes the situation from their own week), and it makes the session assessable — you can watch someone make the decision at minute thirty, which is the whole point.

One practice rep, in the room

The middle fifteen minutes are the session. Present the scenario — a real one, lightly anonymized: the actual suspicious email, the actual stale dashboard — and have people work it before the expert weighs in. Pairs beat solo (talk is faster than writing and nobody hides), and the expert's job flips from performing knowledge to reacting to attempts: that instinct's right, here's the edge case; that's the common trap, here's what it costs. This is the same mechanism that makes reinforcement work — retrieval and attempt, not exposure — compressed into one room. It's also, quietly, a needs assessment: the wrong answers in the room tell you what the next session should be, which beats any topic-suggestion survey ever run.

One artifact that leaves the room

Not the deck — nobody reopens the deck. The artifact is the decision, compressed onto something that lives where the work happens: the one-page checklist, the decision tree pinned in the channel, the three-question “before you hit send” card. The test of a good artifact is that someone who missed the session can use it, and someone who attended actually does. If the session can't produce one — if the material resists being compressed into a usable page — that's diagnostic too: the scope was a topic after all, and it wants either a real course or a proper outline instead of a lunch slot.

Prepping the SME in twenty minutes

Your expert is not a designer and shouldn't have to be. The prep is one conversation: What's a decision people around here get wrong about your area? What does getting it wrong cost? Give me one real example we can put on screen. What are the two most common wrong moves? — which is a compressed version of the same SME interview you'd run for any build, and it yields the scenario, the distractors, and the artifact's skeleton in one pass. Then the format does the rest: ten minutes of setup from the SME, fifteen of attempts, ten of reaction and sharpening, ten to finalize the artifact together. The SME leaves feeling like an expert rather than a failed keynote speaker, because reacting to real attempts is the thing experts are actually good at.

The bottom line

The lunch-and-learn doesn't need retiring; it needs a spine. Scope it to one decision the room actually faces, spend the middle on a real attempt instead of a longer talk, and refuse to end without an artifact that lives where the work does. Same forty-five minutes, same pizza, same SME — but a week later the answer to “what changed?” has an object in it. Interesting is easy. Different-on-Thursday is the job.

— Tom