Instructional Design

Instructional Design Atlas

A field guide to course architectures and gamification mechanics — explore how the best learning experiences are actually built.

Introduction

1.1 What are architecture, structure, and scenario

To design a strong course, you need to move top-down: first choose the architecture — the underlying design of the learning experience, then the structure — the organization of the material, and only then write the scenario — the content. Starting with content is the main mistake.

Architecture

Architecture defines the type of experience. It's the highest level of design, where there are no screens or character lines yet. It answers the question: "What path should the learner take to reach the outcome?"

For example, a course about phishing emails can be built as a series of explanations with a quiz, as a simulation of a workday, as a cyberattack investigation, or as an interactive comic — these are all different architectures.

Structure

Structure organizes the material — but, unlike architecture, it doesn't describe how it feels.

Structure only appears after the architecture has been chosen, and answers a different question: "What parts does the course consist of, and in what order do they go?" Unlike architecture, it says nothing about the emotions or experience of the course — only about the sequence of its parts.

Example of a structure: introduction → situation → explanation → practice → next situation → final challenge → wrap-up.

Or another version: problem → theory → example → exercise → repetition.

You can compare it to a book: architecture is the genre of the book (detective, biography, popular science), while structure is its table of contents — what comes after what.

Scenario

Scenario fills the structure with detail and brings the course to life.

Once the architecture is chosen and the structure defined, work begins on the scenario — the lowest and most concrete level. It answers the questions: What do the characters say? What situations occur? What response options and feedback does the learner get? What emotions arise in a specific scene?

It's precisely the details of the scenario — a character's line, an unexpected message on the phone, a colleague's comment — that make a course memorable.

At the same time, instructional designers most often jump straight to this level, skipping architecture: they ask "what will the character say?", "what story should we invent?", "what jokes should we add?" — instead of first deciding through what kind of experience a person will best master the skill.

Introduction

1.2 Levels of architectures

There are several levels of delivering an experience:

You can simply state facts, rules, and company policy.

You can add care about making sure the person understands — add examples, practice, feedback, and exercises.

Or you can think about what the learner needs to live through and feel in order to change their behavior — this is where plot, characters, surprises, mistakes, emotions, and the consequences of choice come in.

It's precisely this third level that is the territory of Learning Experience Design (LXD), a field that grew out of classic Instructional Design and focuses more strongly on the learner's experience. Most courses stop at the second level, and only the best aim for the third.

Introduction

1.3 The ideal architecture

An architecture isn't right or wrong in itself — it either fits or doesn't fit a specific behavior problem. So before choosing an architecture, and sometimes before even deciding whether a course is needed at all, it's important to understand exactly what's preventing a person from acting the way they need to.

If there were one single correct scheme, all courses would look the same — introduction, theory, practice, test. But it's enough to open a few courses from different companies to see how different they actually are.

The same surface-level problem can have different causes — and the architecture needs to be chosen for the cause, not the symptom.

For example, a company says: "Employees aren't using the new CRM." The cause could be that they genuinely don't know how to use it, or that the system is inconvenient and they prefer the old way, or that managers themselves aren't requiring its use, or that employees simply don't understand why they should switch to the new system.

On the surface, the problem looks the same in all four cases — "the CRM isn't being used" — but the learning architecture (if learning is even needed at all) will be completely different.

If the problem isn't about knowledge, a course won't solve it.

Indeed, Instructional Design has a concept called a performance problem — a workplace-behavior problem. Not every such problem is solved by training.

At a warehouse, employees regularly make mistakes fulfilling orders, and the company orders a course. Analysis reveals that box labeling is nearly unreadable, and similar products sit right next to each other. No matter how much you train people to be more careful, mistakes will continue, because the issue isn't knowledge — it's the layout of the workplace.

That's why there's a rule: if a problem can't be solved by training, don't build a course. This idea alone saves companies an enormous amount of time and money.

Introduction

1.4 Types of architectures

If training really is needed, the architecture is chosen to match the type of experience that a specific skill requires. We need to understand:

What behavior needs to change?
Why isn't it happening now?
What experience will change it the fastest?

This is exactly where the choice of a specific architecture happens. For example, a difficult conversation calls for a dialogue simulation. New software calls for interactive practice. A sense of company culture calls for a story with characters and situations. A diagnostic skill calls for an investigation or a case study.

Only after this does it make sense to start opening up materials. This looks like a slower path, but it's exactly what makes it possible to create courses that change behavior rather than just deliver information — which is why the skills of designing learning experiences or designing learning journeys are so valuable.

From this grows the central idea: an instructional designer doesn't design a course — they design a change in a person's behavior. The course is just one of the tools through which that change happens.

So, there is no ready-made list of architectures, and you can't identify an architecture from a course's outward appearance either — it can only be discovered through how the learning experience is built on the inside.

Architecture is a way of organizing experience, not a fixed type.

Five outwardly dissimilar courses — a data-breach investigation, a first day at work, the role of a manager, helping a customer, a stream of messages in a work chat — can actually come down to just a couple of architectures: some of them are variations of story-based learning, some are forms of scenario-based learning, and one is just a regular linear course with an unusual interface.

You can't identify an architecture by its styling — styling is the shell, not the logic of the course. One of the most common mistakes is judging architecture by style: "the course feels like a game," "we made it like a TV series," "we have a chat instead of a menu." This describes the delivery format, not how the learning is actually structured.

To identify the architecture of a finished course, it's more useful to answer five more specific questions in sequence:

Where does the knowledge come from? Is it explained first and then applied? Or does the person encounter the problem first and only then get an explanation? Or do they discover the patterns entirely on their own?
How does the person practice? Do they answer quizzes? Negotiate? Investigate an incident? Run a company or work inside a software simulation?
How is feedback structured? Immediate or delayed? Through consequences, through characters, through numbers, or through discussion? For example, if a character loses their colleagues' trust because of a wrong decision, that's feedback too, even though no one wrote the word "incorrect."
What drives the person forward? Interest in continuing the story? The desire to pass a challenge? The thrill of solving a puzzle or collecting achievements?
How does the learning conclude? With a test, a final simulation, or a real work task? A conversation with a manager, or a personal action plan? The ending strongly affects what stays with the person after the course.

This five-question model is an original attempt to bring together ideas from Instructional Design and Learning Experience Design into a single framework, including approaches from Julie Dirksen and Cathy Moore.

The next step is to break down the actual families of architectures that have taken shape in the industry: why they emerged, what problems they solve, where their strengths and weaknesses lie — where they work well, and where they don't.

Introduction

1.5 The main e-learning architectures

1. Linear course — answers the question: How do you deliver knowledge in the right sequence?

TYPE 1 Explain → Practice TYPE 2 Scaffolding TYPE 3 Productive Failure TYPE 4 I do – We do – You do

2. Scenario-Based Learning — answers the question: How do you teach people to make decisions in a real context?

This type emerged as a response to the fact that people who had studied the material in a linear course didn't recognize the situation in which that answer needed to be applied.

A scenario is a model of a professional situation in which a person has to make a decision. Specifically a professional situation — not just a story.

Introduction

Deep dive: What makes Scenario-Based Learning work

Let's imagine two courses.

In the first, the learner watches a story about a difficult client. They observe the character object, get emotional, make threats. The story is engaging, the character feels real. But the learner barely makes any decisions at all. They remain a spectator.

In the second course, there's no story at all. A call from an unhappy customer appears on screen. You need to decide how to respond. Then the manager calls. Then a conflict arises within the team. Each situation requires a decision.

Which of these two courses is Scenario-Based Learning? Most people would intuitively pick the first, because it has a plot.

In reality, the second one is closer to Scenario-Based Learning — because its foundation is not the story, but decision-making in a professional context.

So Story-Based Learning and Scenario-Based Learning are not synonyms. Very often they're combined in the same course, but they solve different problems. A story creates emotional context, while a scenario creates the need to make a decision. It's worth noting that:

Branching does not mean Scenario-Based Learning. The architecture is defined not by the number of branches, but by why the learner is making decisions. You can build twenty branches that have no instructional value whatsoever.
Dialogue does not mean Scenario-Based Learning. It only becomes part of Scenario-Based Learning when the learner makes decisions that affect how the professional situation develops.
Game elements do not mean Scenario-Based Learning. Points, badges, scores, timers have nothing to do with the architecture at all — they're motivational elements, and they can appear in any type of course.

How do you know you're looking at genuine Scenario-Based Learning?

Strip the course of: characters; beautiful graphics; animation; voiceover; plot. Keep only the sequence of situations and decisions.

If the course still teaches the person to make professional decisions, then its architecture really is scenario-based. If, once you remove the story, all that's left is text and quizzes, then the scenario was decorative rather than the actual foundation of the learning.

If decision-making is the core of Scenario-Based Learning, what actually makes a decision genuinely instructional?

Two situations.

On screen it says: Which password is considered strong? — 123456 / Password / P@ssw0rd!2026 / qwerty.

The learner picks the third option. Correct. Did they learn anything? Probably not. They just recalled a rule.

Now imagine a different situation. You've just walked out of a meeting room. A client calls. They're irritated. They say the project has fallen through. In five minutes, a meeting with the director begins. At this moment, you need to decide: what do you do?

Now a completely different kind of thinking happens. The person isn't searching for the correct answer — they're assessing the situation, setting priorities, recalling past experience, picturing the consequences, and only then making a decision. This is exactly the goal of Scenario-Based Learning.

People don't memorize ready-made solutions. They learn to recognize situations.

For example: A novice sees an email; an expert sees an attempted social-engineering attack. A novice hears a customer's objection; an expert understands the customer isn't actually arguing — they're afraid of risk. A novice sees a colleague's silence; a manager understands that the colleague disagrees but doesn't want to argue publicly.

In other words, an expert makes a good decision because they perceive the situation differently. That's exactly why good scenarios rarely start with a choice — they first help the person "read" the context.

Good and bad scenarios

Compare two situations: What color is the fire-exit sign? — this is a knowledge-recall task. And: During an evacuation, an employee asks to go back for their laptop. What do you do? Here, uncertainty appears — the person has to weigh safety rules, the pressure of the situation, and another person's emotions.

In real work, most decisions look like this. That's why good scenarios are rarely built around questions with one obvious correct answer.

Consequences matter more than the correct answer

In the first course, after a mistake, a message appears: Incorrect. Try again. In the second, the learner sees that after their answer, the customer ends the conversation, or a colleague loses trust, or the team starts working less effectively.

In which case will the learning be stronger? Obviously, the second — because the person sees the consequences of their own decision, rather than just receiving a grade.

Scenario-Based Learning doesn't teach through grading. It teaches through cause and effect.

Does this mean there's no correct answer at all?

In many real work situations, there isn't just one correct option. There are several acceptable ones, and several bad ones.

For example: you're a manager, an employee was late. You could talk to them right away, talk to them later, or first find out the reasons. All three options can be reasonable — it all depends on context.

That's exactly why strong scenario-based courses rarely split answers into just "right" and "wrong." Instead, they tend to show trade-offs:

This decision quickly relieves tension, but it may create an expectation that this kind of behavior is acceptable.

This approach reinforces discipline, but risks damaging the relationship with the employee.

The person learns to see the consequences of different decisions.

Every decision in a strong scenario-based course should meet four criteria

1. Authenticity — Could this situation realistically happen at work? If not, the scenario loses its value.

2. Uncertainty — Does the situation require thought? Or is the answer obvious within a second?

3. Consequences — Does the choice change how the situation develops going forward? Even just a little.

4. Reflection — Does the learner understand why one decision turned out better than another?

A mistake almost everyone new to this makes: starting with the answer options — for example, "What will you do? A / B / C / D" — and then trying to invent a situation that leads to that question. In reality, the process should go the other way. First, a situation appears that naturally forces the person to make a decision. Only then do the possible actions appear.

What makes a good professional situation?

Learning begins the moment the normal flow of events is disrupted — an unexpected email, a customer complaint, a conflict, a mistake, a lack of time, contradictory requirements, ambiguous information. All of this creates tension. And tension is what triggers thinking.

A situation needs to have a cost

If a choice doesn't affect anything, a person very quickly stops taking it seriously. Imagine a question: "What color should the employee uniform be?" — even if you answer incorrectly, nothing happens.

Now a different situation: "If you send this email to all customers right now, the company could breach the terms of the contract." Here, the cost of a mistake appears. The consequences don't have to be catastrophic — sometimes the cost can be quite small (losing a colleague's trust, five extra minutes of work, a misunderstanding within the team) — but it has to exist.

The strongest scenarios are built around a conflict of goals

Most beginners create a conflict between right and wrong. Experienced designers create a conflict between two right things.

