Having Freedom to Choose: What D&D Teaches Us About Autonomy

Any long term readers (all three of you) of this blog know that I I love finding parallels between Dungeons & Dragons and teams in the workplace. This is not because adventuring parties are particularly effective organisations. Rather, a group of players all representing characters with different skills, goals and outlooks all come together to beat a common goal. Remarkably similar to teams in the real world. Something that drives both the players of the game and team mates at work is autonomy.

In game players have the freedom to decide what their characters do. Of course, those decisions should matter. It is not at all surprising that the same principle sits at the heart of creating a motivated and engaged workplace.

Autonomy is more than freedom

In his book Drive, Daniel Pink identifies three key elements that underpin motivation in modern workplaces: autonomy, mastery and purpose. Autonomy is the desire to have some control over what we do, how we do it, and sometimes when we do it. It doesn’t mean everyone gets to do whatever they want. A workplace without structure would quickly descend into something resembling a badly managed D&D campaign. Everyone would have their own objectives, nobody would know what anyone else was doing, and the person responsible for payroll would probably be hiding in the woods.

Autonomy exists within boundaries.

A D&D game has rules, a setting, a Dungeon Master, a scenario and consequences. Players aren’t free to rewrite reality whenever they want. But within those boundaries, they should have enormous freedom.

The DM might tell the players:

“You have arrived at the gates of the marble city.”

What happens next is up to them. They might walk brazenly through the gate. Or perhaps they sneak in through the sewers at night. Of course, they might decide the city is clearly too dangerous and wander off in completely the opposite direction. The important thing isn’t that the players get everything they want. It’s that they get to choose.

Choices need consequences

I’ve gone into this in more detail in my previous article and I don’t want to cover the same ground. But there is an important distinction between giving people choices and giving people meaningful choices. Railroading is taken badly by the roleplaying community for a reason.

At work we can ask employees for their opinions, run surveys, hold meetings and invite suggestions. But if every decision has already been made, people quickly learn that their participation is decorative only. Autonomy requires more than asking people what they think.

People need to believe that their decisions can change something. That doesn’t mean every suggestion must be accepted. Just as the DM doesn’t have to allow every player plan to succeed, managers can’t accommodate every idea. But when someone makes a decision, we should be able to explain why it mattered.

The D&D player needs agency

Lets consider two different D&D games. In the first, the DM has written an elaborate story. The players are expected to follow the plot from A to B to C. They meet the NPC the DM has prepared, discover the clue the DM wants them to discover, travel to the location the DM has selected and fight the villain waiting there. While the adventure might be beautifully written the players can begin to feel like passengers.

In the second game, the DM establishes a world, creates problems and introduces characters with their own motivations. Then the players decide what they want to do. The DM responds to those decisions. The players might ignore the obvious villain and become obsessed with helping a farmer recover a stolen cow. They might make friends with the Sheriff who was supposed to be an antagonist. Instead of entering the carefully prepared dungeon they might go straight to the castle, because they found another way to deal with the evil necromancer.

For the DM, this can be terrifying. However, for the players, it can be fantastic. Because now the story belongs to them too. Their choices shape what happens next. That is agency. One of the great pleasures of roleplaying games.

The workplace needs agency too

Lets look at a workplace that gives people responsibility without giving them control.

  • “You’re responsible for delivering this project, but I’ll decide how you do it.”
  • “I want you to take ownership, but please run every decision past me.”
  • “I’d like you to develop professionally, but here’s exactly what you’re going to work on.”

These approaches can create accountability without autonomy which eventually leads to people feeling like they don’t own their work. Instead, they become characters following someone else’s adventure path.

A more autonomous approach might sound like:

“Here’s the outcome we need. Here’s the timeframe and the constraints. How would you approach it?”

Now the employee has something to solve. They can bring their expertise to the problem and make their own decisions. Of course, by doing so they can learn from the consequences.

That is much closer to playing a great game of D&D.

The DM doesn’t disappear

