The fastest way to learn scenario design is to read good small ones. Below are six mini-examples across fields — each with a premise, a decision point, branches, and the feedback tags we would use in ScenarioSplice (correct, incorrect, partial, info). Steal the structures and swap in your content.
All six follow the same skeleton — situation, one decision with honest options, consequences before verdicts — which is the decision-tree template every new ScenarioSplice scenario starts from.
1. Nursing: the quiet deterioration
Premise: A 68-year-old, post-op day one after a hip replacement. Blood pressure has drifted from 128/76 to 102/60 and she is newly confused. You have four other patients. Decision: what do you do first?
Focused assessment and full vitals now — you catch the trend and escalate with data; the response team arrives to a prepared nurse. Tag: correct.
Give the PRN analgesic charted for tonight — thirty minutes later the confusion is worse and the picture is muddier. Tag: incorrect.
Call the surgeon immediately — the surgeon asks for the numbers you do not have yet. Not unsafe, just weaker. Tag: partial.
2. Customer service: day 41 of a 30-day policy
Premise: A four-year customer wants a refund eleven days past the window and is already frustrated. Decision: your opening reply.
Empathize, then offer store credit within your authority — the customer grumbles but accepts; the thread ends warm. Tag: correct.
Quote the policy verbatim — technically right; the reply escalates and resurfaces as a public review. Tag: incorrect.
Escalate to a supervisor immediately — this ticket resolves, but handle time doubles and the rep learned nothing. Tag: partial.
3. Compliance: the urgent vendor email
Premise: An email from a logistics partner’s domain — one letter off — requests a customer address export "before end of day." Decision: what do you do with it?
Verify through a known contact channel — the real vendor has no idea what you mean; you report the spoof. Tag: correct.
Send the file — the branch ends with the incident report three days later, not a buzzer. Tag: incorrect.
Forward it to your manager and wait — better than sending, but verification was something you could do yourself in two minutes. Tag: partial.
An info page here shows what a look-alike domain actually looks like — facts, not judgment.
4. History class: Philadelphia, 1793
Premise: Yellow fever is spreading and students advise the mayor. Decision: quarantine the docks, urge evacuation, or trust the physicians recommending bleeding cures?
Each branch follows the policy through September, then an info page carries what actually happened and what people believed at the time.
Notice the tags: mostly info, because the lesson is historical thinking, not a right answer. The four tags are a language, not a law.
5. Sales: "your competitor is 30 percent cheaper"
Premise: Late-stage deal; procurement drops the price comparison. Decision: your next move.
Ask what is driving the comparison — the real concern surfaces (a support horror story), and price stops being the issue. Tag: correct.
Match the discount on the spot — the deal closes; an epilogue page shows renewal season, where the discount is the new anchor. Tag: partial.
Defend the feature list — procurement was not asking about features. The call stalls. Tag: incorrect.
6. Onboarding: stuck for 45 minutes
Premise: A new support engineer is blocked on a config issue and worried that asking looks weak. Decision: what do they do?
Post in the public help channel — an answer in ten minutes, now searchable for the next new hire. Tag: correct.
Keep digging silently — end of day, the ticket breaches SLA; the retro is kind but clear. Tag: incorrect.
DM the tech lead — you get the answer; the next new hire will not. Tag: partial.
What these six have in common
Every example is one decision moment with options taken from real behavior — the tempting shortcut, not a strawman. Consequences appear before verdicts, partial is used honestly for defensible-but-weaker moves, and info pages carry facts without judging. Any of them builds in ScenarioSplice in under an hour from the decision-tree template — the full process is in how to create a branching scenario.
Frequently asked questions
Can I copy these examples directly?
Yes — adapt them freely. They are teaching skeletons, and the details (policy days, drug names, chat norms) should become yours anyway.
How many pages do these come to?
Eight to fifteen each: a situation page, one decision with three branches played one or two beats deep, and a debrief. Merging branches keeps the count down.
Why only one decision point per example?
It is the unit of design. Real scenarios often chain two or three decision moments — but each one should still pass the test these examples pass: honest options, felt consequences.
Where do I start building?
Open a new scenario — it starts as a decision-tree template — and follow the step-by-step guide. The first draft takes thirty to sixty minutes.