For example: you're a manager, an employee made a mistake. What matters more — supporting them publicly, or immediately pointing out the mistake for the sake of work quality? Now a real dilemma appears.

Another example: you have little time. You can respond to the customer quickly, or check the information first. What do you choose — speed, or accuracy? Again, there's no obvious answer.

A good dilemma forces you to give something up

If a person can get everything at once, there's no dilemma. Imagine: you can keep a good relationship, fully follow the procedure, and lose nothing. That's not a dilemma.

Now a different situation: if you strictly follow the procedure, the customer gets irritated; if you accommodate the customer, you break an internal rule. Now you have to choose. It's exactly this act of giving up one value for the sake of another that makes a situation instructional.

Why do most corporate courses feel artificial?

Because they're afraid of ambiguity, and so they start simplifying the situation. The result is answers like: A. Break the law. B. Steal money. C. Follow the procedure. Obviously, the person picks C. They're not learning — they're just passing a test.

A good scenario isn't one where it's hard to guess the author's intended answer. It's one where you understand the appeal of the wrong decision.

Almost All Professional Scenarios Can Be Sorted by the Type of Dilemma

Dilemma	What the person learns	Example
Priorities	Prioritizing tasks	A customer sent five urgent requests at once. A manager asks for an urgent report. A meeting starts in 10 minutes. What do you do first?
Communication	Communicating with people	A customer demands a discount, even though company policy doesn't allow it. How do you respond in a way that preserves the relationship without breaking the rules?
Diagnosis	Analyzing a situation	Sales have dropped sharply. A customer is complaining about the product. The team thinks the issue is pricing, marketing thinks it's the ads. What information do you need to gather before deciding?
Ethical choice	Deciding based on values	A colleague asks you not to tell the manager about their mistake, because they're afraid of being fired. Preserve the colleague's trust, or follow company rules?
Risk management	Weighing consequences	Suspicious activity has been detected in the system. Full information isn't available yet. Stop the service immediately, or gather more data first?
Reacting to a mistake	Fixing your own mistakes	You accidentally sent an email to the wrong customer. The recipient has already opened it. What do you do next?

Outline for upcoming sections (not yet written out): Simulation-Based, Case-Based, Problem-Based, Guided Discovery, Performance Support architectures — plus Routes (Linear navigation, Branching, Hub-and-Spoke, Open navigation) and Feedback patterns.

Part 2 — Scenario-Based Courses / Type 2

Escalating Scenarios

The learner goes through several similar situations, one after another — each one harder than the last. Same skill, rising stakes.

Strengths

Doesn't scare the learner with the worst case right away — builds confidence step by step
Shows where a simple rule stops working and real judgment is needed
Feels motivating — the learner notices they're handling harder things as they go
Matches real life, where problems really do get harder over time

Limitations

Harder to build — needs 3+ genuinely different difficulty levels, not just guesses
Takes more time and material to create
If levels aren't different enough, it feels repetitive instead of escalating
Doesn't work if the skill has no natural easy/medium/hard ladder

When to use it

The skill needs judgment that gets harder to apply as things get more complicated
You want to prepare someone for a range of situations, not just one
In real life, people meet easy versions first, then harder ones later

Typical Examples

Customer complaints, small → serious IT incidents, minor → critical Team conflict escalation Sales objections Security threats

Full Worked Example

"The Complaint That Escalated" — Customer service / de-escalation under increasing pressure

Hook

A customer emails you, unhappy about a late delivery. How you handle this one small message will decide whether it stays small — or turns into something much bigger.

Simple Situation

"My order was supposed to arrive yesterday. It's still not here. Can you tell me what's going on?" Mildly annoyed, but polite.

Choice

A) Reply with a tracking link, an apology, and a clear new delivery estimate
B) Reply with a sincere apology and offer a 15% discount as goodwill
C) Reply immediately with a full refund, no questions asked

Consequence

A: "Thanks, that's helpful" — resolved, trust intact.
B: Accepted, but the actual question was never answered — they write back asking again.
C: Pleasantly surprised, but sets a "complain first, get a refund" pattern.

Debrief

A is correct not because it's generous, but because it matches exactly what was asked for — information, not compensation.

More Complex Situation

Two days later — order still hasn't arrived, and it was needed for a birthday. "This is the second time I've had to chase you."

Choice

A) Acknowledge the birthday, offer expedited replacement + small compensation
B) Escalate to a supervisor immediately
C) Offer a full refund plus a generous voucher

Consequence

A: Feels understood, gets something practical before the birthday.
B: Longer wait — the delay itself becomes a new complaint.
C: Compensated, but the actual problem (no gift in time) stays unsolved.

Debrief

A treats the emotional stake and the practical problem as equally important — the response has to match what's actually needed, not just look generous.

Next Steps

Continue to advanced training on reputational risk management, or explore the "Independent Scenarios" module.

Part 1 — Linear Courses / Type 1

Explain → Practice

Learn a concept, practice it, reinforce it. The most widely used architecture in e-learning.

What is it

Explain → Practice is the most widely used instructional architecture in e-learning. Learners first receive explicit instruction, then immediately apply the new knowledge through examples, practice activities, and a final application task. The architecture follows a simple principle: Learn a concept → Practice it → Reinforce it.

When to use it

Use this architecture when learners need to understand rules, concepts, or procedures before they can apply them. It works particularly well when there is a clear "correct" answer and learners need a solid knowledge foundation before practicing.

Strengths

Simple and intuitive learning flow, easy to design and scale
Works well for most corporate training topics
Suitable for beginners with little prior knowledge

Limitations

Can become passive if practice is limited
May encourage memorization rather than deep understanding
Less effective for developing complex judgment or problem-solving skills
Learners may struggle to transfer knowledge to unfamiliar situations

Common Design Mistakes

Presenting too much theory before the first practice activity
Including practice that does not align with the learning objectives
Using unrealistic examples
Providing only one large assessment at the end

When NOT to use it

Develop critical thinking
Solve ill-defined problems
Build complex interpersonal skills
Learn through exploration or discovery
Practice authentic decision-making in uncertain situations

Typical Examples

Compliance training Product knowledge Company policies Business processes Standard operating procedures (SOPs) Regulations Information security Quality standards

Real-world Examples

GDPR Compliance Code of Conduct Anti-Money Laundering (AML) Information Security Awareness Product Certification Customer Service Standards Workplace Safety Fundamentals

Combining with Other Architectures

Use Demonstration → Guided Practice → Independent Practice when learners must perform a software procedure after learning the underlying concepts
Transition into Scaffolding when the skill becomes increasingly complex
Finish with Productive Failure or scenario-based learning to strengthen transfer and real-world decision-making

Full Worked Example

"GDPR Essentials: Handling Customer Personal Data"

Hook

A customer asks you to send their contract to someone else's email address. What would you do?

Learning Objectives

Introduce the three learning objectives: Identify personal data. Recognize privacy risks. Handle customer information correctly.

Explanation 1

Explain what personal data is and how to distinguish it from non-personal information. (Objective 1)

Example

Compare examples of personal vs. non-personal data.

Mini-practice 1

Identify which pieces of information are personal data.

Explanation 2

Explain common privacy risks (sharing information with unauthorized people, sending data to the wrong recipient, discussing customer information in public, etc.). (Objective 2)

Practise 2

Present several workplace situations. Learners identify which ones involve a privacy risk and explain why.

Explanation 3

Explain the correct procedure for handling and sharing customer information according to company policy. (Objective 3)

Practise 3

Learners choose the correct action in typical workplace scenarios (customer requests, colleague requests, manager instructions).

Final Case

A realistic end-to-end scenario where learners must identify personal data, recognize risks, and choose the correct action.

Feedback

Explain each decision and reinforce all three principles.

Reflection

Ask learners: "Which of these situations are you most likely to encounter in your own work?"

Next Steps

Download the GDPR checklist and use it during your next customer interaction.

Summary

Recap the three key competencies and the most important rules.

Part 1 — Linear Courses / Type 2

Scaffolding

Start simple, increase complexity, perform independently. Build a complex skill through progressively harder tasks.

What is it

Scaffolding is an instructional architecture in which learners gradually build a complex skill through progressively more challenging tasks. Support is provided at the beginning and gradually removed as learners gain confidence and competence. The architecture follows a simple principle: Start simple → Increase complexity → Perform independently.

When to use it

Use this architecture when a skill is too complex to be mastered in a single step, and learners need gradual support. It works best when success depends on combining multiple sub-skills over time.

Strengths

Breaks complex skills into manageable steps
Reduces cognitive overload
Builds learner confidence gradually
Supports long-term skill development
Encourages successful transfer to real-world performance

Limitations

Requires more development time
Can feel slow for experienced learners
Difficult to design without a clear progression of difficulty

Common Design Mistakes

Increasing difficulty too quickly
Providing too much support for too long
Making every practice activity equally difficult
Skipping the integration stage before the final assessment task

When NOT to use it

Memorize factual information
Learn simple procedures
Complete short compliance or awareness training
Acquire knowledge that can be mastered in a single explanation and practice cycle

Typical Examples

Leadership Coaching Negotiation Programming Business writing Language learning Design Public speaking

Real-world Examples

Leadership Essentials Giving Constructive Feedback Coaching Conversations Negotiation Skills Difficult Customer Conversations Business Writing Presentation Skills

Full Worked Example

"Giving Constructive Feedback"

Hook

A manager gives harsh feedback to an employee, who becomes defensive. “How could this conversation have gone differently?”

Learning Objectives

Structure constructive feedback. Adapt feedback to different situations. Deliver feedback confidently in a real conversation.

Explanation

Introduce a simple feedback model (e.g., SBI: Situation – Behavior – Impact).

Simple example

Show a short dialogue where the manager uses the SBI model correctly.

Mini-practice 1

Learners identify the Situation, Behavior, and Impact in several feedback examples.

More complicated example

Show a more challenging conversation where the employee interrupts, disagrees, or becomes emotional.

More complicated practise

Learners choose the best response at several points in the conversation and receive coaching feedback.

Integrated Practice

Learners conduct an entire feedback conversation using the complete model in a branching dialogue with hints available.

Final task

Learners handle a new performance conversation independently, applying all skills without guidance.

Feedback

Provide personalized feedback on the learner’s final conversation. Highlight strengths and explain how each decision aligns with the SBI model.

Reflection

“What changed in the way you approached this conversation?” or “Which part of the SBI model feels most natural to you, and which one will require more practice?”

Next steps

Encourage learners to explore additional practice scenarios, download the SBI quick reference guide, or continue with the next module on handling difficult conversations.

Summary

Recap the four key principles: Describe the Situation. Focus on observable Behavior. Explain the Impact. Invite a two-way discussion. Reinforce that effective feedback is built through consistent practice.

Part 1 — Linear Courses / Type 3

Productive Failure

Attempt, learn from failure, apply again. Learners struggle with a real problem before receiving instruction.

What is it

Productive Failure is an instructional architecture in which learners first attempt to solve a realistic problem before receiving instruction. Initial failure creates cognitive readiness, making the subsequent explanation more meaningful and memorable. The architecture follows a simple principle: Attempt → Learn from failure → Apply again.

When to use it

Use this architecture when learners need to develop judgment rather than memorize rules. It is most effective when there is more than one possible solution and learners benefit from discussing misconceptions before receiving instruction.

Strengths

Promotes deep understanding
Encourages active thinking instead of passive learning
Improves knowledge transfer to new situations
Helps learners recognize and correct misconceptions
Develops confidence in solving unfamiliar problems

Limitations

Can be frustrating for beginners
Requires carefully designed feedback
Takes longer than traditional instruction
Less suitable when mistakes carry high real-world risks

Common Design Mistakes

Providing feedback without explaining the underlying principle
Making the initial problem too difficult
Turning failure into assessment instead of learning
Using unrealistic scenarios that do not reflect real decisions

When NOT to use it

Follow strict procedures
Learn safety-critical tasks
Perform technical procedures accurately from the start
Memorize factual information or regulations
Complete mandatory compliance training with little room for interpretation

Typical Examples

Leadership Critical thinking Decision making Sales conversations Coaching Negotiation Cybersecurity awareness Troubleshooting

Real-world Examples

Customer Complaint Resolution Leadership Dilemmas Root Cause Analysis Incident Response Simulations

Full Worked Example

"Recognizing Phishing Emails"

Problem

Learners receive an email that appears legitimate and must decide whether it is safe.

Attempt

They choose to open, report, or ignore the email without any prior instruction.

Feedback

Explain why their decision was correct or incorrect, highlighting the clues they may have missed.

Second Attempt

Learners analyze the same email again using the newly learned criteria.

New problem

Present a completely different phishing scenario with different warning signs.

Independent solution

Learners independently decide how to handle the new email and justify their reasoning.

