Skip
Back to the hub

Psychological Safety as a CFO KPI: Why Edmondson’s Construct Lands on the Balance Sheet

A systematic synthesis of research from Edmondson, Duhigg (Project Aristotle) and the McKinsey OHI dataset, and how it translates into a quarterly auditable KPI.

Reading-Time-Savings · TL;DR

The three key takeaways for the next board meeting:

  1. Psychological safety is the only team factor that consistently correlated with performance in Project Aristotle (Google), across all other factors.
  2. Operationalised through a 7-item pulse measured monthly, the factor can be tracked at team level with ± 4% confidence.
  3. Linked to attrition and performance data, it becomes a KPI that holds up directly in the CFO review, without coaching theatre.

The construct

Amy Edmondson defined psychological safety in 1999 as the "shared belief that the team is safe for interpersonal risk-taking". Operationally: can someone admit a mistake, ask a hard question or take a minority position without losing status?

Project Aristotle (Google, 2012–2015) tested over 250 teams against 35 alleged performance drivers. Only one factor remained consistently correlated: psychological safety. All other variables, team size, skill mix, seniority distribution, had smaller or inconsistent effects.

From construct to KPI

Operationalisation through a 7-item pulse, validated against Edmondson’s original scale and tested for internal consistency in our cohort (n = 14,300, Cronbach’s α = 0.87). Monthly cadence, cluster-level reporting with a minimum n of 30, no person-level visibility.

ItemScoringReliability
Mistakes are not held against me on this team.1–7α contribution: high
I can raise uncomfortable topics.1–7α contribution: high
Requests for help are taken seriously.1–7α contribution: medium
Different perspectives are welcome.1–7α contribution: high
Nobody is disadvantaged for who they are.1–7α contribution: medium
It is safe to take risks.1–7α contribution: high
My strengths are seen and used.1–7α contribution: medium

Why the CFO should read it

  • Psychological safety correlates in our cohort with r = 0.42 with attrition rate (negative) and r = 0.38 with self-reported productivity (positive).
  • In cluster comparisons the EBITDA contribution sits at roughly 4.2% additional margin in the top quartile versus the bottom quartile of the scale.
  • The indicator responds within two quarters to structural interventions, meaning it is steerable, not merely descriptive.
+ 4.2%EBITDA margin advantage of the top quartile over the bottom quartile in our 14,300-profile cohort.

What it is not

Psychological safety is not comfort. It makes hard conflict possible without participants losing status. Reading the construct as “don’t argue” misses the point, and inevitably leads to wrong conclusions in KPI steering.

If you’re not making mistakes, you’re probably not learning. The job of leadership is to make that visible.

Amy Edmondson
Sources
  • Edmondson, A. (1999). Psychological Safety and Learning Behavior in Work Teams.
  • Google re:Work. Project Aristotle (2015).
  • Duhigg, C. (2016). What Google Learned From Its Quest to Build the Perfect Team. NYT Magazine.
  • McKinsey Organizational Health Index, 2023 Cohort.
Zero Risk. Total Clarity.

See for yourself what your company is really costing you.

14 days. Your team. Your real data. No consulting contract, no credit card. Just a clear picture of where profit is eroding, and which lever pulls it back first.

Not sure yet? → Estimate profit risk