"When the number comes back bad"

A team-health reading that comes back bad is not a failure of the measurement. It is the entire point of it. The whole reason to read a team is to find out what is actually wrong so it can be fixed, and a reading that comes back bad has done exactly that — it has identified a real problem while there is still time to act on it. Yet a bad reading is almost always received as bad news in the wrong sense, as a failure, a judgment, a thing to explain away, and the temptations that follow — to soften it, game it, or bury it — are all temptations to throw away the very thing the measurement was for.

This is one of the most important and least discussed aspects of measuring team health: what happens when the number is bad. The value of measuring the dimensions depends entirely on the willingness to receive and act on bad results, because a measurement you only accept when it is favourable is not a measurement at all — it is a search for reassurance. The bad reading is where measurement earns its value, and it is exactly where the temptation to destroy that value is strongest. Understanding why an honest bad reading is the point, and why the instinct to soften it is the instinct to waste it, is understanding what separates real measurement from the performance of it.

A bad reading means the measurement worked

The first thing to establish is that a bad reading is a sign the measurement is working, not failing. A measurement that can only ever return good news is not measuring anything — it is a formality that confirms what everyone wanted to hear regardless of the truth. The ability to come back bad is exactly what makes a measurement real: it is sensitive to the actual state of the team, which means it can detect a real problem, which means it can sometimes deliver a result no one wanted. A reading that never comes back bad is not a reassuringly healthy team; it is a broken instrument that cannot detect problems, which is worse than no instrument at all because it produces false confidence.

So the correct response to a bad reading is not dismay that the measurement failed but recognition that it worked — it did the one thing measurement is for, which is to tell you the truth about the team, including the parts you did not want to hear. A company that treats a bad reading as a measurement failure has the relationship exactly backward: the measurement succeeded precisely by returning the uncomfortable result, and treating that success as a failure is the first step toward wanting a measurement that only ever succeeds by returning comfort, which is a measurement that has stopped measuring. The bad reading is the measurement doing its job, and the discomfort it causes is the price of the information it provides, which is exactly the information worth having.

The bad reading is where the value is

Not only is a bad reading a sign the measurement worked — it is where the value of measuring actually is. A good reading confirms things are fine and prompts no action; a bad reading identifies a real constraint and points at what to fix, which is the actionable output that justifies measuring in the first place. The entire case for reading a team is that it lets you find and fix what is wrong, and finding what is wrong means, necessarily, sometimes getting a bad reading. The bad readings are where measurement pays off, because they are the ones that lead to improvement.

This inverts the usual emotional response, which treats good readings as the success and bad readings as the failure. In terms of value, it is closer to the opposite: a good reading tells you to keep doing what you are doing, which is useful but not transformative, while a bad reading tells you something specific is wrong and can be fixed, which is where the real return on measuring lives. A team that gets a bad reading and acts on it improves; a team that only ever gets good readings either has nothing to improve or, more likely, has a measurement that cannot see its problems. The bad reading is the valuable one because it is the one that can change something, and a company that dreads bad readings is dreading exactly the results that make measuring worthwhile. The value is in the bad news, because the bad news is what you can act on.

Why the temptation to game it is so strong

Given that a bad reading is valuable, why is the temptation to game, soften, or bury it so strong? Because a bad reading is uncomfortable, and it can feel like a judgment — on the team, on the leader, on whoever owns the result. When a reading comes back bad, the people attached to the team have reasons to want it to be less bad: it reflects on them, it creates work, it is unpleasant to sit with. So the temptation arises to make the reading look better than it is — to soften the language, to game the inputs, to find reasons the reading is unfair, or simply to bury it and not report it. Each of these makes the discomfort go away, and each destroys the value of the measurement.

This temptation is strongest exactly when the reading is most valuable, which is the trap. The worse the reading, the more valuable the information — and the stronger the temptation to suppress it, because the worse it is, the more uncomfortable it is and the more it feels like a judgment. So the readings most worth acting on are the ones most at risk of being softened or buried, which means the temptation systematically attacks the highest-value information. A company that gives in to this temptation loses precisely the readings it most needed, keeping the comfortable ones and suppressing the ones that would have led to real improvement. The strength of the temptation is proportional to the value of the information, which is why resisting it matters most exactly when it is hardest.

Gaming the reading destroys what it measured

