During a recent session on psychological safety with project leaders, someone asked a sharp question: how do you assess whether a team is safe before you've joined it?
It's a legitimate concern. When you're being recruited into a new team, the information asymmetry is brutal. The hiring manager controls the story. The team is filtered. The leadership is rehearsed. Unless you have a trusted contact on the inside, you're mostly buying a narrative.
The solution isn't to ask better questions of the manager. It's to ask different questions of the team itself.
Why the manager alone isn't enough
Standard interview questions can tell you something:
| Question to ask the manager | What it reveals |
|---|---|
| What does team turnover look like here? | Stability and morale signals |
| Could I review the team's working agreements? | Whether norms are explicit and maintained |
| Give me an example of someone pushing back on a decision you made recently. | Whether the manager has actually experienced challenge |
These are worth asking. But the manager controls their own answers. To get past the theatre, push for one-on-one conversations with at least two or three team members. If the manager resists that request, walk away.
Questions to ask team members directly
When you get those conversations, go deep. Generic questions get generic answers. Try these instead:
- On errors and recovery:** Walk me through a recent mistake in your work here. What happened when you raised it—how did your manager and peers respond?
- On upward feedback:** How often do you flag concerns about a colleague's work? When did you last raise issues with someone above you in the hierarchy?
- On dissent:** Tell me about a time you disagreed with something your manager and most of the team supported. What came of it?
- On solidarity under fire:** Has an outsider ever criticized you or a teammate unfairly? What did your team do?
The point isn't the content of the answers—it's the ease with which people give them. In an unsafe team, people speak in achievements and credit splits. In a safe team, they tell stories about missteps and recoveries.
What to listen for
Active listening during these conversations might reveal something different from what people are explicitly saying. Watch for:
- Ease with errors:** Do team members describe setbacks readily, with context and lessons? Or do they pivot quickly to wins?
- Specificity in examples:** Vague answers—"we give feedback all the time"—are different from concrete ones. The concrete ones are real.
- Body language and pauses:** Hesitation before describing a disagreement can tell you as much as the answer itself.
Our analysis: what this means for project leaders
The reason this matters isn't just the candidate experience. It's the mirror.
If your hiring process can't survive a candidate asking direct questions of the team, the team probably has the issues the candidate is trying to detect. The process is the product.
The trade-off worth naming: most managers resist open access to the team during hiring because they're afraid the team will say the wrong thing. That's a reasonable fear in a dysfunctional team and an unreasonable fear in a healthy one. The right response to a candidate asking for team access is to say yes—and use the conversation as a feedback loop, not to find a way to say no.
Worth watching: how the manager reacts when you ask for the working agreements. In a safe team, the document exists and the manager is proud of it. In a fragile team, the document is fuzzy, outdated, or treated as a compliance artefact. The reaction is the data.
Bottom line: psychological safety is something you test for, not something you assume. The interview is the test.
Key takeaways
- Ask the manager for turnover data and the team's working agreements—watch how they're delivered.
- Push for one-on-ones with team members; generic questions get generic answers.
- Listen for how people describe errors and setbacks, not just how they describe wins.
- If the manager blocks access to the team, treat that as the answer you needed.
- The hiring process itself is a signal: if it can't survive direct questions, the team probably can't either.
Frequently asked questions
How do you assess psychological safety before joining a team?
Push for direct conversations with team members, ask specific questions about mistakes and challenges, and listen for ease of answer as much as content. If the manager won't grant access, that's your answer.
What should I ask the hiring manager?
Turnover rates, the team's working agreements, and recent examples of someone pushing back on a decision. Vague answers are themselves signals worth noting.
What should I ask team members directly?
How mistakes are received, how often they raise concerns with peers and superiors, and what happened when they disagreed with a team direction. Concrete stories reveal more than rehearsed answers.
What if the manager blocks access to team members?
Walk away. A team that can't survive a candidate talking to its members is communicating something important.
Why does this matter for project leaders?
Because the hiring process is the team's first product. If it can't survive direct questions, the team probably can't either—and you're both the candidate and the mirror.