How to Build Trust on a Team That Has Stopped Speaking Up

You ask, "Any questions?" and the room goes still. You ask, "Does anyone see a problem with this plan?" and people study the table like it holds the answer. Then, two weeks later, you find out three people saw the problem on day one.

If that is your team right now, you are not a bad leader, and your people are not lazy. Silence is usually a decision people made for a reason. The good news is that you can change the reason.

Here is the short answer. Go first by owning your part. Hold one short meeting where people can name a problem without risk. Fix one thing they name, fast. Then report back, every week, for a month. Trust comes back when speaking up starts to feel safe and worth it. The rest of this page shows you how.

Signs your team has gone quiet

• Meetings end early because nobody adds anything.
• You hear about problems from customers or from the hallway, not from your team.
• People agree in the meeting and complain after it.
• The same one or two voices answer every question.
• Mistakes get hidden or fixed quietly instead of talked about.

One sign alone means little. Three or more is a pattern worth your attention.

Why people stop talking

Researchers at New York University interviewed 40 people who worked full time in fields like finance, consulting, and advertising. Thirty-four of them, or 85 percent, said there had been at least one time when they felt they could not raise an important issue with their boss. Only about half said they generally felt comfortable speaking up at work.

When the researchers asked why, three reasons came up most:

1. Fear of a label. In all, 30 percent worried they would be seen as a troublemaker or a complainer.
2. Fear of hurting a relationship. Another 27.5 percent worried they would lose the trust or support of people they needed.
3. Futility. And 25 percent felt it would not make a difference. "Why bother?"

Notice that two of the three are about fear and one is about hope. That matters, because it means you need to fix both. People must feel safe to speak, and they must see that speaking leads somewhere.

Amy Edmondson, the Harvard professor whose work Google used in its study of team effectiveness, calls this psychological safety: a shared belief that the team is safe for taking interpersonal risks. Her reminder for leaders is a useful one to tape to your monitor: if there is no bad news, it is not that it is not there. It is that you are not hearing about it.

Start with yourself

Before you plan a meeting, think back to the last three times someone brought you a problem. What did your face do? What did you say first? Did anything change afterward?

Be honest. Most of us have a "listening face" that looks a lot like a "please stop talking" face. If you sighed, interrupted, defended yourself, or said "we tried that already," your team noticed. They did not write it down. They just stopped bringing you things.

You do not need a big apology. You need one true sentence, said out loud to the team. That is where the conversation starts.

The conversation plan: the One Thing Meeting

Purpose. Show the team that it is safe to name a problem, and that naming it leads to action.

Time. 30 minutes.

Group size. 3 to 12 people. With a bigger team, run it in smaller groups.

Materials. Index cards, pens that all look the same, a box or bag, and a board or shared screen.

Setup. Hold it in a normal meeting slot, not as a surprise. Sit with the team, not at the head of the table. Tell people the day before: "Tomorrow I want 30 minutes to hear what is getting in our way. Nothing to prepare."

What to say to start

Say this, or something close to it, in your own words:

"I have noticed our meetings have gotten quiet. I think part of that is on me. When people have raised problems, I have not always made it easy. I want to change that. Today I am going to ask one question, and my only job is to listen and say thank you."

Then stop talking. It will feel long. Let it.

The steps

1. Write (5 minutes). Everyone writes an answer to one question on a card, with no name: "What is one thing that slows us down that nobody says out loud?" Everyone writes something, even if it is "nothing today." That way nobody stands out for writing.
2. Collect and read (10 minutes). Put the cards in the box. Mix them. Read each one out loud, word for word, and write a short version on the board. After each card, say only "thank you." Do not explain, defend, or fix yet.
3. Group and choose (10 minutes). Put similar cards together. Ask the team, "Which one, if we fixed it, would make the biggest difference this month?" Let them choose. Pick one.
4. Commit (5 minutes). Agree on one small next step, who owns it, and a date. Say the date out loud. Write it on the board.

Discussion questions

Use one or two of these during step 3:

• What would it look like if this problem were fixed?
• What is the smallest step we could take this week?
• What have we already tried, and what got in the way?
• What do you need from me to make this work?

A way in for everyone

Some people will not speak in a group, no matter how kind you are. That is fine. Offer two other ways in: drop a card in the box after the meeting, or send you a short note within two days. Tell them you will treat those ideas the same as the ones said out loud. Then do it.

