Thursday night. The table's covered in character sheets and dice and half-empty cans of Guayaki. I've spent three hours prepping a space station encounter for our Mothership campaign. Deck maps. NPC motivations. A corporate conspiracy that I'm genuinely proud of, the kind that unfolds like origami if the players pull the right thread.
They don't pull the thread.
They sell the ship. The ship I designed the entire scenario around. They sell it to a scrap dealer I improvised thirty seconds ago and use the money to buy passage on a freighter heading in the opposite direction of everything I planned.
And this is the moment, right here, where game mastering and leadership are the same discipline.
A bad DM panics. Railroads the players back onto the plot. Puts up invisible walls. Makes the scrap dealer refuse the sale for some contrived reason. You can always tell when a DM is railroading because the world stops making sense in small ways. Doors that should open don't. NPCs who should have their own agendas suddenly all want the same thing. The universe becomes a hallway with the illusion of rooms.
A bad leader does the same thing. They build a plan, fall in love with the plan, and then spend all their energy forcing reality to match the plan instead of updating the plan to match reality. The team can always tell. The same way players can tell. Because the world stops making sense in small ways. Decisions that should be theirs aren't. Options that should exist don't. The company becomes a hallway.
Here's what Mothership teaches you that most leadership books won't.
Mothership has a panic mechanic. Every time something goes wrong, you roll on a panic table. Your character might freeze. Might scream. Might fire their weapon at the nearest moving thing. The panic isn't a failure state. It's a feature. It's the game telling you: humans don't perform optimally under stress, and pretending otherwise is a lie.
In business, we pretend panic can be eliminated. We build processes to remove it. Contingency plans for the contingency plans. But the panic is still there. It's in the founder's gut when the biggest client goes quiet. It's in the team's eyes when the strategy shifts for the third time in a quarter. And the leaders who acknowledge it, who say "yeah, this is scary, let's figure it out together," are the ones whose teams don't freeze.★ Because naming the thing is what keeps it from owning you.
Last month one of my players, a marine class character, rolled panic during a firefight and got "combat freeze." Couldn't act for two rounds. The rest of the team didn't leave him. They pulled him behind cover, gave him time, and adapted their tactics around a gap in their formation. Nobody told them to do that. The game made space for it and they filled the space with something better than my plot ever would have been.
That's what good teams do when you let them.
The "yes, and" principle from improv shows up in game mastering constantly, but the version that matters most for leadership is the one nobody talks about: knowing when "yes, and" becomes "yes, but."★
"Yes, you can sell the ship. But the scrap dealer has connections to the syndicate you've been avoiding, and now they know what you look like."
That's not blocking. That's consequences. A good DM doesn't say no. A good DM says yes and then makes the yes interesting. A good leader does the same thing. When someone on the team has an idea that's sideways from the strategy, the answer isn't no. The answer is: here's what that would mean, here are the constraints it creates, now you decide.
The constraints are the creative engine. Mothership gives you a d10 stress die and a panic table and limited ammunition and a ship that's falling apart. And inside those constraints, my players have done things I never would have imagined. They've solved problems I didn't know were solvable. They've built alliances with NPCs I created as throwaway encounters. They've made the game better than anything I could have authored alone.
Thursday nights remind me of something I keep forgetting during the work week: preparation is not the same as control. I prep for three hours so that I can improvise for four. The prep isn't the product. The prep is the foundation that lets me respond to whatever actually happens instead of whatever I thought would happen.
I run Vampire: The Masquerade sometimes too. Different game. Same lesson. In Vampire, the players are monsters trying to hold onto their humanity. Every session is a negotiation between what they want and what they're becoming. The Storyteller's job isn't to judge that negotiation. It's to make it vivid. To put them in rooms where the tension between desire and conscience has nowhere to hide.
Replace "monsters" with "founders" and "humanity" with "the reason they started the company" and you've got every client relationship I've ever had.
The game isn't the plan. The game is what happens when the plan meets the table. And the best DMs, the best leaders, the best people to work with, are the ones who built something sturdy enough to survive contact with reality and loose enough to become something nobody expected.
My players sold the ship last Thursday. The campaign is better for it. I just didn't know that until they showed me.