'No' is the most interesting answer.
The tyranny of yes.
There’s a lot of talk in the ttrpg world about ideas like ‘yes, and’, ‘no, but’, and similar improv-style narrative scaffolding techniques. All of this is often in fear of the simple ‘no’. I love ‘no’. I think it’s the most important response a GM has in their toolkit, despite what a lot of discourse says. Here’s why.
A quick disclaimer: If you like the ‘‘yes, and’/‘no, but’ school of thought that is absolutely fine! But I think we need more advocates for ‘no’, hence this piece.
In fiction
The hobbits ask the GM if they could kill a Nazgûl. “No.” This makes, the Nazgûl fascinating. Plus, restrictions lead to creativity: the hobbits must deal with them in a different way. They cannot ‘beat’ them.
Imagine if in LOTR Gollum had told the hobbits “yes actually, if you just find (insert magical relic here), precious, then you can kill a Nazgûl!” or “No, but you can trap them with a magic circle!”
The magic is gone. The world is less interesting. The Nazgûl are less interesting. The hobbits’ relationship with them is less interesting.
The need for ‘yes’ / ‘yes, and’ / ‘yes, but’ / ‘no, but’ comes from the hero’s journey and in some senses, the colonial roots of D&D’s wargaming heritage. There is an idea that all challenges should be things the PCs can conquer either now or in time, once they have accumulated enough ‘power’.
The name of the game is dominance and player character importance. It’s about the world yielding to you, rather than ever entertaining the reverse.
Contrary to what many seem to believe, ‘no’ is often the biggest point of drama in many stories. In A Wizard of Earthsea, Ged cannot control the shadow he unleashes whilst meddling as a young apprentice and it scars him forever. He tried to do something beyond his capability and was told ‘no’. He paid a dire cost for his mistake and he didn’t get a consolation prize either.
In Game of Thrones, Ned ~why did I choose Ned as an example after Ged, well we’re here now~ tries to be an honourable Hand of the King in a system ridden with corruption. He is told ‘no’ by the establishment, and ends up dead for it.
Fantasy worlds especially are defined more so by what characters cannot do than what they can. Think about it. If the author says yes to every character’s whim e.g. “I want to be able to fly” quickly, we have chaos and something that doesn’t act as a lens for the human experience.
Limitations define challenges, and challenges are drama.
Impassable challenges are the biggest drama, especially because they represent the truth of reality: there are somethings that cannot be overcome.
Sci-fi is no different. We might be able to travel faster than light, but we still can’t raise the dead. ‘No’ is critical for worldbuilding. It is essential for making the imagined feel real.
Fear of ‘no’
I think people are afraid of ‘no’ in TTRPGs for a few reasons.
They worry that the session will grind to a halt. This is really a miscalculation from my perspective. Saying no doesn’t mean players can’t think of a better approach, take a different path, or that the random encounter die isn’t about to make their day even worse/more interesting.
To me, a GM saying ‘no’ is fantastic: it tells me to be more creative, more calculating, to sweat for results, or to explore in a different direction because this genuinely is something I can’t conquer. It is BORING being told yes constantly. Many of us who are gaming are adults: we should be able to process ‘no’ in a game.
Another reason is that ‘no’ can seem like a confrontational answer. I think this is a social problem more than anything. If at your game table the GM saying ‘no’ to a player isn’t something that is a respected answer, you’ve got a table culture problem that needs addressing.
There can be a fear of squashing player creativity. Sure, if you say no to everything. But I think setting boundaries on what a player can be creative within is a crucial part of building consistent fiction and immersion at the table. Again, we’re grown-ups. We can work together to calibrate what it possible in the game world and what isn’t.
The last is narrative expectations. The colonial roots of D&D and the hero’s journey enforce an expectation that conquering is success, and not doing so is failure. There is an implicit idea of win conditions, and winning means bending the world to your whim.
Failure is not losing. Failure is interesting. For creating a real-world analogue, ‘no’ is critical. We get told ‘no’ all the time in the real world, and it forces us to make interesting choices.
Perhaps that’s part of this symptom of anti-‘no’. People want to escape that aspect of the real world. But trust me: the best stories revolve around significant ‘no’ moments. If you embrace the hard ‘no’ as part of TTRPGs, your games will get much more interesting. You become unchained from the hero’s journey, and can explore a plethora of narratives outside the confines of that narrow scope.
Caveat: Obviously if the GM says no to everything, that’s boring. It’s important to embrace player creativity. But I’m not telling you to say no to everything, but to say no when it’s interesting (because it often is).




It's like my parents used to say: "No means no" 😳
Yesterday, I had my first session for Tales from Trinity City.
One of my players has Shurkien to throw, and asked — can I throw four of them at the punks in front of them.
I said, you don’t have the skill, you throw with disadvantage.
He asked, if I throw less, can I throw normally.
I said, no, you don’t have marksmanship: Ninja Star skill, so you throw at disadvantage if you throw more than 1.
There was silence for 30 seconds.
He said, to hell with it, I’m rolling.
Four punks got hit.
You’re right, no adds to the fun, because it adds drama, which is the reason we play!
Drama, fun, and friction!