Now, beware, because there is a trap here. If autonomy is so good, it can be tempting to conclude that managers should simply get out of everyone’s way. But that’s not what autonomy means.

The DM still has a critical role. They establish the world, create challenges, introduce consequences and maintain the rules. On occasion they have to tell the players, “No, your wizard cannot summon an ancient dragon just because you rolled a natural 20.”

Good managers do much the same. They establish expectations and boundaries, while providing resources and support. Where possible they help remove obstacles and make sure people understand both the objective and the constraints.

Ultimately, they allow people to decide how to get there. The skill is knowing when to intervene and when to let the players play.

Autonomy creates ownership

One of the most interesting things about D&D is how quickly players become invested in decisions they have made themselves.

If the DM tells the party that they must defeat the corrupt town mayor, the players may care. But if the players decide that the mayor needs to be brought down because of the way he’s been bullying their characters families, the objective becomes personal. They are fully invested.

Of course, the same thing happens at work. People are more likely to feel ownership over an outcome when they have had a genuine role in determining how they will achieve it. Telling the team “We need to deliver this project by the end of the month, within this budget, while meeting these quality and safety requirements,” creates the playing field. the team then decide how to play the game. That’s autonomy.

Failure is part of autonomy

There is one final lesson that D&D offers us. If players are genuinely making decisions, sometimes they are going to make bad ones. They will open the trapped chest (there might be treasure inside…) or split the party (haven’t horror movies taught us anything?). Sometimes they will charge the ancient green dragon head on.

If we want to create autonomy for our teams at work, we have to accept the same reality. People will make mistakes. The answer isn’t to remove their ability to make decisions. Doing so creates a workplace where the safest strategy is to ask permission for everything.

Instead, we should distinguish between acceptable failure and unacceptable failure. A junior employee making a poor judgement call on a low-risk task can be an opportunity for learning. A decision that creates a serious safety risk is completely different.

Boundaries do matter. Within those boundaries, however, people need enough freedom to experiment and develop their judgement.

That’s how mastery develops too. And Pink’s three elements begin to connect.

  • Autonomy gives people the opportunity to choose.
  • Mastery gives them the opportunity to get better.
  • Purpose gives them a reason to care.

Let the players play

When thinking about autonomy, perhaps the biggest lesson D&D offers managers is surprisingly simple: Don’t write the players’ story for them. Give them the objective and resources. Explain the boundaries before letting them decide what to do.

The same is true at work. If we want people to take ownership, solve problems creatively and become more capable, we need to give them opportunities to exercise judgement.

We need to move from: “Here’s what I want you to do.” towards: “Here’s what we’re trying to achieve. How do you think we should do it?” That small change can transform the relationship between a manager and an employee. One makes someone a participant. The other makes them an owner.

Perhaps that is why D&D continues to be such a useful mirror for the workplace. The best games aren’t about the Dungeon Master telling everyone what happens. They’re about creating a world where people’s choices matter.

The best workplaces aren’t either.

How to Write Engaging Game Scenarios That Fit a Tight Schedule

One of the biggest challenges when using roleplaying games in workplace settings is time. At home, a roleplaying session can happily sprawl across an entire afternoon or evening. Players chat about their week, argue with goblins for forty minutes, and somehow spend half the session buying rope. Conference environments are very different creatures entirely and run to an extremely tight schedule. Sessions need to start quickly, engage immediately, and conclude cleanly before attendees disappear into the next keynote presentation.

I have been asked to run a series of games for a communication conference in 2027 (I’ll post more details closer tot he time). There will be four sessions over two days, each 75 minutes long. The idea is to showcase how roleplaying games can help foster communication and develop leadership skills. Now I love playing short one shots, but they normally take a minimum of 3 hours. So, I have an interesting challenge: write two engaging scenarios that show case the player interaction and can be wrapped up with a debrief in one hour. Easy, right… right…

Rules

While I love D&D, Call of Cthulhu and others, they do contain pretty heavy rulesets. I will also be working under the assumption that none of the conference attendees will have any experience playing roleplaying games. Consequently, using an established ruleset is going to have too high of a learning curve.