Reflection

Ask learners: “Which phishing indicator did you overlook during your first attempt?”

Summary

Recap the five warning signs of phishing emails and the recommended response procedure.

Part 1 — Linear Courses / Type 4

I do – We do – You do

Watch, practice with support, perform independently. The classic architecture for procedural, step-by-step skills.

What is it

This instructional architecture teaches learners how to perform a procedure by first observing an expert, then practicing with guidance, and finally completing the task independently. The architecture follows a simple principle: Watch → Practice with support → Perform independently.

When to use it

Use this architecture when learners need to master a step-by-step procedure or perform a task consistently and accurately. It works best when correct execution is more important than exploring complex theory.

Strengths

Highly effective for procedural learning
Reduces learner anxiety by providing clear guidance
Builds confidence through gradual independence
Easy to assess using observable performance
Closely mirrors on-the-job training

Limitations

Less effective for developing critical thinking or creativity
Learners may imitate steps without understanding the underlying concepts
Requires realistic simulations for best results

Common Design Mistakes

Demonstrating too long or overly detailed
Removing guidance too early
Guided practice that simply repeats the demonstration
Final tasks that are much harder than the guided activities
Focusing on clicks instead of the purpose behind each step

When NOT to use it

Develop leadership or coaching skills
Make complex judgments
Solve open-ended problems
Explore multiple possible solutions
Build conceptual understanding before performing a task

Typical Examples

CRM systems ERP Software onboarding Operating equipment Medical procedures Manufacturing processes

Real-world Examples

Salesforce CRM Onboarding SAP Purchase Order Creation Medical Hand Hygiene Procedure Forklift Pre-operation Inspection CNC Machine Setup New Employee HR System Onboarding

Full Worked Example

"Creating a New Customer Record in the CRM"

Hook

A new customer has just called. Can you create their account correctly so the sales team can contact them?

Learning Objectives

By the end of this lesson, learners will be able to: Navigate the customer creation screen. Enter customer information correctly. Create and save a complete customer record independently.

Demonstration

Watch an expert complete the entire process of creating a new customer record, explaining each step.

Guided Practice

Complete the same task together. Learners follow on-screen prompts that highlight where to click and what information to enter.

Feedback

Immediate feedback is provided after each step (e.g., “The phone number format is incorrect.” or “The required field is missing.”).

Independent Practice

Create a customer record using a different customer profile without hints or guidance.

Final task

Complete the full customer onboarding process independently: create the customer, assign the correct sales representative, add contact details, and save the record correctly.

Reflection

Ask learners: “Which step of the process required the most attention? Which mistakes are you most likely to make in your daily work?”

Summary

Recap the workflow: Create → Complete Required Fields → Assign Owner → Review → Save. Remind learners that accuracy is essential because incorrect records affect the entire sales process.

Part 2 — Scenario-Based Courses / Type 1

Decision → Consequence → Debrief

Face the situation, decide, see what happens, understand why. The foundational scenario-based architecture.

What is it

Scenario Based Learning is an instructional architecture in which learners are placed inside a realistic professional situation and must make a decision under uncertainty, then experience the consequence of that decision before receiving any explanation. The architecture follows a simple principle: Face the situation → Decide → See what happens → Understand why.

When to use it

Use this architecture when the skill is about judgment, not procedure — when there is no single correct action, only better or worse responses depending on context, and the learner needs to weigh competing priorities under real constraints (time pressure, incomplete information, conflicting stakeholder interests).

Strengths

Builds situation recognition, not rule recall — closer to how expertise actually forms
Makes consequences intrinsic and causal, rather than a right/wrong judgment
Surfaces real trade-offs, which increases transfer to ambiguous, real-world decisions
Naturally engaging — tension from an unresolved situation drives attention better than a stated learning objective does

Limitations

Harder and slower to design well than Explain → Practice — every situation needs a genuine, defensible dilemma
Can frustrate learners who want a clear “correct answer” to hold onto
Poor execution (fake dilemmas, obvious right answers) collapses back into a disguised knowledge test
Less suitable when the required behavior really is a fixed procedure with no room for judgment

Common Design Mistakes

Starting from the answer options, and reverse-engineering a situation to fit them (should be the opposite: situation first, choices emerge from it)
Building a “right vs. obviously wrong” choice set (e.g., “follow policy” vs. “steal money”) — no real thinking required
Replacing consequences with an “Incorrect. Try again” message instead of a realistic outcome
Skipping the Debrief, so the learner never connects the outcome to the underlying principle
Branching for its own sake — adding paths that don’t change the professional stakes of the decision

When NOT to use it

Learn a fixed step-by-step procedure with one correct sequence
Memorize facts, rules, or policy text
Complete short compliance or awareness training with no real ambiguity
Get up to speed on something before they’ve seen the underlying concept at all (Scenario Based assumes some baseline familiarity to reason from)

Typical Examples

Difficult customer conversations Leadership and management dilemmas Ethical decision making Social engineering / phishing recognition Sales objection handling Incident response and risk triage Negotiation and conflict resolution

Full Worked Example

"The Feedback Nobody Wants to Give" — Managing conversations / people management

Hook

Slack message from a teammate: “Hey, are you going to say something about Alex’s deadlines? The rest of us are picking up the slack and it’s getting old.”

Situation

Alex has missed the last two deliverables. The team is quietly frustrated. You have a 1:1 with Alex in ten minutes.

Choice

(a) Address it directly right now in the 1:1
(b) Wait and observe one more sprint before saying anything
(c) Raise it with the whole team in the next stand-up, without naming Alex

Consequence

Direct now → Alex is defensive, feels ambushed, no context yet.
Wait → team frustration grows, someone else starts covering Alex’s work silently.
Whole-team → Alex doesn’t recognize themselves in it, nothing changes, but morale dips because others feel unheard.

Debrief

Principle: timely, private, specific feedback beats both avoidance and vague public signals — but timing without context can still backfire.

Next Situation

You raise it privately. Alex reveals they’ve been struggling with an unmanageable workload from another manager, on top of yours.

Choice

(a) Push for the original deadlines regardless
(b) Renegotiate scope with the other manager on Alex’s behalf
(c) Ask Alex to renegotiate their own workload directly

Consequence

[Not captured from the board — the Consequence content for this choice is missing from the screenshots. Add it once you confirm it.]

Debrief

Principle: solving the immediate problem for someone can undercut their long-term capability — coaching vs. rescuing is its own trade-off.

Boss-Level Challenge

Jordan, another teammate, privately says they’ve been struggling too but never spoke up — and noticed Alex got special support. How do you respond?

Choice

(a) Reassure Jordan the process was fair
(b) Acknowledge you should’ve checked in, ask what Jordan needs
(c) Match support immediately, no discussion
(d) Defer to the next scheduled 1:1

Final Consequence

Depends on choice — shown as a realistic shift in Jordan’s trust and openness, not right/wrong.

Final Debrief

Consolidate: feedback is never a single event — it’s a repeated judgment call between honesty, support, and fairness across the whole team, not just one person.

Summary

Timely + private + specific beats silence or public hints.
Solving it for someone isn’t always help.
Fairness across the team matters as much as fairness to one person.

Transfer to Own Work

Think of someone on your team right now you’ve been putting off a conversation with. What’s actually stopping you?

Next Steps

Feedback-conversation planning template; link to a short “structuring a hard conversation” job aid.

Part 2 — Scenario-Based Courses / Type 3

One Story — Many Decisions

One continuous story, a few decision points along the way, each shaped by the last, ending in one Capstone decision.

What is it

This is one continuous story, not separate cases like in Escalating Scenarios. The learner follows a single character or a single situation from start to finish, and at a few points along the way they have to make a decision. Each decision changes what happens next in the same story — so the story can branch, but it never resets to a new, unrelated situation. Simple way to think about it: One story, a couple of decision points along the way, each one shaped by the last, ending in one bigger decision that pulls it all together.

When to use it

The situations a person faces aren’t separate — they’re really one connected process (like handling one difficult client relationship over several weeks, not three unrelated ones)
You want the learner to feel the consequences build up over time, not just react to isolated moments
The skill is about managing something ongoing — a project, a relationship, a case — where earlier choices shape what options are even available later
You want to show that decisions aren’t isolated — what you decide now limits or opens up what you can do next

Strengths

Feels more realistic than separate scenarios — most real work is one continuing situation, not a series of one-off tests
Shows the learner that choices have knock-on effects, not just an immediate result
Keeps engagement high — it’s a story, so people want to know what happens next
Naturally teaches “big picture” thinking, since the learner has to keep track of what happened earlier
The Capstone Scenario at the end gives a strong sense of closure — it pulls everything together into one final, high-stakes moment

Limitations

Harder to build than separate scenarios — every decision point needs to connect logically to what came before and after
If a learner makes an early “wrong” choice, later parts of the story need to still make sense — this takes careful planning
Can get complicated fast if there are too many branches — easy to end up with a tangled story that’s hard to maintain
Learners who make an early mistake may feel “stuck” with a bad outcome for the rest of the story, which can be discouraging if not handled well
Because there’s no separate debrief after the Capstone, the takeaway has to be crystal clear in the Final Consequence and Summary

Common Design Mistakes

Making the story branches so different that it’s basically several separate stories glued together, not one connected story
Not really letting earlier decisions affect later ones — so decision points end up feeling disconnected anyway
Too many branches, so it becomes impossible to maintain or update later
No real “recovery path” for an early wrong choice — the learner just gets punished for the rest of the story with no way to improve things
Making the Capstone Scenario feel like just “one more decision” instead of the moment that brings the whole story together
Leaving the Final Consequence vague, since there’s no separate debrief afterward to clean up any confusion

When NOT to use it

Practice several unrelated situations that don’t naturally connect to each other (use Independent Scenarios instead)
Learn quickly, without following a longer story
Handle situations where real-life choices genuinely don’t affect each other

Typical Examples

Managing one client relationship over the life of a project, where early decisions affect trust later Leading a team through a change initiative, where early communication choices affect how much resistance shows up later Handling one investigation or case from start to resolution Coaching one employee’s performance over several conversations, where each conversation depends on the last

Full Worked Example

"The Client Who Kept Changing Their Mind" — Managing scope creep and client expectations over the life of a project

Hook

A new client project just kicked off. It looks straightforward. But how you handle the first small request outside scope will shape everything that happens over the next three months.

Beginning of story

You’re the project lead on a 3-month website redesign for a mid-size client. The contract is signed, scope is clear, timeline is tight but workable. The client’s main contact, Sarah, seems friendly and easy to work with. Week one goes smoothly.

Situation 1

In week two, Sarah messages you: “Quick one — could we also add a blog section? Shouldn’t take long, right?” It’s a small ask, technically outside the agreed scope, but sounds minor.

Choice

A) Say yes right away, since it sounds small and you want to keep the relationship smooth
B) Explain that it’s outside scope, and offer to log it as a change request to review cost/timeline impact together
C) Say no — the contract is the contract, and scope changes aren’t allowed

Consequence

If A: Sarah is happy, but two weeks later she starts treating “quick asks” as normal, assuming everything small is free.
If B: Sarah appreciates the transparency, and the process for handling future requests is now clearly set up.
If C: Sarah feels shut down and starts going around you to your manager for small asks instead.

Debrief

A feels helpful in the moment, but it quietly trains the client that scope doesn’t really apply — a costly assumption for a 3-month project. C protects the contract but damages the relationship and creates a workaround problem instead. B does both jobs at once: it keeps the relationship warm while keeping scope visible and manageable — which matters because this is one ongoing project, not a one-off request.

Story continues

Because of how you handled the blog request, Sarah now understands there’s a lightweight process for extra asks. Two weeks later, a bigger request comes in — not just “add a section” this time, but a proper reworking of the homepage layout that Sarah says “the whole leadership team wants now.”

Choice

A) Push back hard, reminding her this is a major departure from what’s been approved
B) Walk her through the change-request process again, but this time flag that this one will visibly affect the timeline and needs client leadership sign-off
C) Quietly absorb it into the existing timeline without raising it, to avoid another difficult conversation

Consequence

If A: Sarah feels frustrated that the same “small ask” attitude from before is suddenly being treated as a big problem — the earlier flexibility made this pushback feel inconsistent.
If B: The bigger stakes are made clear early, and because leadership has to sign off, they now understand the tradeoff themselves.
If C: The team absorbs extra work with no formal record — three weeks later, when the deadline slips, there’s no clear reason on file for why.

Debrief

A feels justified, but flip-flopping from “sure, no problem” to “absolutely not” over similar-sounding requests damages trust — the client can’t tell what the actual rule is. C avoids conflict short-term but sets the project up for an unexplained deadline slip later — exactly the kind of problem that becomes visible in the Capstone. B works because it keeps using the same visible process from Situation 1, just scaled to match the size of the request — consistency is what makes the process credible over time.

