Build trust through honest conversations, clear expectations, and support that fits the person.
Imagine an engineer telling you that a change will not be ready when promised. They knew there was a risk earlier, but waited, hoping to solve it before anyone needed to know.
You want people to bring you problems. You also need commitments to mean something. Other people planned around this delivery, and now they have less time to adjust.
How you respond matters beyond this conversation. The team is learning whether bringing you bad news leads to blame, whether missed commitments receive any attention, and whether asking for help is acceptable.
Psychological safety allows people to speak honestly about the work. Clear responsibilities and fair accountability help the team act on what becomes visible. Leaders are responsible for creating both conditions, including when the uncomfortable truth concerns their own decisions.
Make the expectations discussable
Psychological safety means people can ask questions, disagree, admit mistakes, and raise concerns without fear of humiliation or retaliation. It does not promise agreement, approval, or a comfortable conversation.
Amy Edmondson, whose research established team psychological safety as a field of study, has repeatedly addressed the misconception that it requires lower standards or less accountability. People need room to speak candidly while pursuing demanding goals.
Four ideas help distinguish what a healthy team needs:
- Psychological safety: I can speak honestly about the work, including when I am struggling or disagree with the leader.
- Responsibility: I understand what I am expected to handle.
- Accountability: We review what happened, discuss the impact, and address what needs to change.
- Ownership: I proactively move the work forward, communicate risks, and seek the help needed.
These ideas reinforce one another. An engineer can own a delivery and still need another team’s expertise. Asking for help can be part of ownership. Waiting silently while a known problem grows leaves others unable to respond.
The leader’s expectations must also be open to challenge. A deadline does not become realistic because a manager announced it. People need enough context, authority, capacity, and support to fulfill their responsibilities.
Before holding someone to a commitment, establish what was actually agreed. Was the date a promise, an estimate, or a target that depended on unresolved work? Did both sides understand when a risk needed to be raised?
Accountability becomes unfair when the standard only becomes clear after someone misses it.
Your response teaches the team
Telling people to speak up is a beginning. Your response gives that invitation credibility.
If someone questions your plan and you become defensive, the next invitation will carry less weight. If admitting uncertainty leads to ridicule, people have a reason to appear certain. If you thank someone for raising a concern and then repeatedly ignore it, the invitation becomes hollow.
One lesson I use from Crucial Conversations is to establish mutual respect and a shared purpose. In a difficult conversation, explain what needs attention and why it matters, then ask what matters to the other person. Their perspective needs room to change your understanding and the next step.
Make the invitation specific. Before committing to a release, ask which assumptions could make the date unrealistic. In a technical discussion, acknowledge where your own knowledge is limited. When someone challenges you, understand their reasoning before defending your position.
When a problem surfaces, first establish what happened and what needs attention. Recognize the value of making it visible. Then examine decisions, circumstances, and impact fairly.
The response should fit the situation. An unsuccessful, carefully bounded experiment in unfamiliar territory differs from ignoring an established safeguard. Edmondson makes this distinction in her work on intelligent failure: learning requires thoughtful experimentation, alongside efforts to prevent avoidable mistakes.
In engineering, that could mean testing a new approach with limited exposure and a clear learning goal. Permission to experiment does not remove the responsibility to consider the risk to users or colleagues.
Leaders must model the same openness. If your decision contributed to the problem, acknowledge it and explain what you will change.
Support needs follow-through
I have learned that supporting one person requires paying attention to the people around them. I can listen carefully, adapt my support, and still overlook how much work someone else is absorbing. That was a gap in my leadership that I needed to address.
Knowing each person matters. I want to understand what they care about, where they feel confident, and what is getting in their way. My role is to help create the conditions for them to contribute and grow.
That requires adapting my approach. One person might benefit from discussing a difficult problem together. Another might need time to think before the conversation. Someone facing personal difficulties might need a temporary change in scope, priorities, or support. Ask what would help, then review whether it is helping.
Give people the same respect and take their responsibilities seriously. Adapt the support to the person.
Any adjustment also needs to account for the team. If responsibilities change, make the work allocation clear without disclosing private circumstances. Check who is taking on additional work and whether that arrangement is sustainable. Agree when to revisit it.
Otherwise, support for one person can become an indefinite obligation for another.
Respectful feedback belongs in this environment. Naming an observable behavior, explaining its impact, hearing the person’s perspective, and agreeing on a change can be uncomfortable. That discomfort alone does not establish that the environment is unsafe. Humiliation, threats, retaliation, and impossible demands are different behaviors and deserve attention.
Accountability also continues after the conversation. If the same issue persists, revisit the agreement and the support provided. Further action may be necessary. Psychological safety does not require a leader to leave harmful behavior or repeated unmet responsibilities unresolved.
The leader is accountable for following through too. Promised support that never arrives belongs in the review of what happened.
Use this in the next difficult conversation
Choose one concern or commitment that needs attention. Use three steps to prepare and guide the conversation:
- Clarify expectations. What outcome or behavior was expected? Was it understood and feasible? Establish responsibilities, constraints, and available support. Be willing to revise an expectation that the evidence does not support.
- Invite the truth. Explain why the conversation matters and ask for their perspective. What happened? What am I missing? Ask how your decisions or actions contributed. Give them time to think or return to the conversation if needed. Let what you learn influence the next step.
- Respond and follow through. What impact needs addressing? Agree on what changes, who will do what, what support is needed, and when to review progress. Check the effect on colleagues as well.
This is a practice to repeat, not a script that makes a team psychologically safe after one conversation. Its credibility comes from how consistently people experience it, especially when the news is inconvenient.
Return to the engineer who raised the delivery problem late. Understand why they waited. Examine whether your own reactions or expectations discouraged an earlier warning. Address the impact and agree on how risks will be communicated next time.
They should leave knowing that bringing you the truth was the right decision, and knowing what each of you has agreed to do next.