The science behind the Culture Strength Check

What we measure, and what we don't

There are two very different things you can measure about a culture. The first is its content, or type: whether it is collaborative or competitive, cautious or bold. Most culture tools sort you into a type. The second is its strength and intentionality: how clearly and deliberately the culture has been built, and therefore how coherent and resilient it is. We measure the second.

We do this for three reasons. First, it is actionable: a type label leaves you nowhere to go, whereas measuring the practice of building culture hands you the change levers. Second, there is no single right culture, what works for one team fails for another, so ranking teams against one ideal is the wrong move. What matters is how clearly a culture is being built and whether people can see it and choose to belong to it. Third, it is honest: strength and intention can genuinely be read from behaviour, whereas claiming to X-ray a team's soul in eight minutes cannot.

What this instrument does not claim. It is not a personality or culture-type test. It does not prove causation for your team. And on its own, taken by a single leader, it is an informed estimate, not a validated measurement, a distinction we return to in Section 06.

Five layers, read as one system

The model is not a flat checklist. Its parts sit at different depths, and reading them as layers is what makes it a model rather than a list.

• FoundationPsychological safety
  The foundation everything builds from. If a team is not safe, people manage what they say, and every other reading turns overly optimistic.
• PracticeThe six conversations
  The levers a leader actually pulls to build culture on purpose. These are behaviours, which is what makes the read actionable.
• LensThe three gaps
  Not more things to measure, but the three ways we read every conversation: distance to the standard, leader versus team, and how much the team agrees.
• OutcomeEngagement
  The felt result: the energy, purpose and focus the six conversations produce. We report it on its own rather than mixing it into the score, because it is an outcome of building culture, not one of the levers you pull.
• ResultsWhat the business measures
  Retention, performance, innovation and growth. Shown as context and never scored, because these are business data rather than something a team can self-report. Columbia University found strong cultures turn over 13.9 per cent of their people a year against 48.4 per cent in weak ones.

Foundation · Psychological safety

Psychological safety is the shared belief that a team is safe for interpersonal risk-taking, that you can ask a question, admit a mistake, or disagree without it being held against you.¹ Amy Edmondson's foundational work showed that teams higher in safety learn and perform better,¹ and Google's study of 180 of its own teams (Project Aristotle) found it the single largest differentiator between its best and worst teams.² We treat it as the substrate, not a seventh conversation: when safety is low, people do not voice the truth, so the rest of the report is systematically inflated. In scoring, low safety therefore acts as a gate on confidence in everything above it (Section 04).

Practice · The six conversations

The six conversations are drawn from Shane Hatton's book Let's Talk Culture, the behaviours through which culture is built by design. Each also maps to a published construct, so the framework is grounded in both practice and research.

The order is not arbitrary: each conversation builds on the last, and capability sits before confrontation deliberately, because holding someone to a behaviour they have not been equipped for is unfair and erodes trust.

Lens · The three gaps

The three gaps are not additional things we measure; they are three ways of reading the same conversations. Each has a distinct research anchor, and this framing, culture as a set of gaps rather than a grade, is the part no other instrument does.

• The aspiration gap, the distance between where a team is and the standard it aspires to. Goal-setting theory holds that performance is driven by exactly this discrepancy between the current state and a clear goal.⁶
• The perception gap, the distance between how a leader reads the team and how the team reads itself. The self-and-other rating literature behind 360-degree feedback shows that leaders who over- or under-rate relative to their people carry predictable blind spots.¹⁸
• The spread, how much a team agrees with itself. “Climate strength”, the degree of within-unit agreement, is an established construct: a strong average masking high dispersion is a weak, contested culture, not a healthy one.¹⁹

Outcome · Engagement

Engagement, rendered here in plain language as energy, purpose and focus, is our read of the validated dimensions of work engagement, vigour, dedication and absorption.²⁰ It is an outcome, not a lever: you do not build engagement directly, you build the conditions and the conversations, and engagement tells you whether they are landing. Kahn's original conditions for engagement, meaningfulness, safety and availability,²¹ map almost one to one onto this model, with safety as the foundation, availability as capability, and meaningfulness as the purpose we read at the top.