Story continues

It’s now week ten, close to launch. Because most requests have gone through the visible change-request process, there’s a paper trail showing three approved scope additions and their impact on the timeline. But now, one week before launch, Sarah calls you directly: “Leadership just saw the homepage and they want the whole navigation restructured before we go live. I know it’s late, but can we make this happen?”

Capstone Scenario

This is the biggest ask yet, at the worst possible time — right before launch, with real pressure from Sarah’s leadership behind it. Everything that happened earlier — the trust built through transparency, the visible record of previous changes and their costs — is now being tested at once.

Choice

A) Agree to make it happen, given how much goodwill has been built, and have the team work overtime to absorb it without changing the launch date
B) Use the established change-request process one more time — walk Sarah through exactly what this request would cost in time and risk to the launch date, and let her and leadership make an informed decision together
C) Refuse outright, citing how close launch is and how much has already been accommodated

Final Consequence

If A: The team delivers, exhausted, and the client is happy short-term — but the precedent is now set that any request, at any time, gets absorbed if you push hard enough, no matter the cost to the team.
If B: Sarah and her leadership see, in clear terms, exactly what a launch-week navigation overhaul would cost — and because the process has been consistent and transparent the whole project, they trust the numbers and make a decision they own, whether that’s delaying launch slightly or scoping the change down.
If C: The refusal, right after months of flexibility, feels like an abrupt reversal — Sarah feels the goodwill from earlier was conditional and disappears the moment it mattered most.

Summary

A visible, consistent process for handling scope changes — used the same way every time — builds trust more than either blanket “yes” or blanket “no”
Early small decisions set the pattern the client will expect later, for better or worse
By the time the biggest request comes, the goal isn’t to say yes or no — it’s to make sure the client can see the real cost and make the call themselves

Transfer / Final Challenge

Now try this with a client relationship where the first scope request comes from a stakeholder who isn’t your usual point of contact — someone with more authority, but less context on what’s already been agreed.

Part 2 — Scenario-Based Courses / Type 4

Independent Scenarios

Same skill, different unrelated situations, practiced side by side. Each scenario is fully self-contained.

What is it

The learner works through several separate situations, one after another — but unlike One Story — Many Decisions, these situations are not connected. Each one is its own self-contained case, with its own setup, its own choice, and its own consequence. What happens in Scenario 1 has no effect on Scenario 2 or Scenario 3 — they could be shown in any order and it wouldn’t change anything. Simple way to think about it: Same skill, different unrelated situations, practiced side by side.

When to use it

The learner needs to apply the same skill or principle across a variety of situations that don’t naturally follow one another in real life
You want to show the range of contexts where a skill applies, not build up one long story
Real work involves handling many unrelated cases of the same type (different customers, different tickets, different conversations) rather than one ongoing situation
You want practice reps on the same underlying judgment, without the complexity of tracking a continuous storyline

Strengths

Simple to design compared to One Story — Many Decisions — no need to track how earlier choices affect later ones
Easy to add, remove, or reorder scenarios without breaking anything else
Shows the learner that the skill generalizes across different contexts, not just one specific case
Lower risk of learners feeling “stuck” with a bad outcome, since each scenario is a fresh start
Easier to update over time — outdated scenarios can be swapped out individually

Limitations

Doesn’t show how decisions build up or affect each other over time — if that’s actually how the skill works in real life, this format misses it
Can feel repetitive if the scenarios are too similar to each other
Less engaging than a continuous story, since there’s no ongoing narrative pulling the learner forward
Doesn’t test the ability to manage an evolving situation — only the ability to judge separate moments

Common Design Mistakes

Making the scenarios so similar that they feel like the same case repeated with different names
Not varying the context enough — if every scenario is nearly identical, the learner doesn’t actually see the range of the skill
Treating this as “easier to build, so easier to get away with weak scenarios” — quality still matters, since there’s no ongoing story to carry engagement
Failing to make each scenario genuinely stand alone — accidentally referencing an earlier scenario creates confusing false continuity

When NOT to use it

Understand how decisions affect what happens later (use One Story — Many Decisions instead)
Feel the weight of a situation building over time (use Escalating Scenarios instead)
Practice with a real ongoing case, like managing one relationship or project

Typical Examples

Handling different customer service tickets, each with a different issue Practicing objection handling across a variety of unrelated sales conversations Recognizing different types of phishing attempts, each independent of the others Coaching conversations with different employees, each with their own separate context

Full Worked Example

"Reading the Room: Customer Service Judgment Calls" — Applying good judgment across different, unrelated customer situations

Hook

Every customer conversation is different. There’s no single script that works for all of them. Let’s see how well you can read what each situation actually needs.

Scenario 1

A customer calls in, calm and polite, asking to return a product that’s slightly outside the 30-day return window — by 4 days. They explain they were traveling and just got back. They’re not upset, just asking.

Choice

A) Explain the policy clearly, and offer a store credit as a reasonable middle ground
B) Deny the return firmly, since exceptions could set a bad precedent
C) Approve a full refund immediately, no explanation needed

Consequence

If A: The customer appreciates the flexibility and the clear reasoning — they leave satisfied and the exception is documented and reasonable.
If B: The customer accepts the answer but mentions they’ll think twice before shopping again — a small, avoidable loss of goodwill.
If C: The customer is happy, but there’s no record of why an exception was made, and it isn’t clear this was actually the best call given the circumstances.

Debrief

This situation had low emotional stakes and a legitimate, believable reason for going slightly over the deadline. A rigid “no” (B) protects the rule but ignores context that most reasonable policies are designed to accommodate. A full refund with no explanation (C) is generous but skips the judgment step entirely. A works because it’s a considered, explainable exception — not a blanket policy override.

Scenario 2

A different customer emails, furious, saying a product arrived damaged and demanding an immediate full refund plus a “formal apology in writing” from the company. Their tone is aggressive, using words like “unacceptable” and “incompetent.”

Choice

A) Match their tone with a firm, professional response defending the company’s quality standards
B) Acknowledge the frustration directly, confirm the refund, and address the actual issue (the damaged product) without getting drawn into the demand for a formal apology letter
C) Immediately send exactly what they asked for, including a formal written apology, to de-escalate as fast as possible

Consequence

If A: The customer’s tone escalates further — they now feel like they’re in a fight, not getting help.
If B: The customer calms down once they see the actual problem is being solved — the demand for a formal letter quietly stops mattering once the refund and acknowledgment land.
If C: The customer gets everything they asked for, but the interaction reinforces that aggressive tone gets the fastest, fullest response — a pattern that tends to repeat with this customer.

Debrief

A meets aggression with more friction, which almost never de-escalates anything. C solves the immediate case but rewards the tone, not the actual complaint — a distinction worth noticing, since this scenario is independent of Scenario 1 and is testing whether the learner can distinguish “what the customer is asking for” from “what will actually solve the problem.” B works because it addresses the real issue directly, without either escalating or over-rewarding the aggressive framing.

Scenario 3

A long-time, high-value customer messages casually, mentioning almost as an aside that a recent order arrived a few days late — no complaint, no demand, just a passing comment: “By the way, that last order took a bit longer than usual — no big deal though!”

Choice

A) Take it at face value since they said “no big deal,” and simply thank them for the note
B) Proactively offer a small gesture of goodwill (like a discount on their next order) even though they didn’t ask for one, recognizing their value as a long-term customer
C) Launch a full investigation into the shipping delay and report back with detailed findings

Consequence

If A: The customer’s comment is taken literally, but a small opportunity to reinforce loyalty with a long-time customer is missed.
If B: The customer is pleasantly surprised by the proactive gesture — it reinforces exactly why they’ve stayed a loyal customer.
If C: The customer, who said it was “no big deal,” now feels like their casual comment triggered an overblown response.

Debrief

This scenario is deliberately low-stakes and ambiguous — there’s no explicit request at all. C over-responds to a comment that wasn’t actually a complaint. A is a safe, literal reading, but misses a low-cost opportunity to strengthen a valuable relationship. B shows judgment that goes a step beyond just reacting to what’s said — reading the underlying value of the relationship even when nothing was explicitly asked for.

Capstone Scenario

A customer writes in about a delayed order. Their message is short and their tone is hard to read: “This is the second delay this month. Kind of frustrating tbh.” There’s mild irritation, some history (second time), but no explicit demand, no aggressive language, and no clear request for what they want done.

Choice

A) Treat it as a minor, low-stakes comment (like Scenario 3) and simply apologize briefly
B) Treat it as a serious complaint (like Scenario 2) and immediately offer a refund and formal escalation
C) Acknowledge the frustration and the pattern (second delay) specifically, ask what would help make it right, and offer a concrete gesture appropriate to a recurring issue — without overreacting or underreacting

Final Consequence

If A: The customer feels like the “second time” pattern wasn’t taken seriously — this isn’t a one-off like Scenario 3, and treating it that way undersells a real, recurring problem.
If B: The customer is surprised by how big a response their fairly mild message triggered — it feels disproportionate to what they actually said.
If C: The customer feels genuinely heard — the recurring nature of the issue is acknowledged, and the response matches the actual (moderate, not extreme) level of frustration shown.

Debrief

This case doesn’t match any single earlier scenario exactly — it borrows a little from each: a passing tone like Scenario 3, but with real substance behind it (a repeat issue) like Scenario 2, without the aggression of Scenario 2 or the true low-stakes nature of Scenario 3. The point of this capstone isn’t to remember which scenario it resembles — it’s to apply the same underlying judgment used throughout: read what’s actually being said, match the response to the real weight of the situation, and don’t default to a script from a previous case just because it feels similar on the surface.

Summary

The same situation-reading skill applies across very different contexts — calm, aggressive, casual, and ambiguous
Matching your response to the actual situation matters more than following one fixed rule
Not every signal is a clear request — sometimes reading between the lines (Scenario 3, Capstone) is part of the judgment
A recurring issue (Capstone) deserves a different weight than either a first-time minor issue or an isolated angry outburst — recognizing that difference is the real skill being tested

Part 2 — Scenario-Based Courses / Type 5

Sandbox

Give a goal, give a safe space to try things, let the learner explore instead of choosing from preset options.

What is it

Sandbox is different from every other scenario type here — instead of walking the learner through fixed situations with predetermined choices and consequences, it gives them an open space to try things freely. There’s a task or goal, but no single “correct path” scripted in advance. The learner experiments, sees what happens, and can try again — closer to a simulation or practice environment than a branching story. Simple way to think about it: Give a goal, give a safe space to try things, let the learner explore instead of choosing from preset options.

When to use it

The skill genuinely has many valid approaches, not one “correct” choice among a few options
You want the learner to build real fluency through repeated, low-stakes practice — not just recognize the right answer once
The real-world task involves tools, interfaces, or open-ended problem solving where trial and error is how people actually learn
Failure in the sandbox is cheap and safe, so exploring “what happens if I do this” has real value
You want to build confidence through hands-on repetition rather than testing judgment on a single decision point

Strengths

Builds real skill through doing, not just recognizing the right answer among options
Lets learners try different approaches and see the results, without being boxed into A/B/C choices that may not reflect how they’d actually think through it
Naturally supports different paces and learning styles — some learners will explore more, others will go straight for an efficient approach
Mistakes are low-stakes and reversible, which encourages experimentation rather than fear of getting it wrong
Closely mirrors real practice environments — sandboxes, test systems, rehearsal spaces

Limitations

Harder to design well — an open sandbox needs realistic constraints, feedback, and a clear enough goal, or it becomes aimless
Harder to guarantee everyone reaches the same learning outcome, since paths through it can vary a lot
Requires more sophisticated tooling or simulation than a simple branching scenario
Can be less structured feedback than a scripted Choice → Consequence → Debrief, so learners may not always understand why something worked or didn’t
Not ideal for skills where there really is one correct procedure to follow

Common Design Mistakes

Making the sandbox too open-ended, with no clear goal — learners wander without direction and don’t know what “good” looks like
Providing a task without meaningful feedback on the outcome of what the learner tried
Making the “safe space” not actually feel safe — if mistakes feel punished, learners stop experimenting
Treating this like a scripted scenario with hidden “right answers” instead of genuinely supporting multiple valid approaches
Skipping a debrief or wrap-up, leaving the learner unsure what they actually learned from their exploration

When NOT to use it

Learn one specific correct procedure precisely, with no room for variation (use I do – We do – You do instead)
Get quick, clear feedback on a single judgment call (use Decision → Consequence → Debrief instead)
Complete something in a short, predictable amount of time — open exploration takes longer and is less predictable

Typical Examples

