A good mindset improves performance - how?

If you’ve already fixed strategy, structure and headcount and still can’t explain why output lags, the variable you haven’t audited is how the team talks to itself. Good people, bad output is rarely a talent problem. Understand this as a dynamics problem, and it becomes something to act on as part of building for success.

Google spent years studying 180 of its own teams, testing hundreds of variables, expecting to find that the best teams were built from the best individual talent. They found something else: the strongest predictor of team performance was psychological safety, not who was on the team but how the team worked together.[^1]

Does mindset actually improve performance?

Yes, and it isn’t a single company’s finding. An independent meta-analysis found the same link between feeling psychologically safe and task performance.[^2] This is a documented, repeatedly-tested variable, not a cultural nicety.

It’s also not what the sceptics assume. Psychological safety doesn’t mean comfort, or protecting people from criticism. Teams that have it argue harder. They challenge ideas and surface disagreement without fear of being punished for it. That raises the bar on performance and accountability; it doesn’t lower it.

Edmondson’s research shows why.[^3] Psychological safety doesn’t drive performance directly; it drives learning behaviour: asking questions, admitting mistakes, testing ideas out loud. It’s the learning behaviour that improves performance. Her earlier hospital research showed the same pattern from an unexpected angle: better-performing nursing teams reported more medication errors than weaker teams, not fewer.[^4] Edmondson’s reading was that the better teams were not making more mistakes. They were able to discuss them. Teams that hide problems don’t have fewer problems. They have the same problems, discovered later and at higher cost.

Those are the real stakes for a scale-up. Early on, small teams hold this together informally; everyone’s close enough to say what needs saying. As headcount climbs toward a few hundred, that informal cohesion doesn’t scale on its own, and the honest, plainly-spoken disagreement that used to happen by default starts needing to be built deliberately instead.

That’s where a structured approach earns its place. Feldklang’s framework makes building mindset deliberate: a clear primary task so the team knows what it’s actually there to do, role holders who act from their role rather than personal identity, lively discourse that tolerates disagreement instead of avoiding it, and brave leadership willing to hold that discomfort rather than smooth it over. None of this is soft. It’s the operating condition that lets a team’s actual talent reach the surface instead of staying hidden until it fails expensively.

If you want an ambitious team, strategy alone won’t get you there. You also have to deal with the mindset that gets that team moving, not just hope it will be good enough.

[^1]: Google re:Work, “Project Aristotle findings” (rework.withgoogle.com), a multi-year internal study across 180 Google teams examining hundreds of variables; findings are descriptive and specific to one well-resourced company.

[^2]: Frazier, Fainshmidt, Klinger, Pezeshkan & Vracheva, “Psychological Safety: A Meta-Analytic Review and Extension,” Personnel Psychology, 2017, a meta-analysis of 136 samples covering over 22,000 individuals and nearly 5,000 groups.

[^3]: Amy Edmondson, “Psychological Safety and Learning Behavior in Work Teams,” Administrative Science Quarterly 44(2), 1999, a field study of 51 manufacturing teams modelling the effects of psychological safety and team efficacy on learning and performance.

[^4]: Amy Edmondson, research on medication error reporting among hospital nursing teams, widely cited as part of her early work on psychological safety; findings are descriptive of the teams studied rather than a controlled experiment.