In order for the players to get into the game quickly I’m going to use my own ruleset Play2Lead. Easy to learn in a couple of minutes participants should be able to get into the action straight away. In a similar vein there will be no character creation, rather pre generated characters will be provided for each scenario, with clear roles.

The Three Encounter Structure

I’ve written before about designing workplace scenarios before and i intend to follow the same design principles. As such each of these scenarios will a simple three encounter structure that I use for one-shots:

  1. Cold Open: Throw players straight into action—explosions, monsters, a chase. Skip the slow build.
  2. Middle Twist: Add a big revelation that flips the situation on its head.
  3. Final Showdown: End with a bang. The danger should feel real, and not everyone has to make it out alive. If possible add a difficult dilemma for the players to work through.

That’s all we have time for.

This structure creates momentum. Players immediately understand there is a clear objective and limited time to achieve it. As first-time players it’s important that they feel comfortable so they can quickly grasp the rhythm of the game.

Perhaps most importantly, it leaves room for some roleplay without letting the session drift into the wastes of overlong decision-making.

Why Familiar Genres Matter

One thing I’ve learned over years of introducing new players to RPGs is that unfamiliar rules are far less intimidating when wrapped inside familiar stories. People already understand the language of popular movies. They know how zombie survivors behave. The tension of an alien horror film is obvious. They instinctively grasp the heroic structure of fantasy quests. Of course, this means you can skip enormous amounts of explanation.

Nobody needs a twenty-minute briefing to understand: “Something is hunting us on this spaceship.” Or: “The dead are rising and we need to escape.”

The tropes do the heavy lifting for you. Players arrive with expectations already loaded into their brains like pre-installed software, allowing them to engage almost immediately.

As such my intention is to design my scenarios around popular movies. My initial thinking is Alien, Zombies and potentially a Lord of the Rings inspired one, this is roleplaying after all.

Everyone loves a good allien.

First Thoughts on an Alien Inspiration

Science fiction horror works beautifully in short-form workplace games because the pressure is immediate and constant. Everyone can visualise the close industrial tunnels of these types of film. The players can get straight into the game without much in the way of explanation.

Characters

The pre-generated characters for this session will include standard tropes: captain, engineer, science officer, medic, pilot each with a specific skill and piece of equipment.

Encounter One: The Distress Signal

Straight into the action, the crew of a salvage vessel begin by investigating a damaged research station after receiving a fragmented distress call. The station is mostly abandoned, lights flickering, alarms sounding intermittently, and signs of violence scattered throughout the corridors. The players must find the generator and restore power to the engines. What has caused such chaos?

Suddenly the hull will breach and the players need to work together to secure it, quickly. A nice bit of urgency right from the get go.

Encounter Two: Something is Loose

Now for the middle twist, although probably not unexpected given the theme. As the team explores deeper into the facility, they discover evidence of a hostile lifeform. Slime, scratch marks etc. Communications fail. The creature begins stalking them through vents, maintenance tunnels, and darkened laboratories.

Players must talk in whispers, or communicate through note or face attack from the creature. The scenario becomes about teamwork, communication, and managing panic under pressure.

Encounter Three: Escape

The players discover the only way out is aboard a damaged shuttle with limited seats and a failing reactor countdown. They must choose between rescuing survivors, destroying the station, or simply escaping alive. A very juicy dilemma!

This final encounter creates fantastic workplace discussions around leadership, decision-making, and competing priorities.

Keep It Simple, Keep It to a Tight Schedule

The key to designing this sort of adventure is that simplicity creates engagement.

Conference attendees do not need twenty pages of backstory and complicated rules.

They need:

  • A clear objective
  • Recognisable tropes
  • Immediate problems
  • Interesting decisions
  • A chance to contribute

That’s what creates memorable sessions.

Over the next few months I’ll be refining the design for 2-3 scenarios and sharing my thinking here.