Practicing in a sandbox CRM environment before working with real customer data Trying out a new software tool or interface in a safe test environment Rehearsing a negotiation or difficult conversation with no fixed script, just a goal Free-form troubleshooting practice, where there are multiple valid ways to diagnose a problem

Worked Example 1

"New CRM System: Find Your Way Around" — Building fluency with a new CRM interface through hands-on exploration

Hook

The best way to learn a new system isn’t to memorize a manual — it’s to just start using it. Here’s a safe practice environment where nothing you do can break anything real. Let’s explore.

Task

Your first task: create a new customer record in the CRM for a customer named “Alex Morgan” and add a note that they called about a billing question.

Explore the environment

Before jumping in, take a few minutes to click around the practice CRM. Nothing here is real data, so try things: open menus you haven’t seen before, check what different buttons do, look at how existing customer records are laid out. There’s no wrong way to look around.

Choice

You decide how to start creating the record.

Choice

Use the “+ New Customer” button on the main dashboard
Search for “Alex Morgan” first to confirm they don’t already exist, then create the record
Go through the Contacts tab and look for a bulk-import option instead

Consequence

If you search first: The system shows no existing match, and you’re taken directly into a pre-filled “new record” form — slightly faster, and it avoids the common mistake of creating duplicate customer entries.
If you use “+ New Customer” directly: It works fine, but you notice afterward that the system flags a possible duplicate warning you would have caught by searching first.
If you try bulk-import: You realize quickly this tool isn’t meant for single entries, and you back out — no harm done, but not the right tool for this task.

Next task

Now that Alex Morgan’s record exists, a second task: Alex just called again, this time asking to update their contact email and to flag their account as “VIP” for faster future support.

Choice

You decide how to handle the update.

Choice

Open Alex’s existing record directly from the dashboard’s “Recent Customers” list
Search for Alex Morgan again from scratch
Try editing the record from the notes panel instead of the main profile page

Consequence

If you use “Recent Customers”: It’s right there since you just created it — fastest path, and you find both the email field and a “VIP” toggle easily on the main profile page.
If you search again: It works, just takes a couple of extra clicks compared to using Recent Customers.
If you try editing from the notes panel: You discover the notes panel only lets you add notes, not edit core profile fields — you have to navigate back to the main profile page anyway.

Task complete

You’ve now created a new customer record and updated it with new information — the two most common actions you’ll take in this CRM day-to-day.

Debrief

There wasn’t one single “correct” path through either task — the CRM supports multiple ways to get to the same result, and part of building real fluency is discovering which shortcuts work best for you. A few things worth noticing from this practice: searching before creating a new record helps avoid duplicates, the “Recent Customers” list is often the fastest way back into a record you just touched, and core profile fields (like email or VIP status) live on the main profile page, not in the notes panel.

Summary

The CRM supports more than one way to complete the same task — there’s no single script to memorize
Searching before creating a new record helps avoid duplicate entries
Recently touched records are quickest to find again through “Recent Customers”
Core profile fields (email, VIP status, etc.) are edited from the main profile page, not the notes panel
The fastest way to get comfortable with a new system is to explore it directly, not just read about it

Worked Example 2

"Practice Negotiation: Salary Conversation Simulator" — Building comfort and technique in negotiation conversations through free-form practice

Hook

There’s no single script for negotiating a raise — the right words depend on how the conversation actually goes. Practice this simulated conversation as many times as you want. Nothing here affects your real salary — it’s a safe space to find what works for you.

Task

Your task: have a conversation with a simulated manager (an AI-driven chat character) to negotiate a 10% raise, based on your strong performance this year.

Explore the environment

Before starting the actual negotiation, take a moment to look around the simulator: check the “manager profile” tab to see what you know about this character’s communication style, review the sample performance data you’ll be referencing, and try sending a throwaway message just to see how the simulated manager responds.

Choice

You decide how to open the actual conversation.

Choice

Open directly with the number: “I’d like to discuss a 10% raise.”
Start by reviewing your accomplishments first, then transition into the ask
Ask the manager first what they think of your performance, before bringing up the raise at all

Consequence

If you open with the number directly: The simulated manager responds somewhat defensively, asking “based on what?” — you’re now negotiating from behind, justifying the number after the fact.
If you lead with accomplishments: The manager engages positively, and by the time you raise the number, it feels like a natural next step rather than a demand.
If you ask their opinion first: The manager gives generic positive feedback, but you don’t get a clear enough opening to transition smoothly into the actual ask — the conversation stalls a bit.

Next task

The simulated manager responds: “I hear you, but budgets are tight this year. I don’t think 10% is realistic right now.” Now you have to respond to pushback.

Choice

Hold firm on the exact number and restate your case
Ask what number, if any, might be realistic, and explore alternatives (bonus, title change, review timeline)
Back down immediately to avoid conflict

Consequence

If you hold firm: The manager repeats that it’s not realistic — you’re now at a bit of a standoff, and the conversation doesn’t move forward much.
If you explore alternatives: The manager opens up about a possible mid-year review instead, or a smaller raise plus a bonus — the conversation becomes collaborative instead of adversarial.
If you back down immediately: The manager readily agrees there’s no raise this cycle — the conversation ends quickly, but you got nothing you were asking for.

Task complete

You’ve now practiced opening a negotiation and handling pushback — the two moments most people find hardest in a real salary conversation.

Debrief

There’s no single “correct” script here — different openings and different responses to pushback all lead somewhere different. Leading with evidence before the number tends to make the ask land better than leading with the number alone, and treating pushback as a chance to explore alternatives tends to keep the conversation moving, while holding firm or backing down both tend to end it — just in opposite directions. Try the simulation again with a different opening or a different response to pushback, and see how the conversation changes.

Summary

There’s no single correct script for a negotiation — different approaches lead to genuinely different outcomes
Leading with evidence before the ask tends to land better than leading with the number
Treating pushback as a chance to explore alternatives keeps the conversation moving, more than either holding firm or backing down
Real comfort with negotiation comes from practicing multiple approaches, not memorizing one “right” way to do it

Gamification in Education / Introduction

What is Gamification

Gamification is the practice of borrowing mechanics from games — points, levels, quests, trading, guilds — and applying them outside of games, to make an activity more engaging and to shape behavior. Not every game mechanic works the same way: some motivate a single person acting alone, others only exist because other people are involved.

Gamification in Education / Introduction

Individual vs. Social Mechanics

A game mechanic answers the question "what does the player do?" A social mechanic answers a different question: "how does the player interact with other people?" If a game only has things like completing a level or collecting coins, those are individual mechanics. The moment it includes asking for help, trading an item, joining a team, or gifting something, the mechanic becomes social — it stops existing the moment other people are removed.

This section keeps the two apart on purpose. Individual mechanics can be designed into any course, solo or not. Social mechanics only pay off once there's a real cohort, community, or team to design for.

Individual Mechanics

Progress & Achievement

Levels, Points, Progression, Quests, Combo, Achievements — mechanics that make growth visible and give it a shape.

Achievements

A visible, virtual or physical record of something the learner has already completed.

Achievements let players — or students — indirectly show off what they've done.

Achievements can attach to almost anything: they show progress, add challenge and depth, and can be easy, hard, surprising, fun, solo, or team-based.

Seen elsewhere

The badges given for visiting U.S. national parks, or brand logos people display — visible proof of something completed.

Apply in learning

Award a badge for finishing all of a week's tasks ahead of schedule
Give a distinct achievement for completing a module with zero absences

Levels

A linear progression system that rewards accumulated points with increased value — often unlocking new features or abilities as the learner moves up. One of the most motivating components of any game.

Level progression can be flat, exponential, or wave-shaped, and can be tied to unlocking real content or used purely as a motivational marker of "how far I've come."

Seen in games

World of Warcraft — higher levels unlock talent points, so the higher a player climbs, the more powerful their character becomes.

Apply in learning

Unlock new content or tools as a learner's level rises
Use levels purely as a progress marker, independent of content gating

Points

A running quantitative value awarded for a single action or a combination of actions.

Points steer people toward the actions the designer wants rewarded. Weighting some actions higher than others is itself a design lever: whatever earns more points is what players will chase.

Seen in games

Pac-Man — every pellet earns points, but eating a ghost earns far more, which is exactly why players hunt ghosts instead of only eating pellets.

Apply in learning

Weight points toward the behaviors that actually matter (depth of answer, not speed)
Use points as the backbone of a loyalty-style recognition system

Progression

A mechanic that lets a person see that they are developing — not just that they're getting stronger, but that the growth is measurable and visible.

A person needs to see that today they are further along than yesterday.

Seen in games

Classic RPG arc: a level-1 hero with a weak weapon becomes, a few hours later, a level-20 hero with rare gear and tougher enemies to match.

Apply in learning

"3 of 10 modules complete," "12 of 40 skills mastered," "80% of course complete"
Show proficiency moving from "novice" to "confident user," not just a percentage

Quest

A task made of one or more goals the player must complete to advance and earn a reward. Unlike a plain task, a quest has context, a purpose, and a sense of a journey.

Not "do the assignment," but "set off on a small adventure with a clear goal."

Seen in games

World of Warcraft — a quest is rarely phrased as "kill 10 wolves"; it's embedded in a story: "Wolves are terrorizing the village. Help the hunter protect its people."

Apply in learning

Reframe "study the topic and take the test" as a mission: prepare a presentation for an important client, which requires researching, selecting arguments, building the deck, and defending the decision

Combo

A combination of several actions performed in a specific order or within a time window, rewarded with a bonus beyond what any single action would earn.

Not just "do the action" — successfully chain several actions together.

Seen in games

Shooters reward a kill streak; platformers reward collecting several coins in a row without a mistake.

Apply in learning

Watched the video → completed the practice → passed the same-day quiz → earned a bonus badge
Studied five days in a row → earned a bonus

Individual Mechanics

Reward Timing

Appointment Dynamics, Urgent Optimism, Reward Schedule, Bonus, Free Lunch, Lottery, Countdown — mechanics built around when a reward arrives, not just what it is.

Appointment Dynamics

A dynamic where the player must return to the game, or take part in it, at a predetermined place or time in order to get a positive outcome.

Seen in games

FarmVille — players have to come back to harvest crops within a set window after planting, or the harvest spoils and the earnings are lost.

In marketing: "happy hour" — arrive within the set window, order one drink, get two.

Apply in learning

Time-boxed live Q&A slots that only "pay off" if the learner shows up
A weekly window where a bonus challenge is available

Urgent Optimism

The state of wanting to act right now, because the person believes that if they try, they have a real chance of succeeding.

I believe I can handle this, so I start acting immediately.

If either half disappears, the mechanic breaks: urgency without hope creates anxiety and a sense of futility; hope without urgency creates the urge to postpone.

Seen in games / marketing

"Try the service free for 14 days," "free shipping today only," "12 seats left for the webinar."

Apply in learning

"A bonus case study is open today only. You have 24 hours — succeed and you'll get personal feedback from an expert."

Reward Schedule

The rules that govern when and how a system hands out rewards — not just the reward itself, but its timing, predictability, and the actions it's tied to. A fixed-interval schedule is a specific case: the reward arrives after a set stretch of time (e.g. every 30 minutes), which produces a low-engagement dip right after each reward, rising activity as the next one approaches, and then the cycle repeats.

Seen in games

World of Warcraft — killing a set number of enemies predictably levels up the hero. Tetris — clearing a line pays out instantly. FarmVille — the harvest arrives after a fixed wait, tying the reward to anticipation and a return visit.

Apply in learning

A daily bonus inside a learning app, mirroring the fixed-interval pattern
A weekly "featured resource" drop

Bonus

An extra reward on top of the normal one, earned for meeting a specific condition — the key difference from a regular reward is that it isn't guaranteed for every action; it requires extra effort.

Do a little more — get more than you expected.

Apply in learning

Completed all of the week's tasks → gets an extra debrief session
Submitted the project early → gets personal feedback
Helped three other participants → unlocks a closed webinar

Free Lunch

A mechanic where the person feels they've received value with almost no effort of their own, because someone else — or the system — already did the underlying work.

The key is not to deceive the player: they need to understand where the benefit actually came from. "I got lucky — I got more than I put in."

Seen in marketing

A special offer becomes cheaper because a hundred other people already bought it — there's no trick, the buyer understands the work was done (by others), they just didn't have to do it themselves.

Apply in learning

A new cohort starts with a shared knowledge base built by last year's learners, so day one already feels ahead of zero
Pre-filled templates or starter notes from an instructor let learners begin from a head start instead of a blank page

Lottery

A dynamic where the winner is determined entirely at random, creating a high level of anticipation. The fairness of the process is often questioned — winners tend to keep playing without limit, while losers tend to leave, despite the random split between the two groups.

