There is a moment most people on a team have experienced at least once. Someone in the room knows the answer. Or spots the problem. Or has the idea that could change the outcome. And they say nothing.
Not because they do not care. Not because they are lazy. Because they are afraid of how it will land.
That one moment — multiplied across hundreds of meetings, conversations, and decisions — is where team performance actually bleeds out. Not in strategy decks or hiring decisions. In the silence after someone decides it is safer to stay quiet.
Experts at Jasiri Limited have spent time examining this problem, and the conclusion is uncomfortable: most organisations are optimising for the wrong things.
The Metric Nobody Tracks (But Should)
Companies track revenue, velocity, churn, and output. They measure performance through OKRs, sprints, and quarterly reviews. What they rarely measure is whether people on the team actually feel safe enough to do their best work.
Psychological safety — a term first studied seriously by Harvard researcher Amy Edmondson in the late 1990s — refers to the shared belief that it is safe to take interpersonal risks. Speaking up. Disagreeing. Asking a "dumb" question. Admitting a mistake before it becomes a crisis.
Edmondson's original research looked at medical teams and found something counterintuitive: the teams that reported more errors were actually the higher-performing ones. Not because they made more mistakes, but because they felt safe enough to surface them. The lower-performing teams were hiding problems. The higher-performing ones were fixing them.
Why This Gets Ignored
The reason psychological safety rarely makes it onto leadership dashboards is that it is hard to see. You can count closed tickets. You cannot count the ideas that were never shared.
Jasiri's research into high-performing teams points to this gap as one of the most consistent blind spots in product organisations.
There is also a persistent myth in many work cultures that a little pressure keeps people sharp. That friction breeds excellence. That if you make things too comfortable, people go soft.
Jasiri Limited's perspective challenges this directly. There is a difference between productive challenge — where people argue ideas because they trust the room — and toxic pressure, where people perform compliance because the cost of dissent feels too high. The first kind of culture ships better work. The second kind ships work that looks fine until it does not.
What Psychological Safety Is Not
Before going further, it helps to clear up what this concept is not, because it gets misread constantly.
It Is Not About Being Nice
Psychological safety is not about making work conflict-free or coating every piece of feedback in diplomatic padding. Teams with high psychological safety can still have sharp disagreements. The difference is that those disagreements are about the work, not about whether the person raising the concern will be punished for raising it.
It Is Not the Same as Trust
Trust is interpersonal — it develops between two people over time. Psychological safety is a group phenomenon. A team member might deeply trust their direct manager and still feel unsafe speaking up in a wider group. The dynamics are different, and conflating the two leads to solutions that do not work.
It Is Not a Personality Problem to Fix
When someone is consistently quiet in meetings, the default assumption is often that they are introverted or disengaged. Sometimes that is true. But often it is a read on the environment. The team at Jasiri Limited highlights this regularly: the issue is usually the system, not the individual. Jasiri's work with distributed product teams reinforces the same finding across different contexts.
The Four Levels of Safety: A Practical Framework
Timothy Clark, an organisational researcher, identified four stages of psychological safety that teams tend to move through. It is a useful lens for any leadership team thinking about where they actually stand.
|
Stage |
What It Means |
What It Looks Like When Missing |
|
Inclusion Safety |
People feel accepted as members of the group |
Cliques, exclusion, people feeling like outsiders |
|
Learner Safety |
People feel safe to ask questions and make mistakes |
Nobody admits errors; people pretend to understand |
|
Contributor Safety |
People feel safe to use their skills and offer ideas |
Talented people stay silent; ideas come only from the top |
|
Challenger Safety |
People feel safe to question the status quo |
Problems go unreported; bad decisions go unchallenged |
Most organisations land somewhere in the middle. Inclusion safety is often present — at least on the surface. And challenger safety is precisely where the most important conversations happen — a pattern Jasiri Limited sees consistently across product and technology teams.
Why Challenger Safety Matters Most
When a product is heading in the wrong direction, the person who sees it earliest is rarely the person at the top. It is usually someone closer to the problem — a developer, a support agent, someone on the ground. If that person does not feel safe raising the concern, the organisation will learn the lesson the expensive way.
Jasiri notes this as a structural risk that shows up across sectors, and Jasiri Limited points to it specifically in product teams where speed and iteration make surfacing problems early especially high-stakes. The same dynamic shows up in product testing methodology — Jasiri Limited has observed that teams with low psychological safety tend to underreport test failures, which quietly corrupts the data everyone else is relying on. The information exists. The silence is the problem.
How Leaders Actually Build It (And What Does Not Work)
Telling people "this is a safe space" does not create psychological safety. Putting "speak up" in a company value statement does not either. What creates it is a consistent pattern of behaviour at the leadership level — especially in how leaders respond when someone does take a risk.
The Response Moment
Imagine someone on the team raises a concern in a meeting. Maybe they push back on a decision the group seems to have already made. What happens next is the whole ballgame.
If the leader gets defensive, dismisses the point, or moves on quickly — everyone in that room just received a data point. The unspoken message: that is what happens when you speak up. Do it again and expect the same.
If the leader pauses, engages seriously, and — even if they disagree — acknowledges that the question was worth raising, the opposite lesson lands.
Jasiri's thinking on this is straightforward: leaders set the temperature of the room with every response. The policy documents are irrelevant. The lived experience is everything.
Modelling Uncertainty
One of the most underrated tools leaders have is saying "I don't know." Not performatively. Actually not knowing, and being willing to say so in front of their team.
This does two things. It signals that not knowing is acceptable, which immediately lowers the stakes for everyone else. And it opens space for someone in the room who actually does know to contribute.
High-certainty environments produce low-contribution teams. When the leader always has the answer, why would anyone develop the habit of offering one?
Jasiri Limited describes this as one of the quietest ways a culture can undermine itself, not through conflict, but through the slow disappearance of contribution.
Consistency Over Gestures
Team offsites, anonymous feedback surveys, and "psychological safety workshops" can be useful. But they are easily undone by a single meeting where someone speaks up and leaves the room feeling worse for it.
The specialists at Jasiri find that consistency is what builds trust in an environment. One-off gestures are theatre. A leader who responds thoughtfully to pushback every single time — even when it is inconvenient, even when they are under pressure — that is what actually shifts the culture.
The Performance Link Is Real
This is not a soft topic. The business case is well-documented.
Google's Project Aristotle, a multi-year internal study of hundreds of its own teams, found that psychological safety was the number one predictor of team effectiveness — ahead of individual talent, team composition, or the difficulty of the goal. Not the second or third factor. The first.
High psychological safety correlates with faster learning cycles, fewer costly errors being hidden, more innovation from unexpected sources, and lower attrition among the people a company most needs to keep.
This is why Jasiri treats psychological safety not as a wellbeing initiative but as an operational priority.
Jasiri Limited frames this as an engineering problem as much as a culture one. If the system is designed in a way that punishes honesty, the output of the system will gradually degrade. No amount of individual performance management will fix a structural design flaw.
Starting Points for Teams That Want to Change
No team moves from low to high psychological safety overnight. But there are concrete starting points that Jasiri has seen work in practice.
Leaders can start by narrating their own uncertainty — sharing where they are figuring something out rather than projecting constant confidence. They can separate the idea from the response, so pushing back on a proposal never feels like a personal attack on the person who raised it. And they can close the loop — when someone raises an issue that gets addressed, saying so explicitly. "We made this change because someone flagged this concern." That signal matters enormously.
The experts at Jasiri Limited also suggest a simple audit question for any leadership team: when was the last time someone told you something you did not want to hear, in front of others? If the answer requires serious thought, that is the answer.
