How to Get Quiet D&D Players to Participate More

Watch or listen to this blog post here.

Have you ever had a game where one player was doing almost all the talking while everyone else just sat there saying nothing? That happened to me recently, and my solution was to quite literally force the other players to contribute.

Now, before that sounds worse than it actually was, let me explain what happened.

I was running my Khor Badhir Shadowdark campaign, and the group was in the middle of taking over an entire city called Telepathica. The campaign is run somewhat like a West Marches game in that the players decide what goals they want to pursue and what adventures they want to undertake, except I have a fixed group instead of a rotating cast.

My players had developed a deep hatred for one particular nation in the setting, so naturally they decided to invade one of its cities.

With an army.

As one does.

The Players Needed to Escape the City

The group was in the middle of a multi-part adventure and had just completed one of their major objectives. The problem was that they were still deep inside enemy territory, and opposing forces were closing in.

I did not want to run battle after battle while they escaped. That would have become tedious fast, and frankly, I wanted to move on to the next interesting part of the adventure. At the same time, simply saying, “Okay, you escape,” felt a little too handwavey.

So, I ran a skill challenge.

The structure was simple. The party needed six successes before they accumulated three failures. Each failure would create some kind of narrative setback, but the point of the challenge was primarily to resolve the escape quickly without turning it into another hour of combat.

My hope was that they would succeed, get out of the city, and we would move on.

The dice had other plans.

They rolled horribly. Just catastrophically bad. Failure after failure piled up, and they hit three failures in record time.

Sometimes the dice simply murder you.

Failure Needed to Have Consequences

A failed skill challenge should not automatically result in a total party kill. Imagine losing your entire group because three dice rolls went badly. That would be what I call a DM screw job.

But failure also should not mean nothing. If there are no consequences, then why bother rolling?

So, I ruled that four of the six characters had been captured by the enemy, while two managed to escape. The four players whose characters had been captured rolled up backup characters, joined the two survivors, and headed back into the city to rescue everyone else.

That setup works particularly well in this campaign because I already have an in-world system for replacement characters.

Shadowdark is lethal. Very lethal.

So, in the setting, there is a man named Uncle Merrick who owns a butcher shop called Merrick’s Meats. The butcher shop is just a front for his real operation: recruiting adventurers. Uncle Merrick keeps brave souls on standby, and when a character dies or otherwise gets removed from play, he can teleport a replacement adventurer to the group.

It sounds ridiculous, but it works beautifully.

And frankly, Shadowdark is lethal enough that I even added house rules to make characters more survivable. People occasionally advertise products promising to make Shadowdark even more deadly, and that always makes me laugh. You do not need help. Shadowdark will kick your teeth in all by itself.

Then the Rescue Scene Completely Stalled

The surviving characters and their new recruits headed back into Telepathica to infiltrate the prison and rescue the captured party members.

There was only one small problem: I had prepared none of this.

I had never expected four characters to get captured, so I was improvising the entire rescue scene on the fly. I started describing the area, setting up the situation, and asking the players what they wanted to do.

And almost nobody said anything.

One player engaged with the scene. He discussed options, suggested plans, and tried to figure out how the group might approach the prison. Everyone else was mostly silent.

What made the situation even more noticeable was that the one player contributing knew he was dominating the conversation. Multiple times he said something along the lines of, “Guys, please jump in if you have ideas. I don’t want to be the only one talking.”

That was excellent self-awareness on his part, and I appreciated it.

But the others still were not saying much.

This was unusual for me. I have run games for a very long time, and while quieter players are nothing new, I had rarely encountered a scene where almost the entire group simply refused to engage. It was like pulling teeth.

Want to Get Better at Keeping Players Engaged?

Sometimes the hardest part of game mastering is not building encounters or knowing the rules. It is figuring out what to do when the table itself is not working. Maybe one player is dominating the conversation, other players are checking out, or a scene you expected to work simply falls flat.

The Secret Art of Game Mastery is packed with practical advice for dealing with situations like these. It covers player management, pacing, improvisation, preparation, encounter design, and the judgment calls that come with keeping a game fun for everyone at the table.

If you want to become better at reading your group and adjusting when something is not working, check out The Secret Art of Game Mastery.

Should You Call on Quiet Players Directly?

At that point, I decided to change how I was running the scene.

I put everyone into strict turn order and began calling on players one by one, asking what they wanted to do. The funny thing is that Shadowdark actually recommends running the entire game in turn order, even outside combat. I tried that rule when I first started running the system and quickly threw it out.

