Teaching Organizational Behavior and HRM with Simulation Games

A simulation lets students feel the trade-offs that OB and HRM theories describe. But the learning is made in the debrief, not the game. Here is how to teach with one well.

Why simulations work where lectures struggle

Organizational behavior and HRM are applied disciplines — they are about judgement under competing pressures, not facts to recall. A lecture can describe the tension between short-term results and long-term culture; a simulation makes a student feel it when their cost-cutting decision quietly erodes engagement three turns later. Experiential learning theory (Kolb) explains the mechanism: we learn deeply by acting, observing consequences, reflecting, and then generalising. A simulation supplies the action and consequence; your teaching supplies the reflection and generalisation.

Choose the concepts the simulation should teach

Don't run a sim for its own sake. Decide first which two or three concepts it should illuminate — leadership style and its effect on morale, the trade-off between control and autonomy, how culture compounds from small decisions, the lagged consequences of HR choices. Brief students on those concepts beforehand so the game becomes a test of ideas they have just met, not a random experience.

Integrate it into the course, don't bolt it on

• Before: teach the relevant theory, then set the simulation as the application.
• During: have students record why they made key decisions, not just what they chose. The reasoning is the assessable learning.
• After: debrief, then connect explicitly back to the theory and, if you wish, to an assessment.

A simulation referenced once and never revisited teaches little; one woven into the week's theory and assessment teaches a lot.

The debrief is where learning happens

This is the single most important — and most skipped — step. A structured debrief turns an experience into understanding. A reliable sequence:

• What happened? Surface the facts: what decisions students made and what outcomes followed.
• Why did it happen? Connect outcomes to mechanisms — which decision drove the engagement drop, and why.
• So what? Link to theory: "this is exactly what [theory] predicts; here is the concept."
• Now what? Generalise: what would you do differently as a real manager, and where does this apply beyond the game?

A tool like TeachWall works well here — have students post their biggest surprise from the simulation, then theme the responses live to anchor the debrief in their own experience.

Handle competition and emotion

Simulations can get competitive, which raises engagement but can also raise defensiveness when decisions go badly. Frame ‘failure’ as data: a poor outcome is the most instructive result, because it makes a consequence visible. Make it safe to have managed badly in a game — that safety is exactly what lets students take the risks that teach.

Assess the reasoning, not the score

If you assess a simulation, grade the quality of students' reflection and their links to theory, not their in-game score. A student who managed poorly but analyses precisely why has learned more than one who won by luck and cannot explain it. A short reflective memo connecting their decisions to course concepts is a strong, hard-to-fake assessment.

Final thought

A simulation is a generator of experience; you are the one who turns experience into understanding. Pick the concepts deliberately, integrate the game into theory and assessment, and above all run a real debrief. OrgLife gives students the decisions and consequences — the debrief is where it becomes learning.