What good looks like: signals of operating health

Every CPO I have worked with has a dashboard, and most of them are green. Engagement score, eNPS, attrition by cohort, time-to-hire, the lot. When I have actually scored those same functions for operating reality rather than survey sentiment, the base rate has been ugly: of eleven I put through a real readiness assessment, not one came in above seventy. Green on the board, failing underneath. The signals of operating health you can trust are conversational, and they move long before any of those numbers do.

Why a green dashboard tells you nothing about operating health

Green dashboards and dying organisations coexist because the dashboard runs on a delay. It reports what already happened, aggregated across a quarter, smoothed by whoever wrote the query. By the time attrition ticks up in the numbers, the decision to leave was made months earlier, in a one-to-one nobody in leadership sat in on. The dashboard is a lagging indicator wearing a leading indicator's clothes, and the gap between the two is where the damage lives.

This is the same trap as mistaking the plan for the operating reality. The chart is a representation of the organisation, produced on a schedule, and like any representation it is most confident exactly where it is most out of date. If you want the difference laid out properly, the difference between strategy and operating reality is the piece that does it. For the purpose of reading health, the point is narrower: a metric can only tell you about a state it has already been given the vocabulary and the time to measure. Operating health fails faster than any of your metrics are built to notice.

So the honest answer to "is this organisation healthy" is not on a screen. It is in a room, in the way a team talks about the thing that just went wrong.

The real signal is language

The real signal lives in language, and specifically in how a team describes a failure it owns.

Sit in on a retro at a healthy team and you will hear specifics. "We shipped the pricing change without checking the enterprise contracts. That is on me. Here is what we are doing differently next sprint." Named owner, named mistake, named fix. Nobody flinches, and the conversation moves on in ninety seconds because there is nothing left to hide.

Sit in on a retro at an unhealthy team and you will hear the passive voice doing the hiding. "Mistakes were made in the rollout process." "There were some communication gaps." "It was not fully clear who owned that." Nobody is named. Nothing is specific. The conversation stretches, because everyone is quietly negotiating how much truth is safe to put on the record, and that negotiation is the tell. You are watching people manage risk to themselves, not manage the problem.

"I approved that migration without a rollback plan" and "the migration process lacked a rollback plan" describe the same event. One of them names a person who can change their behaviour next time. The other has been laundered of ownership, and an organisation cannot fix what it will not attach a name to. This is why you cannot survey your way to the answer. Ask people directly whether they feel safe admitting mistakes and you will get the reply they think you want, which is itself a measurement of how unsafe it actually is.

Here is the play, and you can run it this afternoon. Pull your last five retro documents, or sit in on the next five live, and count two things. First, how often a specific name attaches to a specific decision. Second, how often the write-up reaches for a passive construction to describe what broke. You are looking for a ratio, not a verdict on any single line. A healthy function runs maybe four named owners to every laundered sentence; a sick one inverts it, and the worst I have read produced five pages of incident review without a single first-person "I". The documents were immaculate and told me nothing, which was the finding. When the vocabulary is that uniformly careful, you are not reading a record of what happened. You are reading a record of what people were willing to be seen to have written.

Where bad news travels is the diagnostic

The second signal is direction. Watch where a problem goes when someone first spots it.

In a healthy organisation, a junior engineer who finds a production bug tells the on-call channel immediately, in public, because the cost of speaking up is lower than the cost of staying quiet. In an unhealthy one, that same engineer tells their manager privately first, and the manager decides whether and how it gets escalated. If bad news only ever travels upward through the formal reporting line, and never sideways or downward, you are not seeing most of the real problems in your organisation. You are seeing the subset that survived a filtering process built to protect careers, not to fix things.

You can read this without sitting in a single meeting, just by knowing where to look and what each venue tends to reveal.

None of these is a survey. Each is a place where the organisation is already telling you the truth about itself in the vocabulary it uses, if you go and listen rather than wait for the quarterly roll-up. Reading an organisation this way, at the level of the actual conversation, is the whole discipline. It is what the quiet discipline of operating leadership is built around, and it is a skill you get better at by doing it deliberately, not by buying a better tool.

The one number worth tracking

If you want a single quantitative proxy for all of this, and I understand the itch, use mean time from an incident to an honest, public write-up. Not time to fix. Time to a document that names what happened, in plain language, without softening the ownership.

Track it across your engineering incidents, your lost deals, your failed launches, whatever the equivalent is in your function. A healthy organisation gets from "this went wrong" to "here is exactly what happened and why" in hours or days. An unhealthy one takes weeks, if it ever produces the document at all, because the write-up has to pass through a legal-adjacent instinct to protect reputations before it protects information.

This beats an engagement score for one plain reason: it measures what people did, not what they told a survey they felt. You cannot fake a fast, honest write-up culture in a questionnaire. You can only produce one by actually doing it, repeatedly, until it becomes the default instinct instead of a special effort.

One warning. The moment you start tracking this number, someone will want to put it on the dashboard and set a target for it, and the target will teach people to file thin write-ups fast to hit the metric. Watch the substance of the documents, not just the clock. The number is a prompt to go and read, not a replacement for reading.

What breaks when you get this wrong

The failure mode is not dramatic. It is a leader who mistakes the quiet for calm.

A room of forty going silent to that question is not a neutral result. It is a measurement, and it reads far higher than any engagement score would have that quarter. The founder walked out reassured. The information he most needed had been routed around him by people who had learned, correctly, that surfacing it cost more than sitting on it.

That is the whole risk of reading health from the wrong instrument. A dashboard cannot show you a silence. It has no cell for the problem that was never written down. And once bad news has learned to route around you, every metric you do have gets quietly less true, because it is now describing the filtered version of reality that made it upward. Acting on this before it hardens is exactly the art of the operating intervention: you change the incentive that produced the silence, not the individual who went quiet.

How to read the signals of operating health yourself

Do not build a dashboard for this. That would be the exact mistake the whole piece is arguing against, turning a conversational signal into a quantitative one and losing the thing that made it useful. Build the habit of listening instead, and run your own organisation through a short filter this week.

Two of these are about you, not the team, and they are the ones that move the others. Notice, deliberately, whether names attach to decisions or whether the passive voice is doing the hiding for people. When you hear evasive language, do not correct the individual. Look at the incentive that produced it. People go passive-voice when the active voice has cost them something before, and the fix is to change what it costs, not to police the grammar.

And if you are the leader in the room, model it first. The fastest way to get a team naming its own mistakes cleanly is to name yours that way, in front of them, before you ask it of anyone else. Nobody surfaces bad news to a leader who has never publicly owned their own. If you want an outside read on how this looks across one real process, click by click, that is what a Grain Audit does: it reads the operating reality at the level of the actual work, not the summary.

A doctor does not diagnose from the patient's holiday photos. They ask what hurts, and they listen to how the answer is phrased. Operating health gets read the same way, in the room, in the language, months before it shows up anywhere you would think to look. Learning to read it that way is not a soft skill. It is the operating-leadership discipline that decides whether the numbers you eventually see are describing the organisation or only its cover story.