In this article
- Team feedback depends on your response history
- Reduce the size of the first request
- Respond to the first concern without making the giver defend you
- A hypothetical bad-news pattern
- Distinguish a development concern from a reportable issue
- Make one visible change and invite correction
- What to observe next
- Avoid putting the team on the spot
Harvard Business Review examines feedback employees hesitate to give leaders. This guide focuses on the practical conditions around speaking up, without repeating unverified survey figures.
Team feedback depends on your response history
Review the last few occasions when someone challenged your decision or delivered bad news. What did you say immediately? What happened to the person afterwards?
You may remember thanking them. They may remember a public interrogation, a sarcastic remark or being excluded from the next discussion.
Look for observable behaviour rather than assuming you know how safe people feel. Ask a trusted colleague to describe one moment when your response narrowed the conversation.
Do not use the absence of complaints as proof that the process works. Silence can mean agreement, uncertainty, lack of time, concern about consequences or something else entirely.
Reduce the size of the first request
Ask about one practice you can change, rather than inviting an unlimited critique of your leadership.
For example: “When I ask for an update, what makes it difficult to tell me the real position?” Or: “Where do my approval habits slow the work?”
Explain how the answer will be used. If you are reviewing the meeting process, say so. If a formal reporting channel is more appropriate, make that route available.
Offer time and more than one channel where feasible. A private conversation, a written response or an established confidential process may suit different concerns.
Do not demand a personal disclosure or ask employees to name colleagues who agree with them. You are seeking information about the work, not building a list of critics.
Respond to the first concern without making the giver defend you
When the answer arrives, listen and clarify. Avoid explaining your good intentions before you understand the effect.
A useful response is: “Thank you. Can you help me understand one occasion when that happened?” Ask for enough detail to act, rather than every possible proof.
If your immediate reaction is strong, say that you need time to consider it and give a return point. Do not leave the person wondering whether they have damaged the relationship.
You can disagree with a factual claim after checking it. Receiving feedback well does not require accepting every interpretation. It does require responding fairly to the person who raised it.
A hypothetical bad-news pattern
Imagine a team leader says she wants early warnings, but responds to each one by asking the owner to explain the problem in front of the entire group.
A colleague eventually tells her that employees wait until they have a complete solution because they fear being exposed as incompetent.
The leader changes the first response: she asks what is known, what is at risk and what help is needed. She moves detailed performance concerns into the appropriate private discussion.
She also tells the team what changed and why. The next few warnings give her an opportunity to demonstrate the new response.
This hypothetical does not prove what employees in your team feel. It illustrates how a management habit can contradict a stated invitation.
Distinguish a development concern from a reportable issue
Some feedback concerns meeting style or approval delays. Other information may involve misconduct, discrimination, harassment, safety or fraud.
Do not promise to keep every concern between the two of you. Explain the limits of confidentiality and follow the appropriate organisational process.
If the concern is about you, use the proper independent route rather than trying to investigate yourself informally. The person should not have to rely solely on the subject of the complaint for a fair response.
Avoid treating formal reporting as disloyalty. A credible feedback culture includes channels that do not depend on a manager’s goodwill.
Make one visible change and invite correction
Choose a behaviour connected to the concern. “I will be more open” is difficult to verify. “I will ask for risks before discussing solutions in the weekly review” is observable.
Tell the team what you will try without exposing the giver. Then ask whether the change is addressing the original difficulty.
Do not require praise for making the adjustment. Employees may need time to decide whether the change will last.
If you cannot adopt a suggestion, explain the relevant constraint and consider whether another response can address the underlying problem.
What to observe next
Watch for earlier warnings, clearer disagreement and questions that previously arrived only after decisions. Treat these as signals to examine, not proof that trust is fully established.
Use Peak Belt’s trust-and-credibility guide and conflict guide for related management practice. More is available in TrueNorth.
Avoid putting the team on the spot
A public request such as “Tell me what I do badly” may place employees in an uncomfortable choice between silence and exposure. Offer a specific, appropriate channel and time to consider. Do not interpret a reluctance to answer in front of peers as resistance to improvement. Your task is to make the request usable, not to force an immediate demonstration of candour.
Choose one response habit you control. Change it before asking your team to take a larger interpersonal risk.
AI-assisted researched guidance from PeakBelt. Hypothetical examples are labelled in the text. See our editorial approach.