Why most training scenarios feel fake.
Most learners can detect a training scenario in two sentences. The names, the language, the tidy structure of the dilemma all signal "this is a training exercise" before the learner has even finished reading. Once that signal arrives, the learner stops engaging with the story and starts looking for what the course wants them to pick. The scenario has failed before it began.
Stock names and corporate language.
"Sarah is a manager at ABC Corp who has been struggling with…" Every scenario that opens this way has lost the reader. Real situations involve real names that sound like real names, in real settings with real specifics. "Sarah, the new team lead at the Brisbane warehouse, is on her third week of nights…" sets a scene. "Sarah, a manager at ABC Corp" sets up a worksheet.
Dilemmas with one obvious right answer.
If the three options are "do the right thing", "do nothing", and "do something silly", the scenario is a multiple choice question with characters. Real workplace dilemmas have trade-offs. The cautious choice has costs. The aggressive choice has costs. Even the "do nothing" option has costs. Good scenarios put the learner in genuine uncertainty — the kind they'll feel at work, where every option costs something.
Resolution wrapped up in a bow.
"And Sarah learned to communicate more clearly with her team." Real outcomes are messier — the conversation went better than expected but still hasn't resolved the underlying issue, or it went badly but at least the air is clear. Tidy resolutions teach learners that the situation always wraps up — which prepares them poorly for situations that don't.
Part two
How to write scenarios that feel real.
Realism in scenarios doesn't come from elaborate detail — it comes from a few specific writing choices that, taken together, make the situation feel grounded.
Open with specific context.
Concrete details ground the reader. Not "a customer calls" but "a customer calls at 4:50pm on a Friday." Not "a teammate is upset" but "you find your teammate at their desk after lunch, jacket still on, scrolling through emails without opening any." Specificity tells the reader this is a real situation, not a generic scenario. It also makes the situation easier to imagine, which is when scenarios start to work.
Write dialogue you'd actually hear.
"I'm experiencing significant frustration with this situation" is training language. "Honestly, I just don't know what to do." is real language. Read your scenario aloud — if it sounds like a manual, rewrite. Listen to how people actually talk at work: incomplete sentences, hesitations, the small word choices that signal frustration or politeness. Capture those.
Make all options plausible.
Each choice in a scenario should be defensible — something a thoughtful person might actually pick. The "wrong" answer shouldn't be obviously wrong; it should be plausibly wrong, in the way real mistakes are plausible. If the learner can pick the right answer by eliminating the silly options, you've written a quiz with extras, not a scenario.
Show consequences, don't grade them.
See the branching scenarios guide for the core principle: don't say "correct" or "incorrect" after a choice — show what happens. "The customer's voice softens. They take a breath, then start telling you the rest of the story." That's a consequence. "Correct!" is a grade. The consequence teaches; the grade closes the moment.
Leave some things unresolved.
Real situations don't always wrap. Sometimes the conversation ends with the issue half-handled. Sometimes the customer agrees but you sense they're still unhappy. Scenarios that always resolve cleanly teach learners that conversations have endings — they don't always. End some scenarios with the situation still in progress, with a comment that the rest will play out tomorrow, next week, or never.
Use names that aren't placeholders.
Avoid Sarah, John, Mike, Anna as default names. They've been overused in corporate training to the point of cliché. Pick names that sound like specific people — Marcus, Priya, Diya, Tane, Eliza, Amara. Names that have personality, that the reader doesn't immediately tag as "training character". Also, vary them — a course where every scenario protagonist is white and middle-aged is doing demographics work the writer probably didn't intend.
Part three
Scenarios in context.
How scenarios are used in a course matters as much as how they're written. A great scenario in the wrong place misses; an average one in the right place lands.
A standalone scenario card.
Short, single-choice, used to illustrate a point or open a section. Three to five sentences of context, three options, one paragraph of consequence each. The format is light enough to use multiple times in a course without feeling repetitive. Rise's scenario block fits this pattern well.
A branching scenario.
Three or more decisions, each with consequences that build on the previous choice. The format is heavier — see the branching scenarios guide for full design considerations. Worth it for content where judgement and accumulated decisions matter: customer service, leadership, difficult conversations.
A scenario as an opener.
Used to set up a topic. "Imagine you're the new team lead at the Brisbane warehouse. It's Friday afternoon. One of your team comes to you and says…" — and then the course continues to teach the relevant skill. The scenario is the hook; the content that follows is the teach. This pattern works well when the scenario asks a question the course will answer.
A scenario as a closer.
Used at the end of a section to apply what was taught. The learner has just covered "how to give difficult feedback"; now they walk through a scenario where they have to apply it. Closing scenarios convert passive learning into rehearsal — by far the most powerful pedagogical move you can make at the end of a lesson.
A scenario is fiction in the service of learning. Write it like fiction — with specific details, real dialogue, plausible choices, and unresolved edges. Use it where rehearsal matters more than knowledge transfer. The hardest part isn't the writing itself; it's the willingness to leave the scenario messy, with choices that all cost something. That's when scenarios start to teach.