But what i really want is to give those conference attendees signing up for my games to leave with a fun memory having experienced something different. And i hope the realisation that RPGs can be used as a fun way to practice both communication and leadership.

Particularly the bit where Dave from HR sacrificed himself to the space monster while screaming into a malfunctioning flamethrower.

Why Hero Leadership Really Fails

There’s a particular story we love to tell about leadership.

One person stands at the front. They have the answers. When things go wrong, they step forward, make the hard call, and save the day. The team rallies. The credits roll.

It’s a great story. It’s just a terrible way to run a Dungeons & Dragons party… or any other organisation.

The Myth of the Hero Leader

Hero leadership is built on a simple idea: progress depends on a single exceptional individual. The hero leader is decisive, charismatic, endlessly capable. When the dragon appears or the quarterly results dip, they draw their sword (or pen) and fix it.

In D&D, this often shows up as the “main character” syndrome. One player dominates planning, talks to every NPC, solves every puzzle, and lands the killing blow. The rest of the party becomes a supporting cast, present but rarely essential.

In business, the same pattern plays out with the superstar manager or visionary executive. Decisions funnel upward. Problems wait for approval. Success is attributed to one person rather than the system around them.

In both cases, things may appear to work… for a while.

What Actually Happens at the Table

At a D&D table, hero leadership creates subtle damage long before it causes a wipe. Other players disengage. Why contribute if the paladin always decides the plan? Why risk a creative idea if the wizard will override it? The game becomes quieter, flatter, less surprising.

Worse still, the party becomes fragile. When the hero is absent, stunned, or simply wrong, everything collapses. A single failed saving throw can derail the entire session. D&D is designed around distributed competence. Different characters shine in different moments. When one player tries to carry the whole narrative, the system pushes back, usually with teeth.

The Workplace Version Is No Kinder

Hero leadership in business produces similar cracks. Teams stop thinking ahead. People wait to be told what to do. Initiative dries up, not because people lack ideas, but because they’ve learned those ideas won’t be used.

Decision bottlenecks form. The “hero” becomes exhausted, then indispensable, then overwhelmed. When they finally step away, the organisation discovers it hasn’t been developing leaders at all, only dependencies.

The scariest part? It often looks like success right up until it doesn’t.

Heroes Don’t Scale

A single hero can slay a goblin. They cannot sustainably run a campaign. Both D&D parties and businesses face complexity, uncertainty, and problems no one person can fully understand. Trying to centralise leadership in one figure reduces the system’s ability to adapt.

When leadership is shared, something different happens. People take ownership of their piece of the problem. Information flows faster. Mistakes are caught earlier. Success belongs to the group, not the loudest voice.

In D&D, this is when the rogue scouts ahead without being told, the cleric speaks up about risk, and the fighter suggests a plan that isn’t “kick in the door.”

In business, it’s when team members make decisions within their remit and feel safe doing so.

The Real Alternative Isn’t Leaderless Chaos

Rejecting hero leadership doesn’t mean abandoning leadership altogether.

It means shifting from “the leader has all the answers” to “the leader creates the conditions for good answers to emerge.”

In D&D, the best leaders are often the ones who ask questions:
“What do you think?”
“Who hasn’t spoken yet?”
“What’s another way this could go wrong?”

In business, strong leaders do the same thing. They clarify intent, set boundaries, and trust their teams to act within them. They step forward when needed and step back just as often.

Shared Leadership Creates Better Stories

The irony is that hero leadership actually makes for worse stories.

The most memorable D&D moments rarely come from flawless heroes. They come from messy plans, unexpected teamwork, and someone stepping up who wasn’t supposed to be the star. The same is true in organisations. The strongest cultures aren’t built around legendary individuals, but around teams who know how to think and work together under pressure.

If you want a campaign that lasts, or a business that survives its own success, retire the hero.

Build the party instead.

Dealing with a Lone Wolf Player in D&D and Business

