The Research on Expert Performance Says Your Role Play Is Missing Its Most Important Ingredient

Most sales teams already do role play. Most sales teams also admit it doesn't really work. The room goes quiet, two reps stare at each other, someone reads a script off their screen, and by the following week nobody remembers a single line from it.

That's not a role play problem. That's a research problem: sales teams are just rediscovering something Anders Ericsson's foundational studies on expert performance already settled decades ago. Ericsson's core finding wasn't that practice builds skill. It was that undirected repetition, on its own, mostly doesn't. What separates expert performers is deliberate practice specifically: a narrow, well-defined task, repeated with real effort, paired with immediate, specific feedback on what went wrong. Remove any one of those three ingredients and the hours stop compounding into skill. A monthly, vague, unscored role play session is missing all three at once.

Why the standard version falls flat

A typical role play session picks a vague setup ("okay, pretend I'm a prospect who's not interested") and gives it five minutes once a month in a team meeting. That fails on every axis Ericsson's research says actually matters: the task isn't narrow (a "not interested" prospect can go a hundred directions), there's no real effort under real stakes (everyone knows it's theater), and the feedback, if it comes at all, arrives as a vague "good energy" instead of a specific correction tied to the exact line that went wrong.

Skill comes from targeted reps with fast feedback, not from a single well-intentioned exercise. A scenario that only runs once a quarter, with no scoring attached, is a performance, not deliberate practice.

What makes a scenario worth running

1. It's specific, not generic: the "narrow task" Ericsson's research requires. "Handle an objection" isn't a scenario. "The prospect says they already have a vendor and sound annoyed you called" is. The more precisely you name the situation, the more useful the rep's response actually is, because they're rehearsing the exact words for the exact moment, not a vague category.
2. It has a clear trigger line. Every good scenario starts with the exact sentence the rep will actually hear: "Send me an email," "We're all set," "Call me back next quarter." Practicing the response to a specific trigger transfers directly to the real call. Practicing a general topic doesn't.
3. It gets scored the same way every time: the immediate feedback the research says can't be skipped. Did the rep acknowledge the objection instead of arguing with it? Did they ask a follow-up question instead of pitching immediately? A short, consistent rubric turns "that felt fine" into something a manager can actually coach against.
4. It repeats. One run of a scenario is a demo. Ten runs of the same scenario, spaced across a week, is where the response stops sounding rehearsed and starts sounding like the rep's own voice, which is just deliberate practice's third ingredient, real repetitions, showing up in a sales context.

Four scenarios worth building into a rotation

• The instant brush-off. Prospect says "not interested" before you've finished your first sentence. The rep's job is to earn ten more seconds without sounding pushy.
• The price objection with no context yet. Prospect asks "how much does this cost" on a cold call before any value has been established. The rep has to answer honestly without either dodging the question or letting it derail the call.
• The competitor mention. Prospect says they already use a specific competitor. The rep needs a response that doesn't trash the competitor and doesn't concede the deal either.
• The soft stall. Prospect says "sounds interesting, send me some info" as a polite way to end the call. The rep's job is to convert that into a real next step instead of letting it become a dead email thread.

The part teams usually skip

Building four good scenarios takes an afternoon. Running them consistently, every rep, multiple times a week, with the same scoring rubric, is the part that actually requires a system instead of a monthly meeting. That's the gap daily flashcard drills and short AI practice calls are built to close: the same scenario, run enough times that the response stops being a script and starts being muscle memory, which is exactly what DialDynamics' daily drills are built around.

If your team already has a list of real objections you hear every week, that list is your scenario bank. The only thing missing is a way to run it often enough to matter.