I hated it.

In my experience, strict turn order during normal exploration and conversation made the game feel artificial and slow. People naturally interrupt each other, build on ideas, react, and bounce conversations back and forth. Putting every moment into rounds sucked the energy out of those interactions.

But in this particular situation, I thought turn order might solve the problem.

It did not.

I would call on a player, and the response was often something like, “Uh, I’m not sure. What does everyone else think?” Then I would move to the next player and get more or less the same thing.

Nothing was happening.

Why the Scene Was Not Working

Part of the issue was that I was trying to run the rescue more like an improvisational scene than a traditional tactical encounter.

I wanted each player to contribute something that moved the situation forward. One player might describe sneaking toward a guard post. Another might create a distraction. Someone else might interact with an NPC or take advantage of something established by the previous player.

The idea was that we would collectively build the story of the rescue. I would establish the situation, provide information, adjudicate outcomes, and then the players would keep adding to the scene.

In theory, that sounded great.

In practice, it was falling flat.

So, I finally stopped the game.

Sometimes You Need to Explain What You’re Doing

I called a timeout and explained exactly what I was trying to accomplish.

I told the players that this was not really a normal encounter. We were essentially improvising the rescue together, and I wanted everyone to contribute to the unfolding narrative. When it was their turn, they did not need to produce the perfect tactical move. They did not need to worry that one wrong choice would doom the rescue. They simply needed to do or say something that pushed the situation forward.

I also revealed something I normally would have kept behind the screen.

The stakes were not quite as dire as they probably thought.

This was less about succeeding at a carefully simulated infiltration and more about creating an interesting story together. I very rarely explain my games this way because normally I want the players immersed in the world and responding to events as their characters.

But the scene was dying.

So, I did.

And holy crap, did things improve.

Why the Players Were So Quiet

Looking back, I think there were two things happening.

First, the players probably did not understand the improvisational nature of the scene. Everything was theater of the mind, and the way I was running it diverged from what they were accustomed to in a more traditional D&D-style game. They may have been waiting for clearer choices, a tactical map, or more concrete information before acting.

Second, I think they simply needed encouragement.

Sometimes players hesitate because they do not want to make the wrong decision. Sometimes they worry about stepping on someone else’s toes. Sometimes they assume another player has a better idea. And sometimes a group gets caught in a weird social loop where everyone is waiting for someone else to act.

A little push can break that loop.

Breaking Immersion Can Be Worth It

Once I explained what we were doing, the scene worked much better. The players began contributing, ideas started flowing, and people built on what the previous player had done.

Suddenly, the rescue actually had momentum.

Yes, stopping the game and explaining the mechanics broke immersion. It also weakened some of the tension because once I told them, “We are basically building this rescue scene together,” they knew I was not sitting behind the screen waiting to punish one bad decision with catastrophic failure.

But the alternative was worse.

The game had stalled.

If something you are trying clearly is not working, especially if you are experimenting with a style of play your group is not accustomed to, there is nothing wrong with stopping and explaining what you are trying to accomplish.

Explain the mechanics. Explain the expectations. Explain what kind of participation you are looking for.

Then start again.

Quiet Players Still Need an Opportunity to Contribute

There is an important distinction here. I am not saying every quiet player needs to become the loudest person at the table.

Some players genuinely prefer to speak less. Some enjoy watching other players take the lead, and that is perfectly fine. Different people engage with the game in different ways.

The problem comes when players are not contributing because they are confused, hesitant, disengaged, or simply being drowned out by someone else. That is where the game master may need to intervene.

Calling on someone directly can help. Asking a specific player, “What does your character think about this?” can create an opening that would not otherwise exist. In extreme situations, temporarily using turns can also ensure everyone gets space to participate.

But I would not make that your default approach.

Running an entire RPG in rigid turns outside combat tends to make conversations feel unnatural, at least in my experience. The goal is not to force everyone to speak every thirty seconds.

The goal is to create space for everyone to contribute.

Know When to Pause the Game

The biggest lesson I took away from this session was not that game masters should force quiet players to talk. It was that sometimes the best way to fix an in-game problem is to step out of the game.

If a mechanic is confusing everyone, explain it. If you are trying something experimental, tell the players what you are trying to accomplish. If the group is completely stalled because nobody understands what they are supposed to do, stop pretending everything is fine and talk about it.

Yes, you sacrifice a little immersion.

Sometimes that is worth it, because immersion does not matter very much if nobody is actually playing the game.