We all know that in both Dungeons & Dragons (D&D) and the workplace, teamwork is essential for success. However, every group occasionally encounters a lone wolf—an individual who prefers to act independently rather than collaborate with the team. While independence can be a valuable trait in certain situations, a lone wolf’s behavior can be detrimental when it disrupts group cohesion, communication, and shared objectives. If left unchecked, a lone wolf can cause irreparable damage to a business or group.

What Is a Lone Wolf and Why Is It Detrimental?

A lone wolf is a player or employee who operates primarily on their own, often avoiding teamwork, disregarding group plans, and making decisions without consulting others. In D&D, this could be a character sneaking off to loot treasure without the party, or a player who constantly ignores group discussions in favor of their own agenda. In business, a lone wolf might be an employee who works in isolation, hoards information, doesn’t follow process or fails to engage in team projects.

Often individually a lone wolf can be successful. For example make great sales, or make a great in game fighter. However, their unwillingness to collaborate can cause significant issues, including:

  • Lack of synergy: The group is forced to work around the individual rather than integrating them into team efforts.
  • Poor communication: Important details are missed because the lone wolf operates separately.
  • Reduced trust: Team members may feel frustrated or disconnected when the individual ignores their input.
  • Lower efficiency: The group wastes time resolving conflicts instead of focusing on their shared goals.

Strategies for Dealing with a Lone Wolf in D&D

As a Dungeon Master, your goal is to balance individual player agency with team cohesion. Here are some ways to handle a lone wolf player effectively:

  1. Understand Their Motivation – Talk to the player to understand why they prefer to work alone. Are they roleplaying a specific character concept, or do they simply dislike group decision-making?
  2. Encourage Group Decision-Making – Implement moments where cooperation is necessary, such as puzzles, multi-step combat strategies, or social encounters requiring group input.
  3. Use Narrative Consequences – If the lone wolf consistently acts against the party’s interests, have the world react accordingly. NPCs may become untrusting, or the character may face in-game consequences for their isolationist behavior.
  4. Set Clear Expectations – Before the game, establish that D&D is a cooperative experience and that all players should engage with the group’s decisions.

Strategies for Dealing with a Lone Wolf in Business

Managing a lone wolf employee requires a balance of respecting their independence while ensuring they contribute to the team’s success. Here’s how leaders can address this behavior:

  1. Identify the Root Cause – Is the employee avoiding teamwork due to a lack of trust, unclear expectations, or personal preference? Understanding their reasoning helps tailor your approach.
  2. Encourage Open Communication – Lone wolves may not realize how their actions impact the team. Provide regular feedback and encourage dialogue to align them with team goals.
  3. Assign Team-Oriented Tasks – Give them projects that require collaboration, emphasizing shared success over individual achievement.
  4. Create Accountability – Ensure that responsibilities are clearly defined and that the lone wolf must provide updates and integrate their work with the team’s efforts.

Final Thoughts

While implementing the strategies above should bring a lone wolf around to integrating more with the team, there will be instances where they will refuse to do so. If this is the case and their behavior is having a detrimental impact on the team then you should seriously consider asking them to leave the gaming group. Or, in the case of a workplace begin enacting performance management. However, DMs and leaders alike can turn a lone wolf into a valuable team player. Whether in fantasy or the workplace, the best adventures—and successes—are built on cooperation.

Team Building Through Shared Storytelling — Why D&D Might Be the Ultimate Trust Exercise

When people think about team building, they often picture ropes courses, awkward icebreakers, or nerve-wracking trust falls. But what if the most powerful tool for creating real team cohesion wasn’t physical activity or corporate exercises—but storytelling? Enter Dungeons & Dragons, a tabletop roleplaying game that thrives on shared storytelling. It’s a game where players build imaginary worlds together, solve problems as a group, and embody characters who grow, struggle, and triumph as a team. And while it might look like fantasy fun (and of course it is), D&D also offers a surprisingly deep model for how to build strong, psychologically safe, high-performing teams.

Let’s look at how D&D’s narrative structure creates team bonds—and how you can use these lessons in your workplace, classroom, or community group.