Behavioural, not evaluative

The single most important design choice is that we never ask people to rate the construct directly. “Rate your team's psychological safety out of 100” triggers ego and social desirability, and almost everyone answers around 85.²² Instead we ask about specific, recent, observable behaviour and compute the construct from it. Asking “when someone makes a mistake here, does it tend to get held against them?” is answered honestly, because it does not feel like a judgement of the respondent, and it tells you far more.

Three moves make this work:

• Behavioural, not evaluative. We ask what happens, not how good it is.
• Recent and specific. “In the last two weeks…” beats “generally…”, because the memory of a real event resists spin.
• Reverse-scoring. Roughly a third of items are worded so that agreeing is the unflattering answer, which breaks the auto-pilot of straight agreement and helps surface the truth.

Every item maps to one facet of one construct, so results are specific enough to act on rather than vague. There are 32 items in total, across the six conversations, psychological safety and engagement. In the team version, items written from the leader's point of view are reframed to the team member's seat, so both are reading the same team through comparable questions, which is what makes the perception gap valid.

From answers to a score

• Each answer becomes 0 to 100. Five-point scales map to 0 / 25 / 50 / 75 / 100; scenario and recency questions are scored best-to-worst on the same range; reverse-scored items are flipped. Nobody ever sees an item as a score, only as a question.
• Each layer is the mean of its items, rounded to a 0-to-100 score and banded: By design (70+), Taking shape (50 to 69), or By default (under 50).
• Culture strength is the mean of the six conversation scores. Psychological safety and engagement are reported separately, as the foundation and the outcome.
• Safety is a gate. It is reported as its own band, and when it is thin it flags the whole read as likely optimistic and shapes the recommended priority, rather than simply averaging in.
• The aspiration gap is the distance from a healthy benchmark. Until enough real data exists to set population norms, that benchmark is seeded at a deliberately healthy anchor (see Section 06).
• The priority follows a simple default: fix the foundation first if safety is thin; otherwise, start with the lowest-scoring conversation, since that is usually where the most is to be gained. It is a starting point, not a rule. A leader may equally choose to build from a strength where that carries more leverage.

How the perception gap is measured

A single leader can give an informed read, but two of the three gaps, perception and spread, do not exist until the team also answers. In the team benchmark, teammates take the same read anonymously, and:

• Anonymity is protected. Individual answers are never shown, and results unlock only once at least four people have responded, so no single teammate can be identified.
• The team score for each layer is the mean of the individually computed member scores.
• The perception gap is the leader's layer score minus the team's, per layer and overall.
• The spread is the standard deviation of members' scores within each layer, our operational measure of climate strength.¹⁹ A reasonable mean with low spread is a strong, shared culture; a high spread signals a contested one, even when the average looks fine.

Validity, limits, and what comes next

A methodology that will not name its own limits does not deserve to be trusted, so here are ours plainly.

• It is self-report. It measures perception, which is a large part of what culture actually is, but it shares the known limits of self-report data.
• Solo, it is a single rater. The free leader read is one perspective, an informed estimate, and leaders are known to over-rate, particularly on psychological safety. It becomes a measurement when the team answers.
• It is not yet psychometrically validated. Item performance, internal consistency, the behaviour of reverse-scored items, and the factor structure will be tested in a pilot. The current bands are interpretive anchors, not norm-referenced percentiles, and the healthy benchmark is a placeholder until real population norms accumulate.
• It is correlational, not causal. The model draws on causal theory, but this instrument does not prove causation for your particular team.
• It is a starting point, not a verdict. The read is designed to open the right conversation, not to replace listening to your team.

None of this is a reason to distrust the read; it is the basis for trusting it, at exactly the level it earns. The citations below are the grounding for each design choice.