What to say when someone finally speaks up

This is the moment that decides everything. The first person to speak is testing the water for everyone else.

Edmondson's advice is simple: pause, take a breath, and say thank you. She adds that it helps to say out loud that speaking up is hard.

Instead of this	Try this
"We already tried that."	"Thank you. Tell me more about what you are seeing."
"That is not really the issue."	"Thanks for saying it. What makes it hard day to day?"
"Who said that?"	"That is helpful. Does anyone else see it the same way?"
Silence, then a new topic	"I want to come back to that. Let's put it on the board."

You do not have to agree. You do have to show that the person is safer, not less safe, for having said it.

The follow-up: four weeks that rebuild trust

The meeting opens the door. The follow-up is what keeps it open. Remember the third reason people stay quiet: "it will not make a difference." Your follow-up is the answer to that.

• Week 1. Take the first step you promised, on time. Then tell the team in one sentence: "You told us X slows us down. Here is what we did." Short and specific beats long and vague.
• Week 2. Ask, at the start of a regular meeting, "What is one thing that got in your way this week?" Use the same card and box if the room is still quiet.
• Week 3. Report on the first problem again, even if the update is "still working on it." Then pick a second card from the first meeting.
• Week 4. Ask the team one question: "Is it easier to raise problems here than a month ago? What would make it easier still?" Listen, thank them, and decide together what to keep.

By week four, many teams no longer need the box. If yours still does, keep it. It is a tool, not a grade.

An illustration: the quiet warehouse team

This is an illustration, not a real team. Dana leads a warehouse team of eight. At the Monday meeting nobody talks. On Thursday, a big order ships late because a scanner had been broken for two weeks. Two people knew.

Dana runs the One Thing Meeting the next Monday. She opens with one true sentence: "Last month Luis told me the scanners were slow and I said we did not have the budget. I should have listened longer." Four of the eight cards mention equipment. The team picks the scanner. Dana gets it repaired by Wednesday and says so on Thursday in one sentence. In week two, someone raises a scheduling problem out loud, with no card. It is not a miracle. It is one fixed scanner and one kept promise.

Common mistakes

• Hunting for the writer. Never ask who wrote a card, and never guess out loud. One slip ends the trust.
• Fixing too many things. Pick one. A finished small fix does more than five half-started big ones.
• Arguing with the cards. Every card is information, even the unfair ones. Thank, then think.
• Going quiet yourself. If you skip the weekly report, the team will read it as "nothing happened."
• Using this for serious issues. Harassment, safety hazards, or anything illegal should not wait for a team meeting. Follow your organization's reporting process right away.

Where this fits

Trust and communication grow together. Once your team is talking again, keep the habit going with the short exercises in 10-Minute Communication Exercises for Small Teams. If you are new in the role and inherited a quiet team, read the First-Time Leader's Guide to Leading a Team. And if you want an activity that gets people comfortable saying "I do not understand," try Team Building for Small Groups.

Sources

• Frances J. Milliken, Elizabeth W. Morrison, and Patricia F. Hewlin, An Exploratory Study of Employee Silence: Issues that Employees Don't Communicate Upward and Why (author manuscript). Published in the Journal of Management Studies, 2003. Journal record. The source for the 40 interviews, the 85 percent figure, and the three most common reasons.
• Google re:Work, Guide: Understand team effectiveness. Psychological safety as the first of five team dynamics, and Edmondson's definition.
• Kara Baskin, Four Steps to Building the Psychological Safety That High-Performing Teams Need, Harvard Business School Working Knowledge, June 14, 2023. Edmondson's point about bad news.
• Matt Abrahams and Amy C. Edmondson, Embracing Failure: How to Make Mistakes That Work, Stanford Graduate School of Business, April 15, 2024. Pause, take a breath, and say thank you.
• James R. Detert and Ethan Burris, Can Your Employees Really Speak Freely?, Harvard Business Review, January 2016. Background on how often employees keep quiet rather than question plans or suggest ideas.

The One Thing Meeting, the response table, the four-week follow-up, and the illustration are our own.

About the author. Jay Olivo is an author, keynote speaker, coach, and transformational leader, who by profession is certified by Maxwell Leadership and a Certified Professional Maintenance Manager (CPMM). More about Jay.