Shared Storytelling = Shared Ownership

In D&D, the story doesn’t belong to one person. Sure, the Dungeon Master (DM) might guide the world, but the plot evolves through the choices of everyone at the table. Players decide how to approach challenges, who to trust, and what kind of characters (or leaders) they want to become.

That shared narrative builds shared ownership. When a mission succeeds, the whole group feels it. When things go wrong (and they almost always do), the group adapts together. This sense of co-authorship is powerful: it creates a team culture where every voice matters.

In the workplace, this mirrors the difference between top-down directives and collaborative strategy. When the story is presented from the top, buy in can meet significant resistance. However, when team members help shape the story—of a product, a project, or a goal—they’re more invested, more creative, and much more committed.

Psychological Safety: Failure Is Part of the Game

One of the greatest strengths of D&D is how it normalizes failure. Characters miss attacks, fall into traps, or make poor decisions—and the story doesn’t end. It gets significantly more interesting. The consequences of failure become narrative fuel, not a source of shame.

This culture of playful risk-taking builds what Google’s research famously identified as the #1 trait of high-performing teams: psychological safety. In a psychologically safe team, people feel comfortable speaking up, taking risks, and being vulnerable without fear of ridicule or retribution. By playing D&D together, teams rehearse this kind of safety in a low-stakes setting. They learn that mistakes aren’t fatal—they’re part of the fun. And that mindset carries over into real work.

Building Empathy Through Character

In D&D, players take on personas that often differ wildly from their real-world identities. A quiet analyst might play a boisterous half-orc bard. An outspoken manager might become a timid elven healer. As they explore these characters, players inhabit new perspectives—and watch their teammates do the same.

This roleplaying builds empathy. It invites players to step into someone else’s shoes (or boots, or hooves), wrestle with emotional dilemmas, and support each other’s fictional struggles. And in doing so, it strengthens their emotional intelligence in real life.

Empathy isn’t a soft skill—it’s a critical leadership trait. D&D gives teams a safe way to build it naturally, through play.

Tips for Encouraging Shared Storytelling

You don’t need to be a master Dungeon Master to encourage better storytelling in your game. If you are running a game at work or using roleplaying to help impart experiential learning, consider using these tools to deepen the shared storytelling experience:

1. Paint the Scene Questions

Instead of describing everything yourself, invite players to contribute. Ask things like:

  • “What does the ruined temple smell like?”
  • “What’s the one thing about this town that makes it feel like home?”
  • “What do you see on the battlefield that makes you hesitate?”

These questions invite creativity, distribute narrative control, and reinforce the idea that this world belongs to everyone.

2. Ask for Flashbacks

Let players add history to the world:

  • “What memory does this cave bring back?”
  • “Tell us about the last time you faced something like this.”

Flashbacks connect characters more deeply to the story and build emotional investment.

3. Spotlight Sharing

Make space for each player to shine. Don’t let loud voices dominate the session. Encourage quieter players by giving them openings:

  • “Hey, Mira, what does your character think of this?”
  • “You’ve been watching from the shadows—what do you notice?”

4. Celebrate Narrative Wins, Not Just Combat

Don’t let the game revolve around dice rolls alone. Praise creative problem-solving, emotional roleplay, and team synergy as much as battle strategy.

5. De-brief After the Game

After each session, take a few minutes to reflect:

  • “What was your favourite moment tonight?”
  • “What surprised you?”
  • “What do you think your character learned?”

This builds reflection and reinforces shared memory—essential for team bonding.

Every Team Has a Story

Your team already has a story. The question is: are you telling it together, or is it being written without them? Dungeons & Dragons shows us that the act of co-creating a story builds connection, empathy, and trust. Whether you’re sitting around a game table or a boardroom, the principle holds: when people feel seen, heard, and included in the narrative, they give their best.

So maybe next time you’re planning a team-building session, skip the ropes course. Grab some dice. Sit around a table. And start telling a story—together.