Visible consequences
Each decision changes system meters, making the impact of design choices visible immediately.
Resource Lab Flagship Pattern
Learning Systems Quest
A decision-based mindset adventure about designing learning that survives contact with real work. Start with a common stakeholder request, make design choices, and see whether your solution becomes a one-time event or a useful learning system.
A stakeholder walks in and says the six words every learning designer knows too well:
“Can we make a quick course?”
Maybe the answer is yes. Maybe the real problem has nothing to do with a course. Maybe the workflow is broken, the support is missing, the manager behavior is inconsistent, or the measurement plan is basically vibes in a spreadsheet.
This tiny adventure game is about slowing down that first request long enough to design the system around the learning, not just the deliverable.
Interactive Quest
Build a learning system, not just a launch moment.
Make one choice at each stage. Your decisions will affect clarity, learner trust, operational fit, and sustainability.
Stage 1 of 5
Clarity
50
Learner Trust
50
Operational Fit
50
Sustainability
50
Diagnose
The “quick course” request
A stakeholder says people keep making the same mistake in the workflow. They want a short course by Friday. What do you do first?
Coaching Feedback
Choose a path.
Your feedback will appear here after each decision.
Quest Result
Your learning system result
Your final result will appear here.
0
System score
Design lens
Advice will appear here.
What This Teaches
The course is often the visible artifact, not the whole solution.
Learning experiences rarely succeed because a single asset launches. They succeed when the surrounding system supports the behavior the learning is trying to create.
That system may include clearer expectations, better manager cues, performance support, workflow prompts, follow-up practice, accessible references, coaching moments, and measurement that actually tells the team whether people can perform.
The point of this game is not to punish course design. Courses can be useful. The point is to help learning designers ask better questions before a course becomes the default answer.
Design Notes
Why this works as a learning interaction.
This pattern uses lightweight game mechanics to reinforce systems thinking without burying the learner in a giant branching scenario.
Coaching feedback
Feedback explains why a choice helped or hurt the system instead of simply marking the choice right or wrong.
Simple progression
The five-stage structure keeps the experience focused: diagnose, design, support, reinforce, and measure.
Reusable model
The same pattern can support onboarding strategy, compliance design, leadership scenarios, coaching practice, or workflow training.
Build Notes
How to adapt this pattern.
Swap the five stages for any decision process you want learners to practice. For example, a safety scenario could use Notice, Verify, Act, Escalate, and Debrief. A customer support scenario could use Listen, Diagnose, Respond, Resolve, and Follow Up.
The key is to choose meters that reflect the real tradeoffs learners need to manage. Instead of generic points, use meaningful dimensions like trust, risk, speed, confidence, friction, accuracy, compliance, or readiness.
This is where game mechanics become useful. Not because the learning needs points for the sake of points. Because visible consequences help learners understand the system they are operating inside.
Starter Code
The pattern underneath the polish.
The interaction runs on a simple structure: stages, choices, meter impacts, and coaching feedback. The model is intentionally easy to adapt.
const stages = [
{
label: "Diagnose",
title: "The quick course request",
choices: [
{
title: "Ask where the behavior breaks down.",
impact: {
clarity: 14,
trust: 8,
fit: 12,
sustainability: 8
},
feedbackTitle: "Strong systems move.",
feedbackText: "You slowed the request down just enough to understand the real problem."
}
]
}
];Better learning design starts before the deliverable.
The real design move is not asking, “What course should we build?” It is asking, “What system needs to exist so people can perform with more clarity, confidence, and consistency?”