De-escalation storyboard
A desk-scenario storyboard using cumulative variables rather than right-or-wrong scoring, with three endings and in-tool decision data kept separate from the floor measure.
Prototype · no floor data
Design review case study
What a design review actually produces.
Most reviews stay private, so nobody knows what they buy. This one is published in full — the work that came in, the five observations that went back, and what the designer rebuilt because of them.
What came in
Two pieces of work and two honest questions.
Justin was building practice for a public resource front desk. The performance goal was fewer escalations with real patrons. He was upfront that one piece had shipped and one had not — which made the review far more useful than a polished pitch would have.
De-escalation Coach
An open-response tool where learners write what they would actually say, then receive structured feedback against a five-part framework instead of a generic AI reaction.
Stronger learning experienceWhat he asked for
- How would you approach the scoring model here?
- Do the three endings give a learner feedback they can act on?
What went back
Five observations, in priority order.
A review is not a verdict. Each observation names what is happening, why it matters for performance, and the specific move that would strengthen the work.
01
The storyboard names a competency but never a measurable performance objective.
- What I saw
- A clear competency target, but no statement of what the learner must do, under what conditions, and what successful de-escalation looks like.
- Why it matters
- Without that objective, the decisions, the feedback, and the measurement strategy have nothing to answer to. Each one gets designed on instinct instead.
- The move
- Write the objective first, then let it drive the decision points, the feedback, and the floor measure.
02
Remove the knowledge check.
- What I saw
- A knowledge check deliberately isolated from the simulation outcome — a defensible instinct, cleanly executed.
- Why it matters
- It still interrupts the tension of the interaction, and it produces no performance evidence. The scenario already asks the learner to apply the principle.
- The move
- Cut it. Let the scenario carry the evidence.
03
The cumulative design contradicts itself.
- What I saw
- The storyboard states that no individual response is simply right or wrong, yet every option is internally classified Strong, Middling, or Poor — and the Escalated variable can make recovery impossible after one poor decision.
- Why it matters
- Real conversations are usually recoverable. A single unrecoverable misstep teaches the opposite of the cumulative principle the design claims.
- The move
- Let a learner recognize a misstep and regain trust. The system becomes more authentic and finally matches its own stated design principle.
04
This is not a branching simulation.
- What I saw
- Every response returns to the same next decision. That is a state-based scenario with conditional outcomes, not branching.
- Why it matters
- The architecture is valid either way. But naming it accurately makes the portfolio explanation stronger, and misnaming it invites the one question you do not want in an interview.
- The move
- Describe it as a state-based scenario and explain why that architecture fit the performance goal.
05
The storyboard and the coach read as two solutions instead of one evolution.
- What I saw
- One piece uses predetermined responses in a single continuing interaction. The other uses open responses, rubric-based feedback, and three separate scenarios. Nothing connects them.
- Why it matters
- If the coach is an evolution of the storyboard, that is the strongest thing in the portfolio — it shows a designer who recognized the limits of multiple-choice practice and moved toward authentic performance evidence.
- The move
- Make the open-response coach the centerpiece and tell the progression as a single decision, not two samples.
What changed
The review is only worth what gets rebuilt.
Within the hour, Justin identified the observation that landed hardest and committed to three specific changes.
Reframed the narrative
The write-up is being rebuilt around the storyboard-to-coach progression as one evolution rather than two separate pieces.
Moved the centerpiece
The open-response coach becomes the lead artifact, because written responses produce better evidence than selecting from three options.
Named the objective
A measurable performance objective now drives the decisions, the feedback, and the escalation trend it would be held to.
“It named what I missed, pointed to the stronger move, and told me what to check next. It coached the next move.”
Justin Weathers
Instructional Designer · Training & L&D Coordinator
Your turn
Bring one artifact.
Focused entry service · $79 founding price
Professional Design Review
The review above is exactly this service. Written feedback organized around strengths, risks, and opportunities, the five highest-value improvements prioritized, and a 20-minute debrief.
Explore the Professional Design Review → Free tool · no account neededFeedback Rewrite Studio
Want to see the same thinking applied to your own feedback? Paste in something you are not proud of and rebuild it so it coaches the next move instead of grading the last one.
Open the free tool →