Resource Lab Pattern
Decision Drive
A Spy Hunter-inspired judgment-practice pattern that turns a high-pressure workflow into a lane-driving interaction where learners collect useful support, avoid bad shortcuts, manage risk, and stay on mission.
What it is
A lane-driving game where speed only helps if judgment comes with it.
Decision Drive uses the familiar arcade logic of staying in lane, avoiding hazards, collecting support, and reaching the destination. The learning move underneath is simple: learners practice choosing useful inputs while resisting risky shortcuts and noisy distractions.
It scratches the “make it feel like a game” itch without turning the learning goal into decoration. The vehicle is fun. The road is the workflow. The hazards are bad decisions. The support pickups are the behaviors you actually want people to use.
Basically, it is eye candy with a steering wheel and a conscience.
Pressure-based decisions
Situations where learners must keep moving while watching for signals, hazards, support cues, and tempting shortcuts.
Workflow navigation
Escalation, support, safety, troubleshooting, leadership, customer scenarios, onboarding, and operational judgment practice.
Make momentum useful
Use motion and game energy to reinforce prioritization, risk awareness, and choosing better support paths under pressure.
Live Preview
Stay on mission.
Move between lanes, collect support pickups, avoid hazards, and reach the finish with as much mission clarity as possible. This sample is generic so you can adapt it for real workflows, decisions, or scenarios.
Decision Drive
Navigate the workflow road.
Why this works
The road makes the workflow visible.
A lane-driving metaphor works because it is immediately understandable. The learner has a goal, limited space, incoming obstacles, and useful supports. That makes pressure visible without requiring a giant branching simulation.
The trick is making sure each game element maps to a learning behavior. Support pickups reinforce useful actions. Hazards represent bad shortcuts. Lane changes represent prioritization. The finish line represents clarity, not just completion.
The game is the wrapper. The debrief is where the learning earns its keep.
Design Notes
Use speed to create pressure, not to hide shallow learning.
A racing game pasted onto quiz content
The learner dodges random objects, earns points, and leaves with no clearer understanding of the work behavior.
A road system tied to workflow judgment
The learner collects support, avoids risky shortcuts, manages urgency, and receives coaching on what helped or hurt the mission.
Build Structure
The pattern has five parts.
Workflow road
Define the road as the path through a real process, decision, escalation, or support workflow.
Support pickups
Create helpful items that represent SOPs, verification steps, job aids, coaching cues, or useful context.
Decision hazards
Use hazards for assumptions, shortcuts, pressure, missed context, unverified claims, or risky actions.
Behavior badges
Reward meaningful behaviors like prioritization, support use, risk recovery, and mission focus.
Coaching debrief
Explain what the learner collected, what they avoided, where they got distracted, and how that maps to the real workflow.
Starter Code
Copy, adapt, and make it your own.
Use this starter structure for Rise blocks, Storyline web objects, S3-hosted learning tools, internal knowledge pages, or portfolio prototypes.
<div class="decision-drive">
<div class="drive-stats">
<div>Score: <span id="score">0</span></div>
<div>Support: <span id="support">0</span></div>
<div>Hazards: <span id="hazards">0</span></div>
</div>
<div class="drive-stage">
<div class="drive-car"></div>
<!-- Moving support and hazard objects are generated with JavaScript -->
</div>
<div class="drive-badges">
<div>Support Collector</div>
<div>Lane Strategist</div>
<div>Mission Focus</div>
</div>
</div>
<script>
const supports = ["SOP", "Verified Cue", "Escalation Path"];
const hazards = ["Shortcut", "Assumption", "Urgency Trap"];
// Core logic:
// 1. Define lanes.
// 2. Spawn support and hazard objects.
// 3. Move learner left/right.
// 4. Detect collisions.
// 5. Add points for supports.
// 6. Subtract points for hazards.
// 7. Unlock badges based on behavior.
// 8. End with a coaching debrief.
</script>Adaptation Notes
Use the same pattern in Rise, Storyline, or a hosted page.
Use as an embedded web interaction
Host the HTML page on S3 or another approved location, then link or embed it from Rise as a short workflow navigation activity.
Build with motion paths and variables
Use variables to track score, lane changes, support collected, hazards hit, badges, and completion. Show layers based on learner performance.
Show purposeful game design
Present it as evidence that you can build fun, visually engaging learning interactions without letting the game swallow the learning goal.
Showcase Angle
Why this works as a portfolio or community submission.
Decision Drive has nostalgia, motion, badges, and arcade energy, but the instructional purpose is still visible. The learner is not just dodging objects. They are practicing how to keep moving through a workflow while choosing supports and avoiding risky shortcuts.
That makes it useful for portfolio examples, E-Learning Heroes submissions, design challenges, and stakeholder conversations about how to make learning engaging without turning the whole thing into an unrelated mini-game.
The goal is not a cooler road.
The goal is a clearer path through the work. Decision Drive gives learners the energy of an arcade interaction while keeping the design anchored to judgment, support use, and better decisions under pressure.