The specific tragedy of gaming a bad reading is that it does not just hide the problem — it destroys the measurement's ability to help with the problem. A reading that has been softened or gamed no longer reflects the team, so it can no longer aim an intervention or track a change, which means the whole apparatus of reading and acting collapses. The team still has the problem the honest reading would have identified; it has just lost the reading that would have let it fix the problem. Gaming the measurement keeps the disease and discards the diagnosis, which is the worst of both.

This is why gaming a reading is worse than not measuring at all. A company that does not measure at least knows it is operating blind; a company that games its measurements believes it can see and is looking at a false picture, which leads it to act on a reality that does not exist and ignore the one that does. The gamed reading produces false confidence — the problem looks addressed or absent when it is neither — which is exactly the false confidence that skipping the diagnosis produces, arrived at by a different route. Whether you skip the reading or game it, you end up with a comfortable false picture and an unaddressed real problem, and the gamed reading is arguably worse because it wears the appearance of rigour. Gaming the reading destroys the thing it measured by replacing the truth with comfort, which leaves the truth unaddressed and disguised.

An honest bad reading is a gift to the team

The reframe that makes bad readings bearable is recognising that an honest bad reading is a gift to the team, not a judgment on it. The reading has identified something real that is holding the team back, while there is still time to address it — which is the most useful thing anyone could do for the team, far more useful than a comfortable reading that let the problem persist unexamined. A team that receives an honest bad reading has been handed the specific thing it needs to improve; a team that receives a softened one has been denied it. The honest bad reading serves the team; the softened one betrays it, however kind the softening felt.

This reframe matters because it changes the emotional valence of the bad reading from threat to help, which is what makes it possible to receive it well. A leader who understands that the honest bad reading is the useful one, the one that lets the team actually improve, can receive it as the gift it is rather than the judgment it feels like — and can resist the temptation to soften it, because softening it would be discarding the help. This is the mindset that makes measurement work: treating the bad reading as valuable information about how to help the team, not as a verdict to be managed. A company that holds this mindset gets the full value of measuring, because it can receive and act on the bad readings that are where the value lives. The honest bad reading is the team's best chance to improve, which is exactly what a gift to the team looks like.

Acting on it is what completes the measurement

Receiving a bad reading honestly is necessary and not sufficient; the value is only realised when the reading is acted on. A bad reading that is honestly received and then not addressed is almost as wasted as one that was buried — the team knows the truth and does nothing with it, which converts the measurement into a source of guilt rather than improvement. The point of the bad reading was to enable action, and the action is what completes the measurement: the reading identifies the constraint, and addressing the constraint is what turns the identification into value.

This is why a bad reading should be received not with dismay but with direction — it tells you what to work on next. The right response to a bad reading is to design an intervention for the constraint it identified, run it, and read again to see whether the constraint moved, which is the whole method in motion. The bad reading is the start of that cycle, not the end of a process; it aims the next intervention, which is exactly what makes it valuable. A company that receives bad readings honestly and acts on them systematically improves; a company that receives them honestly and does nothing accumulates accurate knowledge of problems it never fixes, which is its own kind of waste. The measurement is completed by the action, and the bad reading is valuable precisely because it points the action at something real. Receiving it well is the first step; acting on it is what makes the receiving worthwhile.

The reading that is suspiciously good

A useful corollary of all this is that a reading which is suspiciously good deserves scrutiny, not celebration. If every team reads as healthy, every dimension strong, every result favourable, the most likely explanation is not that everything is genuinely fine but that the measurement is not sensitive enough to detect problems, or that the readings are being softened before they surface. A measurement that never brings bad news is broken, and a set of uniformly good readings should prompt the question of whether the instrument is actually working, not the conclusion that all is well.

This runs against the natural instinct, which is to be reassured by good readings and worried by bad ones. In terms of what the readings reveal about the measurement itself, the instinct should be tempered: uniformly good readings can indicate a measurement that has stopped measuring, and the presence of some bad readings is evidence the measurement is real. A company whose team-health readings are all glowing should be less reassured than one whose readings vary, because the varying readings are the ones detecting reality, and the glowing ones may be detecting nothing. The suspiciously good reading is a red flag for the measurement, not a green light for the team — and treating it as reassurance is how a broken, comfortable measurement survives, producing false confidence indefinitely because it never contradicts anyone. Good readings are welcome when the measurement can also produce bad ones; uniformly good readings from a measurement that never comes back bad are a warning about the instrument.

A bad reading is about the state, not the worth