Seen in

Many forms of gambling and lottery tickets.

Apply in learning

A prize draw among everyone who submits an optional practice assignment, to nudge participation without making it mandatory
Use sparingly and transparently — random rewards work best for optional extras, not for core learning outcomes

Countdown

A dynamic where players are given a fixed amount of time to accomplish something. It creates a rising activity curve as the deadline approaches, and stops activity outright once time runs out.

Seen in games

Bejeweled Blitz — 30 seconds to score as many points as possible; bonus rounds and time-limited levels work the same way.

In marketing: countdown timers showing when a sale ends.

Apply in learning

A visible timer during a timed case-study exercise, mirroring real deadline pressure
"Early-bird" enrollment window for a cohort that closes registration bonuses after a set date

Individual Mechanics

Motivation & Meaning

Epic Meaning, Blissful Productivity, Behavioral Momentum, Ownership, Status, Discovery, Layered Information — mechanics that shape why the effort feels worth it.

Epic Meaning & Calling

The feeling that your actions are part of a larger, meaningful mission that outweighs personal gain — the person feels they're taking part in something important and valuable.

People are willing to invest enormous effort if they believe they're doing something genuinely important.

Seen in games

World of Warcraft — narratively, the player isn't just killing monsters and gathering resources; they're saving kingdoms and standing against ancient evil. Players even built the WoWWiki encyclopedia entirely on their own time, for free, because they felt part of something larger.

Apply in learning

Frame a course around the real-world stakes it serves, not just the skill it teaches

Blissful Productivity

The state of enjoying hard work because every action feels meaningful, moves you toward a goal, and produces a visible result immediately.

The pleasure doesn't come from the reward itself — it comes from the process of being productive.

Seen in marketing

Apple Watch's closing activity rings — the pleasure comes less from the watch and more from the feeling "I hit my target today."

Apply in learning

Design tasks so each step produces something visibly finished (a working prototype, a filled-in worksheet) rather than an abstract step toward a distant grade
A daily practice streak with a simple visual (a filled square per day) that makes the work itself feel satisfying

Behavioral Momentum

A person's tendency to keep going with an action once they've already invested time, effort, or attention in it — the longer someone has been doing something, the harder it becomes to stop, even if the original goal no longer matters much.

Seen in marketing

Marketers try to get someone to complete one small first action — start a free subscription, favorite an item, add something to cart — after which the odds of further action rise sharply. Many services deliberately break the customer journey into small sequential steps for this reason.

Apply in learning

Open a course with a very small, quick first task (answer one question, watch a 2-minute video) to get momentum going before the harder material
Break a long assignment into small sequential checkpoints so each completed step pulls the learner into the next

Ownership

A powerful mechanic that underlies loyalty. Games where the player owns a pet or companion create a strong emotional response — players want to protect and care for what's theirs.

What we consider ours becomes far more valuable to us.

Seen in games

Nintendogs, Club Penguin's Puffles — the sense of ownership is what drives the emotional attachment.

Apply in learning

Let learners personalize a workspace, portfolio, or project they'll keep building throughout the course
Have learners "adopt" a running case study or project of their own choosing that they carry from module to module

Status