Part of what makes a bad reading feel like a judgment is the conflation of the team's current state with the team's worth or its people's competence — and separating these is what makes the bad reading bearable and useful. A bad reading says the team is currently constrained on some dimension; it does not say the people are bad, the leader has failed, or the team is beyond help. It is a reading of a state, and states change — which is the whole premise of acting on the reading. A team with a bad reading is a team with a fixable constraint, not a team that has been found wanting, and treating the reading as a verdict on worth rather than a description of state is what turns useful information into a threat to be managed.

This distinction matters practically, because a bad reading received as a judgment on people provokes defensiveness, and defensiveness is what drives the gaming and softening. A bad reading received as a description of a fixable state provokes problem-solving, because there is nothing to defend against — the reading is not saying anyone is bad, it is saying something is constrained and can be improved. The reframe from worth to state is what lets a leader receive the bad reading without the defensiveness that would make them soften it, and it is accurate: the reading genuinely is about the team's current functioning, not its people's value. Keeping this distinction clear — a bad reading is about the state, which is changeable, not the worth, which is not in question — is what makes it possible to receive bad readings honestly and act on them, rather than defending against them as if they were accusations. The reading describes a constraint, not a character.

A company that can hear bad news

Whether bad readings survive to be acted on depends on something larger than any individual's response: whether the company can hear bad news at all. In some organisations, bad news is punished — the messenger suffers, the bad reading reflects badly on whoever surfaces it — and in those organisations, bad readings will be softened and buried no matter how well individuals understand their value, because surfacing them is unsafe. In others, bad news is welcomed as useful, and there the bad readings survive to be acted on, because surfacing them is safe. The organisational culture around bad news determines whether measurement can work, because measurement depends on bad readings surviving contact with the organisation.

This connects the whole question of bad readings back to trust at the organisational level. A company where it is safe to surface bad news — where the bad reading is received as valuable rather than punished as a failure — can measure its team health honestly, because the honest readings survive. A company where bad news is dangerous cannot, because the readings get softened before they surface, regardless of how good the measurement instrument is. So building the capacity to measure team health honestly is partly building the organisational safety to surface bad readings, which is the same safety that the dimensions themselves are about. A company cannot honestly measure a thing it punishes people for reporting accurately, which means the ability to hear bad news is a precondition for measuring team health — and building it is inseparable from building the trust that lets any hard truth surface. The measurement works only in a culture that can hear what it finds, which is a culture safe enough to receive bad news as help.

A worked example

A company reads its teams' health for the first time, and one team's reading comes back clearly bad — low trust, poor decision-making, a real constraint on the team. The reading lands on the desk of the leader responsible, who feels it as a judgment and faces the standard temptations: to question the methodology, to soften the result in the report upward, to frame it as a temporary blip, or to quietly not act on it and hope the next reading is better. Every one of these would make the discomfort go away and would waste the reading, keeping the team's real problem in place while disguising it.

The valuable response is the opposite. The leader treats the bad reading as what it is — an honest identification of a real constraint, delivered while there is still time to fix it, which is the most useful thing the measurement could have produced. They act on it: design an intervention for the trust and decision-making constraints the reading found, run it, and read again to confirm it moved. The bad reading, received honestly and acted on, becomes the beginning of the team's improvement rather than a verdict to be managed. Same reading, and the entire difference between a team that improves and a team that stays stuck comes down to whether the bad news was received as a gift to act on or a judgment to explain away. The reading did its job by coming back bad; the value depended on the leader letting it.

Want the bad news, and act on it

A reading that comes back bad is the point of measuring, not a failure of it — it means the measurement worked, detecting a real problem while there is still time to fix it, which is exactly the value measuring was for. The bad readings are where the return lives, because they are the ones that can change something, and the temptations to game, soften, or bury them are temptations to throw away the highest-value information precisely when it is most valuable. Gaming a reading keeps the problem and discards the diagnosis, producing the same false confidence as skipping the measurement entirely.

The discipline is to want the bad news and act on it — to receive an honest bad reading as a gift to the team rather than a judgment on it, and to complete the measurement by addressing what it found. A company willing to receive and act on bad readings gets the full value of measuring; a company that only accepts favourable results is not measuring but seeking reassurance, and it keeps its problems disguised as health. Want the bad news, and act on it, because the entire value of reading a team is the chance to fix what is wrong — and you cannot fix what you were not willing to see, which is exactly what the bad reading, honestly received, finally lets you do.