Players are frequently motivated by the drive to reach a higher level or standing — also connected to envy. In learning contexts, status can recognize achievement, experience, or contribution to a community, unlocking new capabilities as a person advances (e.g. reviewing others' work, moderating discussions).

Seen in marketing

Airline Silver/Gold/Platinum tiers unlocking lounges and priority boarding; Sephora Beauty Insider tiers unlocking early access and exclusive gifts.

Apply in learning

Experienced learners earn the status to review or mentor newer ones, rather than just a higher number on a leaderboard
A "trusted contributor" tier that unlocks moderating discussion threads or early access to new material

Discovery

Also called exploration. Players enjoy uncovering something new and being surprised — this in itself is a game-like quality. Discovery encourages people to visit new pages or areas, increasing time spent and depth of engagement.

Seen in games

World of Warcraft — discovering new lands earns bonus experience points, with dedicated achievements for exploration.

Apply in learning

Give an increasing bonus based on how many new pages/resources a learner explores each week

Layered Information Theory

You don't need to tell the player everything at once. Information should be revealed in small portions, exactly when it becomes necessary.

The core idea: give a person exactly as much information as they need right now.

Apply in learning

Reveal an advanced technique only after the learner has struggled with the basic version — the failure creates the appetite for the detail
Use progressive disclosure in a tool tutorial: show only the next relevant button, not the whole interface at once

Individual Mechanics

Spreading the Loop

Virality, Community Collaboration, Infinite Gameplay — mechanics about extending engagement outward to other people, or keeping it going indefinitely.

Virality

A mechanic where a player gains extra value when other people join or take part. The experience becomes more interesting, easier, or more rewarding once the user invites friends or interacts with other players — which is exactly why players start spreading it themselves.

Apply in learning

A student unlocks a bonus case after inviting a colleague
A practical assignment can only be completed in pairs
A group earns a shared bonus once every member finishes the module

The value comes not from the invitation itself, but from the joint activity it enables.

Seen in marketing

A new user gets a discount via a referral link, while the referrer gets a bonus on their next purchase.

Community Collaboration

A dynamic in which an entire community joins forces to solve a puzzle, crack a problem, or clear a challenge together. Highly viral and genuinely fun.

Apply in learning

A cohort-wide challenge where individual contributions (solved problems, shared notes) add up to a collective target
A shared class project or knowledge base that only comes together if enough learners contribute their piece

Infinite Gameplay

Games without a defined end point — best suited to casual games that can "refresh" their content, or to games where the reward is simply a stable, positive ongoing state.

Seen in games

FarmVille — a relatively stable, ongoing position is already a form of winning.

Apply in learning

An always-open practice space or resource library that keeps offering fresh material after the formal course ends
A recurring "skill of the month" track with no final finish line, aimed at habit rather than course completion

Social Mechanics

Social Exchange

Help, Gifts, Reciprocity, Mentorship, Trading, Teamwork

Help

Creating a situation where one person is able to make the path easier for another — informational (explain, point the way), practical (do it for them), or emotional (encourage, praise).

Why it works

Reciprocity — being helped creates a desire to help back. Competence — helping someone makes you feel "I'm good at something." Belonging — the act of helping signals "you're one of us."

Seen in games

World of Warcraft — help exists at every level, and the game gives no reward for it at all; players do it because it makes them feel expert, respected, and connected. Death Stranding — players never meet, yet leave ladders, bridges, and roads for strangers to use later — help given to someone you'll never see, by someone who'll never see you.

Apply in learning

"Explain it to a newcomer" — after finishing a topic, the system randomly matches the learner with someone who's stuck, and they record a short voice explanation
An "SOS" system where each learner has a limited number of help requests; whoever answers earns reputation, not points
A group task that's impossible to solve alone — one learner sees the description, another the image, a third the grading criteria

Gifts

The voluntary transfer of value from one player to another with no immediate exchange expected — the value can be an item, currency, time, knowledge, or anything else useful.

Why it works

A gift creates a social bond between people; it produces gratitude, trust, and a sense of belonging to the same community. A gift is not a system-issued reward — it only counts when one person voluntarily hands value to another.

Seen in games

Pokémon GO — players send daily gifts to friends, deepening the friendship level and unlocking bonuses. Animal Crossing — gifting furniture and materials is core to how the game's economy and community feel work.

Apply in learning

"Share a find" — if a learner discovers a useful article or resource, they can gift the recommendation to the group and get recognized for helping others learn
"Gift time" — a learner strong in a topic offers a 15-minute consultation slot to a peer
A "gratitude bank" — after a joint project, teammates send each other recognition cards that accumulate in a professional profile

Reciprocity

A player responds to another player with a matching action, because they earlier received help, a gift, or support from them — the unspoken rule of "you helped me today, I'll help you tomorrow." Usually there's a time gap between the two actions.

Why it works

Breaking the "you scratch my back, I'll scratch yours" rule creates real discomfort and can cost someone others' trust. Over time it builds confidence that support will be there in a difficult moment.

Gift vs. reciprocity: a gift is a voluntary transfer with no expectation of an immediate answer — it creates a connection. Reciprocity is the answer to value already received — it maintains and strengthens a connection that already exists.

Apply in learning

Add a way to "pay help forward" — after a learner who received a consultation finishes their task, the system offers them a chance to help someone else
A "time credit" system: a learner who gave a half-hour consultation earns the right to request help from any other community expert later

Mentorship

A more experienced player helps a less experienced one learn the game, passing on knowledge, skill, and experience. Unlike ordinary help, which usually solves one specific problem, mentorship is a long-term relationship aimed at developing the other person — the mentor's goal is not to do the task for the newcomer, but to make sure they can handle it alone in the future.

Why it works

For the mentee, a mentor reduces anxiety and uncertainty and speeds up confidence. For the mentor, teaching builds a sense of competence and significance — and explaining material well forces you to understand it more deeply yourself (the "learning by teaching" effect). Mentorship also builds durable social bonds, which is part of why some communities last for years.

Seen in games

Final Fantasy XIV — an official Mentor system: experienced players who meet certain requirements get a mentor badge and access to a dedicated help channel. Destiny 2's "Sherpa" community — experienced players who volunteer to walk newcomers through hard raids, sometimes over several hours, aiming to teach the mechanics rather than just carry them through.

Apply in learning

Appoint students who successfully finished the previous cohort as mentors for the next — both sides win, since mentoring reinforces the mentor's own knowledge
"Study pairs" — an experienced participant accompanies one or two newcomers through the course, asking questions and pointing to resources rather than doing the work for them
"Become a mentor" — finishing a course automatically unlocks the ability to help the next cohort

Trading

Players voluntarily exchange resources because each side receives something they value more. Trading emerges once people can no longer produce everything they need alone and start to specialize.

Why it works

People gain a sense of control — the decision to buy, sell, or trade is theirs, reinforcing autonomy, one of the basic psychological needs. Trading also lets each person lean on their own strengths, and successful trading gradually builds trust between regular partners.

Seen in games

EVE Online — the entire economy is player-run: prices are set by supply and demand, not developers, and some players build entire careers purely as traders. RuneScape's Grand Exchange is a centralized marketplace for nearly any in-game item.

Apply in learning

A "skills marketplace" — one student is strong in Excel, another in presentation design, a third in statistics; instead of only asking the instructor, participants trade skills directly
An "expertise exchange" — an employee runs a one-hour CRM consultation and earns credit redeemable for a colleague's consultation on finance or project management
Trade time, experience, knowledge, templates, and feedback — not just points or currency

Teamwork

Players can only reach a goal through joint action, with everyone participating on equal footing. Success depends not on any one player's strength but on how well the team coordinates.

Why it works

Teamwork strengthens belonging — achieving a goal alongside others makes a person start seeing themselves as part of the team. Shared victories are remembered more strongly than individual ones, especially when everyone contributed meaningfully, and repeated reliable teamwork builds trust within the group.

Seen in games

Overwatch 2 — tanks protect, damage dealers deal the hit, support heals and buffs; even a very strong player rarely wins alone if the team doesn't coordinate. Keep Talking and Nobody Explodes — one player sees the bomb but not the instructions, another has the instructions but not the bomb; the puzzle is solvable only through constant communication.

Apply in learning

Design tasks where participants genuinely depend on each other — one gets raw data, another gets the analysis tools, a third gets the grading criteria, a fourth presents the final solution
Grade joint case work only at the team level, so participants help strugglers instead of competing with them

Social Mechanics

Competition

Race, Leaderboards, Tournaments, Flower Picking, Pac-Man Mechanics, Tug-of-War, Handicapping, Secrets, Last Man Standing, Wagering, Bluffing & Deception, Third-Party Wagering

Race

Whoever reaches the goal first wins — it doesn't matter by how much, only that you were first. Rarely used in purely social games.

Why it works

Races create urgency and excitement. First place carries outsized emotional value — the gap between first and second feels much larger than between second and third.

Seen in games

Mario Kart, Trackmania, speedrun communities. Duolingo's weekly leagues carry a similar "racing" feeling even though formally they're a leaderboard.

Apply in learning

Small sprints — first to solve the problem, find the bug, or clear a mini-quiz
Better: race for regularity, not speed — first team to finish the week's module, first to collect all required skills — with quality as the entry bar, not just speed

Leaderboards

Players compete asynchronously by comparing results rather than playing at the same time — each plays at their own convenience, and results accumulate in a shared ranking.

Why it works

Satisfies the human need to compare ourselves to others to define our self-image. Even moving from 150th to 80th feels like an achievement and keeps people motivated — and the higher someone climbs, the more they want to defend the position.

Seen in games

Duolingo's weekly leagues, promotion between divisions.

Apply in learning

Rank by multiple criteria — solution quality, modules completed, discussion activity, helping others — not just raw points
Weekly leaderboards that reset regularly, so newcomers always have a real shot and top performers don't permanently occupy the top spots
Show a few peers just above and below a learner, rather than the full list — a nearby target feels achievable, unlike chasing a distant leader

Tournaments

Players are split into pairs or groups and progress through several stages until one winner remains. Unlike a race or a leaderboard, what matters is a series of consecutive wins, not one single result.

Why it works

Tournaments create a sense of progress — each stage won feels like a small victory bringing the finals closer. People also compare themselves against a small pool of rivals rather than the entire world, which feels far more achievable.

Apply in learning

A knock-out series of mini-quizzes where the strongest advance each round
A "project tournament" — teams defend ideas within their group first, then winners meet in semifinals and a final

Flower Picking

A limited resource periodically appears on the map, and players compete over who grabs it first. The competition isn't direct between players — it's a race against the clock for a scarce resource.

Why it works

Scarce, periodic resources trigger a strong scarcity effect, and the recurring "maybe it's already there — better check" feeling pulls players back regularly.

Seen in games

Pokémon GO — rare Pokémon appear only at certain times and places, so players race to the spot before someone else gets there first.

Apply in learning

Only the first 10 people get individual expert feedback
A hard bonus case with extra points drops once a week
A limited number of seats for a live review or masterclass

Pac-Man Mechanics

Whoever collects the resource first, gets it — a continuous scattering of small, collectible resources across a space, competed for indirectly through gathering speed rather than direct confrontation.

Apply in learning

A shared pool of bonus questions or optional resources that any learner can claim first, encouraging steady engagement without direct confrontation
First-come slots for feedback sessions or office hours, rewarding promptness rather than pure skill

Tug-of-War

Two sides fight over a shared resource or territory, and the balance is constantly shifting rather than settled by a single victory — the game becomes a continuous struggle for advantage.

Why it works

Creates a strong sense of agency: any single action can shift the balance, capture a point, or move a team closer to winning. It also keeps tension alive to the very end — even a losing team can feel the situation is still reversible.

Seen in games

Overwatch 2's Push mode — both teams push one robot in opposite directions, and it only ever moves toward whichever team currently controls it. Splatoon — territory is painted and re-painted continuously, and the winner is decided by how much territory they control at the end, not kill count.

Apply in learning

A shared progress bar that shifts toward the team answering more questions correctly
Two groups defend different case solutions, gathering expert votes that shift the bar
Departments compete on a shared KPI, gradually "pulling" the bar to their side

Handicapping

Artificially evens the odds when one competitor is significantly stronger than another — the stronger player faces slightly more friction, the weaker one gets slight help. The goal is to preserve suspense and give everyone a real shot.

Why it works

People enjoy competition only when victory feels possible. If a beginner already knows they can't win, motivation disappears fast — but an expert who wins effortlessly every time also gets bored. Handicapping keeps both sides in the "zone of optimal challenge," where the task feels hard but doable.

Seen in games

Mario Kart — players in last place get stronger items (Blue Shell, Bullet Bill), leaders get weaker bonuses, keeping the race uncertain until the finish.

Apply in learning

Give beginners more time on a task, give advanced students harder cases
Vary team starting conditions based on prior performance

Secrets

Built on the idea that not all information is available to the player immediately — finding a hidden item, location, character, or path requires exploring, experimenting, or exchanging knowledge with other players. A secret doesn't need to be required to finish the game; the best secrets are simply a pleasant reward for the curious.

Why it works

Sensing "something is hidden here" triggers curiosity that pulls the player to keep exploring, and finding a secret creates a feeling of discovery — of having found something themselves, not just completed a checklist item. People also love sharing secrets, which is why great games grow forums, guides, and whole communities of explorers around them.

Seen in games

Dark Souls — illusory walls, hidden passages, optional bosses and entire areas can be missed entirely on a first playthrough.

Apply in learning

Hide extra materials that unlock only after solving a hard problem
Leave "easter eggs" in lessons — interesting facts or bonus tasks
Build alternate paths through the course that a student can discover on their own

Keep secrets optional and rewarding, never a required part of the course — they should reward curiosity, not punish the people who didn't find them.

Last Man Standing

Play continues until only one winner (or one team) remains, with everyone else gradually eliminated. Unlike a tournament, which follows a pre-set bracket, everyone is in the same match at once and the field shrinks over time.

Why it works

Built on constantly rising tension — early on, a player is one of many and can afford to be cautious, but as fewer remain, every mistake costs more. It also creates a survival effect: the goal isn't necessarily to defeat everyone, sometimes it's simply to outlast them.

Seen in games

PUBG and Fortnite's shrinking safe zone; Fall Guys reframes it without weapons, as an elimination obstacle course; Tetris 99 shows it works even in a puzzle game.

Apply in learning

Use "soft elimination": a learner can stop competing for first place but keeps learning
Several teams solve a case, and only the strongest solution advances after each stage
A marathon where difficulty rises after each task, so only the best-prepared reach the final round

Wagering

A player risks something valuable for the chance to gain even more — money, resources, items, time, rating, or any other in-game value.

Why it works

People feel a potential loss far more sharply than an equivalent gain — loss aversion. Even a small wager sharply raises emotional engagement, and the perceived value of a stake depends less on its absolute worth than on how hard it was to earn.

Seen in games

Poker — the psychological stakes come less from the cards than from the size of the pot. Modern games often soften wagering's downside (insurance on lost gear, fast rating recovery) to keep losses from driving players away entirely.

Apply in learning

A team stakes part of its accumulated points before a hard challenge
A student can risk an attempt: double points for a correct answer, lose some earned points for a wrong one
Participants "forecast" their own result and get a bonus for an accurate self-assessment

Bluffing & Deception

Lets a player deliberately mislead other players to gain an advantage. This mechanic only works against a human, never against a computer — it's one of the most inherently "social" mechanics that exists, since it's other players' perceptions, not the game's rules, that are being deceived.

Why it works

People are constantly trying to predict others' intentions; the chance to lie or conceal intent turns a game into a psychological standoff.

Seen in games

Among Us — the strongest strategy for a deceiver isn't killing well, it's explaining actions convincingly; the most skilled players rarely lie outright, they tell partial truths and let others draw wrong conclusions.

Apply in learning

Give a group several statements, some deliberately false, and ask them to spot the errors
Run a debate where one team must defend a weak position
Use a Mafia-style game where participants analyze arguments to identify hidden roles — this trains fact-checking, not memorization

Third-Party Wagering

Several players compete for a limited resource that belongs to a third party (an auction is the classic example).

Why it works

Combines several psychological effects at once: scarcity (the reward is limited), competition (an object's value rises because others want it too), and the auction effect (people end up fighting to win, not just for the item). Behavioral economics calls the resulting overpaying the "Winner's Curse" — the desire to win outweighs a rational read of the item's value.

Seen in games

World of Warcraft's Auction House produced professional "auction traders" who barely raid and earn purely by trading and reselling.

Apply in learning

Teams bid for the right to choose the most interesting case
Participants "buy" extra hints with earned points
The best projects get a limited number of expert consultation hours, and teams decide how many of their own points to spend on it

Social Mechanics

Cooperation

Prisoner's Dilemma, Game Master, Roles, Role-Switching Groups

Prisoner's Dilemma

A situation where two participants would both be better off cooperating, but each fears the other will act selfishly. Mutual trust benefits both; if one betrays the other, the betrayer gains more while the other loses; if both betray, both end up worse off than if they'd cooperated.

Why it works

Research shows that in one-off interactions people more often choose the selfish option — but when they know they'll meet again repeatedly, cooperation becomes far more likely. This is exactly why long-term relationships matter so much for building trust.

Seen in games

The Division's Dark Zone — any ally can turn "Rogue" before extraction and kill their partners for the loot, turning every encounter with a stranger into a dilemma of trust vs. expected betrayal.

Apply in learning

Two teams independently decide whether to share useful information with each other
Participants split a shared budget between personal and team interests
Groups simultaneously choose "cooperate" or "compete" and get different outcomes depending on the combination — the real value is in the debrief afterward: why did people trust or distrust each other?

Game Master (Kriegsspiel)

Play is overseen not just by a rule set, but by a live person — a facilitator, game master, or judge. The name comes from the 19th-century Prussian wargame Kriegsspiel, designed to train officers, where the judge didn't just enforce rules but modeled events, withheld information, made judgment calls in ambiguous situations, and made the world feel more real.

Why it works

A live facilitator makes the experience less predictable — players know they're facing a person, not a lifeless algorithm, who can react to unusual decisions, improvise, create unexpected events, and adjust difficulty to the group.

Apply in learning

Run a live-facilitated case simulation rather than a fully scripted branching scenario, letting the facilitator improvise based on the group's actual decisions

Roles

Participants receive different specializations, capabilities, and responsibilities.

Why it works

People enjoy feeling indispensable — when a team's success genuinely depends on your specific action, engagement rises sharply. Roles also let people play to their own character and strengthen interdependence between teammates.

Seen in games

World of Warcraft's Tank–Healer–DPS trinity has anchored the MMO genre for over two decades. Among Us and Dead by Daylight show how giving different players fundamentally different goals turns one match into effectively two different games happening in the same space.

Apply in learning

Assign case-work roles in advance: analyst gathers information, expert assesses risk, spokesperson defends the decision, coordinator manages the process
Run a company simulation with a director, a finance lead, a marketer, and a customer role

Role-Switching Groups

Players unite into groups, but a person's role inside the group can unexpectedly change — as in Mafia, where an ordinary participant may turn out to be a hidden predator or traitor.

Why it works

The possibility of a role switching, or a hidden threat inside the group, creates a distinct kind of tension: who can be trusted? Is everyone still on the same team? The mechanic combines two powerful motives — belonging and uncertainty.

Seen in games

Project Winter — everyone starts as a team trying to survive, but hidden traitors slowly sabotage cooperation through small acts (broken generators, stolen resources, false information) rather than open conflict, so suspicion builds long before anything is confirmed.

Apply in learning

During a case, participants start on one team, then get reassigned to roles with different, sometimes conflicting, interests
A former team member becomes the project lead partway through
Some participants unexpectedly become auditors, clients, or competitors evaluating the rest

Social Mechanics

Economy

Arbitrage, Supply Chains, Public Goods, Tragedy of the Commons

Arbitrage

A player profits from a price difference for the same resource across markets, territories, or participants — buying where it's cheap, selling where it's expensive. The resource itself doesn't change, only its value in different places.

Why it works

Arbitrage gives people the feeling of spotting an opportunity others missed — the pleasure comes less from the resource itself than from the satisfaction of a good deal and a sense of competence. For many players, the hunt for a good trade becomes more interesting than actually using what they bought.

Seen in games

EVE Online — a vast universe split into regions where the same goods carry different prices, and players profit by moving resources between systems.

Apply in learning

An internal "skills market" where participants trade skills with each other
Let students "buy" expert consultations with an internal course currency
Let earned points convert into different learning opportunities whose "price" shifts with demand

Supply Chains

Value comes not just from a resource, but from delivering it from one participant to another. Players need to build reliable routes for moving goods, information, or other resources. If arbitrage answers "where's it cheaper to buy and sell," supply chains answer "how do you deliver it safely and efficiently."

Why it works

Introduces long-term planning — weighing risk, finding efficient routes, allocating resources, anticipating problems. It also creates a sense of responsibility: when a supply chain breaks, many people feel it at once.

Apply in learning

Have teams organize a "delivery" of knowledge or resources between subgroups, with reliability tracked over time

Public Goods

Several players jointly use a shared resource available to everyone.

Apply in learning

Build a collective library of useful materials, articles, and templates
Maintain a shared Q&A base that students themselves populate
Co-develop checklists, guides, or a glossary
Build a shared idea map where anyone can add their own experience

The result needs to be usable by everyone, regardless of who contributed it.

Seen in games

Death Stranding — bridges, roads, and generators built by one player become available to others, so the whole community benefits from shared infrastructure even without building it themselves.

Tragedy of the Commons

Several players share a limited common resource. If everyone acts purely in their own interest and takes as much as they can, the resource depletes and everyone ends up worse off.

Why it works

Built on the conflict between short-term and long-term gain, it forces players to negotiate, set shared rules, and enforce them.

Apply in learning

Give the whole group a shared budget of time or points that must be allocated across tasks
Teams share a limited pool of expert consultations and decide together when and how much to use
In a company simulation, departments share one budget, and one department's overspending affects everyone else

This is also a well-known economic model used to explain real problems: overfishing, deforestation, pollution, climate change — which makes it a natural fit for simulations in ecology, economics, and public policy.

Social Mechanics

Status & Recognition

Status, Self-Expression, Reputation & Influence, Exclusivity, Rituals, Trust

Status

Shows a player's standing among others — a level, rank, count of achievements, badge, or title that lets others see someone's experience, success, or contribution. Status doesn't grant a direct in-game advantage; its main value is social recognition and attention.

Why it works

Status satisfies a basic human need for recognition — when achievements become visible to others, a person gets confirmation of their own competence and significance, which reinforces intrinsic motivation. It also helps people navigate a community, since we intuitively trust someone who has already proven their experience — often status is valued even more than material rewards.

Apply in learning

Award levels or titles tied to actually mastered competencies
Mark topic experts with special badges
Use digital certificates that verify specific skills, not just course completion

Keep status tied to real knowledge and contribution — rewards that come too easily lose their value quickly.

Self-Expression

Lets a player show their individuality through appearance, behavior style, achievements, or content they've created. Historically this began as displaying status through rare accessories, but today it's much broader — character looks, profile design, class choice, play style, builds, and creative work all count.

Why it works

Self-expression satisfies a fundamental human need to be noticed and to stand out.

Seen in games

The Sims 4 and Animal Crossing are built almost entirely around self-expression — designing characters, homes, islands, and outfits.

Apply in learning

Let students customize their own profile
Give a choice of learning path or specialization
Let them present projects in their own style
Build a digital portfolio where the learner chooses which work to showcase

Reputation & Influence

How other players treat someone depends on how that person has behaved in the past. The more often a player helps others, keeps their word, or contributes to the community, the more they're trusted and the more influence they gain — a kind of social currency. Unlike status, which the system usually assigns, reputation is built by other people.

Why it works

Reputation satisfies the need for social recognition and trust — when others rate someone's actions highly, they feel significant and work to maintain that image. It also reduces uncertainty: it's easier to cooperate with someone who has already proven reliable. Good reputation gradually becomes a source of influence — people listen to, trust, and invite such people to collaborate more readily.

Seen in games

League of Legends' Honor system and Overwatch 2's Endorsements let players recognize teammates for good play, friendliness, or leadership. In EVE Online, losing the community's trust is often more costly than losing a ship.

Apply in learning

Encourage students to thank each other for useful help
Show a count of helpful answers a learner has given others
Recognize the experts classmates most often trust
Weigh contribution to shared projects, not just individual results

Reputation should track real actions, not turn into a popularity contest of likes.

Exclusivity

Access to certain items, opportunities, territories, or privileges is limited to a narrow group of players — the source of VIP clubs, rare items, closed areas, and unique rewards. The value lies less in the object itself than in the fact that not everyone can have it.

Why it works

People automatically place greater value on things that are hard to obtain — the scarcity effect: the more restricted access is, the more desirable the object becomes. Exclusivity also strengthens belonging to a select group.

Seen in games

Fortnite's season-limited cosmetics; Destiny 2's raid-exclusive rewards.

Apply in learning

Unlock extra masterclasses only after successfully finishing the course
Give top participants a chance to work on real projects
Create a closed alumni club with regular meetups and extra materials

Exclusivity disappears the moment a rare item becomes common — make it available to everyone, and it stops functioning as a symbol of special achievement.

Rituals

Brings players together through regularly repeating events, ceremonies, or traditions that mark important moments — starting or finishing a journey, gaining a new status, holidays, shared achievements, or memorable events. A ritual rarely delivers practical benefit on its own — its job is to create emotional value around the event and strengthen belonging.

Why it works

Rituals help people feel part of a community, and make achievements feel more significant — reaching a new level or finishing a hard project lands far more vividly when it's accompanied by a ceremony or congratulations. They also build traditions, which give a community its own recognizable culture.

Apply in learning

Hold a formal opening and closing for the course
Mark transitions between stages with small ceremonies or symbolic awards
Run regular community meetups where participants share wins
Build a tradition of weekly reviews, best-project showcases, or a "welcoming new mentors" moment

Trust

A player makes decisions based on how other participants have behaved in the past. The more often a person keeps promises, helps the team, and acts honestly, the more they're trusted — and trust built through direct personal interaction runs deeper than trust built through mutual acquaintances.

Why it works

Trust reduces uncertainty — knowing a partner won't let you down makes decisions easier and cooperation more likely. It also saves effort: instead of constant checking and control, people start relying on each other's reputation, which makes interaction faster and more comfortable.

Seen in games

In EVE Online, trust underlies nearly the entire economy — players hand over expensive ships and manage shared corporate finances based on it, and some alliances have lasted for years because of it.

Apply in learning

Keep students in stable teams that work together across the whole course, rather than reshuffling groups constantly
Use peer review so participants learn to give honest, constructive feedback
Assign mentors based on their past contribution to the community
Show a participant's collaboration history, so newcomers can see who's already trusted

Trust is arguably the foundation underneath most other social mechanics — trading, mentorship, teamwork, and community economies all work poorly without it.

Social Mechanics

Communities

Guilds, Guild vs Guild, Elections, Exile, Community, Strategic Guilds

Guilds

Players unite into standing communities to pursue shared goals. Inside a guild, members help each other, trade resources, train newcomers, tackle hard tasks together, and gradually build their own culture — arguably one of the most effective social structures in games, since guilds let many small social groups combine into one larger community.

Why it works

Guilds satisfy one of the most important human needs — belonging to a group. Once someone becomes part of a community, they start experiencing its successes as their own, feel responsible to other members, and want to help, join shared events, and defend their group's interests. Over time, a person starts saying "we" instead of "I." For many players, friends and guild are the main reason they keep playing, even when the game itself no longer feels fresh.

Seen in games

World of Warcraft guilds coordinate raids, resource sharing, and newcomer training, and many have existed for decades.

Apply in learning

Replace ad-hoc study groups with standing communities that exist for the whole course, or beyond it
Group students into small teams with their own name and identity
Build alumni professional communities and mutual-support groups
Run joint projects where success depends on the whole team's contribution

Guild vs Guild

Whole communities compete against each other rather than individual players — victory depends on the contribution of dozens or even thousands of participants, not one person's actions.

Why it works

Once a person identifies with a group, their motivation changes: the group's win registers as a personal win, even with a small individual contribution — a well-documented effect of social identity. Group rivalry also creates a long-term goal that can run for months, and it lowers the fear of failure, since one person's mistake no longer determines the outcome, so people take more risks and try harder things.

Seen in games

Guild Wars 2's World vs World and EVE Online's large alliance wars — many participants never fight directly, contributing instead through scouting, diplomacy, logistics, or industry; the war is won by the better-organized community, not the strongest army.

Apply in learning

Several course cohorts race to accumulate collective progress fastest
Company branches compete in a shared learning challenge scored by average team development, not top performers
An AI tutor could automatically sort students into "houses" (like Hogwarts) that earn points together over months
Compete on contribution, not speed — the team that wrote the most helpful explanations, recorded the most tutorial videos, or helped the most newcomers wins

Elections

Community members jointly decide who will represent their interests, manage resources, or make decisions on the group's behalf.

Why it works

Elections give people a sense of participating in governance, and make power visible and discussable — participants start evaluating not just personal sympathy but competence, reliability, and track record. Elections also tend to spark a whole layer of social activity around them: campaigns, coalitions, promises, and debate.

Apply in learning

Course participants vote on which case the group will discuss next
Students vote for the best projects, but must justify their choice against set criteria
A council elected within a long program represents the cohort's interests to the course team
A more interesting variant: budget delegation — the group gets a limited pool of resources and votes on what to spend it on (an expert session, project review, a practice tool, access to a materials library)

Elections work best when the decision has real consequences — a vote held purely for appearance is quickly seen through and stops being taken seriously.

Exile

The community restricts a player's access to shared resources or opportunities, or removes them from the group entirely, for breaking the rules — temporarily or permanently.

Why it works

Exclusion from a group is one of the strongest social punishments most people can face — the fear isn't really about losing in-game resources, but losing the trust, status, and relationships built over time, which is why the threat of exile is often more effective than any point penalty. It must be used carefully: if punishment feels unfair or opaque, people stop taking initiative and gradually disengage.

Apply in learning

A participant who repeatedly breaks constructive-communication norms temporarily loses the ability to comment on others' work
A student who submits AI-generated answers without review or understanding loses eligibility for the leaderboard until the task is redone
A team can vote to replace a member who's stopped contributing

More interesting than outright exclusion is recoverable trust — a participant can regain full standing after meeting certain conditions: helping other students, completing an extra module, or a successful probation period. That teaches responsibility rather than fear of punishment.

Community

The community itself becomes the main value — not any single game mechanic. At a certain point, the community holds people better than any game system, since if mechanics create a reason to show up, community becomes the reason to stay.

Why it works

It matters to people to belong to a group where they're known, valued, and expected — over time the emotional connection to the people can outweigh interest in the activity itself. A community also creates a "social home" effect: shared jokes, traditions, an internal culture, familiar faces, and a sense of safety, all of which raise engagement and lower the chance of leaving.

Apply in learning

Build a closed alumni community where the exchange of experience continues after the course ends
Run regular meetups with no lecture content — just discussion of participants' real work challenges
Let students publish their own cases and get feedback from peers, not only instructors
Grow interest-based mini-communities: UX, analytics, AI, project management
Use AI as a "connector" — recommending participants with similar problems, or automatically finding someone who already solved a similar issue

The most common mistake: assuming a course chat automatically becomes a community. A real community only forms once people actually have a reason to interact with each other.

Strategic Guilds

Communities formed not just to socialize or play together, but to reach goals no single person or small group could reach alone — requiring role division, long-term planning, coordination of large numbers of people, and effective resource management. If an ordinary guild answers "who do I play with?", a strategic guild answers "how do we organize hundreds of people around a shared goal?"

Why it works

Once a task grows too large for one person, specialization becomes necessary and people start choosing roles that fit their strengths, producing an effect of collective competence — success stops depending on the single most talented person and depends instead on how well the whole system is organized.

Seen in games

EVE Online's largest alliances run tens of thousands of players like real organizations — with combat units alongside finance, intelligence, diplomacy, logistics, industry, HR, and even a training division, with some operations planned for weeks and involving hundreds of players.

Apply in learning

Participants build their own learning communities and split roles: moderator, expert, event organizer, digest author, mentor for newcomers
In a corporate academy, different departments each own a piece of a shared knowledge base
An AI system automatically analyzes participants' skills and suggests the roles where they'd add the most value

The most interesting version of this: participants don't just take a course, they build the learning ecosystem — writing instructions, reviewing materials, running webinars, designing tasks, and improving the program, so the community's value grows with every new cohort.

Social Mechanics

Content Creation & Misuse

User-Generated Content, Griefing

User-Generated Content

Players create part of the content themselves rather than only consuming what the developers built — new levels, maps, scenarios, characters, mods, items, or entire game modes. Developers build the tools; users fill the game with new content.

Why it works

People care not only about receiving a finished result but about creating something themselves — when people invest their own effort into making something, they value it far more, producing a sense of authorship and personal stake. Creating content also lets people express individuality, get recognized by others, and feel significant within a community.

Seen in games

Minecraft and Roblox — most games inside Roblox were built by players themselves, who become designers and organizers of their own projects. Super Mario Maker gives players tools to build and share their own levels.

Apply in learning

Have students build their own case study on the topic being studied
Have them create a quiz for the next cohort
Record a short explainer video
Prepare a checklist, cheat sheet, or infographic
Build a shared collection of best solutions or useful materials

The most common mistake: assuming only instructors should create learning content. Assignments where participants become authors themselves tend to drive far more engagement.

Griefing

A player deliberately interferes with other players' enjoyment — sabotaging teammates, destroying builds, blocking progress, stealing resources, provoking others, or abusing game systems to hurt other participants. Considered negative, but it appears in nearly any multiplayer game with enough freedom of action, so designers have to account for it.

Why it works (for the griefer)

Some players enjoy influencing others' emotions, not just their own achievements — for some, it becomes a way to assert power, demonstrate control, or get attention. Griefing tends to appear wherever destructive behavior carries no real consequences; if punishment is minimal or absent, some users start testing the limits.

Apply in learning — design against it, don't reproduce it

Build in protection against sabotage when designing team assignments
Use peer evaluation to distribute accountability across the team
Keep a change log for shared/collaborative projects
Set interaction and conflict-resolution rules up front
With AI tools, monitor collaboration history to flag uneven participation early

Don't port the mechanic itself into a learning product — treat it as a behavior pattern the design needs to be resilient to.

Preview

This type isn't built in the demo yet

Content is ready in your Course Architecture Library — once you approve this layout, every remaining type gets built the same way.