"Leading versus lagging signals of team health"

A resignation is a lagging signal. By the time it lands on a desk, the team problem that produced it is not new — it has been forming for months, eroding the person's belonging or trust or sense that the team was worth staying for, and the resignation is merely the moment that long process finally became visible. The company experiences the resignation as an event and it is really the endpoint of a deterioration that started long before, in a window when it could have been caught and was not, because the company was watching the lagging signal that arrives at the end rather than the leading signal that moves at the start.

This is the distinction that determines whether team measurement is preventive or merely diagnostic of damage already done. Leading signals — the dimensions of team health — move before the outcomes do, so reading them warns of a problem while there is still time to act. Lagging signals — attrition, missed targets, visible breakdowns — arrive after the underlying problem has already done its damage, so they confirm a problem too late to prevent it. Most companies manage their teams on lagging signals, which puts them in permanent reaction, and understanding why is understanding why so much team management is cleanup rather than prevention.

Lagging signals arrive at the end

The defining feature of a lagging signal is that it is an outcome — the result of a process that has already run its course. Attrition is the outcome of belonging or trust or energy that eroded over months; a missed target is the outcome of a team that has been misaligned or unable to decide for some time; a visible breakdown is the outcome of a dysfunction that built up long before it became visible. In every case, the signal marks the end of a process, not its beginning, which means that by the time the signal appears, the thing that produced it has already happened and can no longer be prevented.

This is what makes managing on lagging signals a permanent exercise in reaction. The signal tells you a problem has fully formed, so your only options are remedial — replace the person who left, recover the missed target, repair the breakdown — rather than preventive, because the window for prevention closed before the signal appeared. A company watching only lagging signals is always responding to problems that have already done their damage, always a step behind, always cleaning up rather than catching. It is not that lagging signals are false; they are accurate and they are late, and their lateness is structural, because they are outcomes, and outcomes come at the end. Reading them is reading the past, which is useful for understanding what happened and useless for preventing it, because it has already happened.

Leading signals move at the start

Leading signals are different in kind: they are not outcomes but causes, and causes move before the outcomes they produce. The dimensions of team health deteriorate before the deterioration shows in the results — trust erodes before the resignation, alignment fails before the missed target, decision-making stalls before the visible breakdown — so a reading of the dimensions catches the problem in its early phase, while it is still forming, before it has produced the lagging outcome. The leading signal moves at the start of the process the lagging signal marks the end of, which is exactly the window in which prevention is still possible.

This is why reading the dimensions is preventive where watching outcomes is merely reactive. A dimension deteriorating is a warning that an outcome is coming, delivered early enough to prevent the outcome by addressing the dimension. A company reading its dimensions sees the trust eroding before it becomes a resignation, the alignment failing before it becomes a missed target, and can act on the cause while it is still cheap to fix, before it compounds into the expensive outcome. This is the whole value of measuring causes rather than results, which what to measure in a team establishes: the causes are leading, so measuring them buys the time that measuring results does not. The leading signal is an early warning; the lagging signal is a late confirmation, and the difference between them is the time to act.

Why companies default to lagging signals

If leading signals are so much more useful, the obvious question is why companies rely on lagging ones, and the answer is that lagging signals are automatic while leading signals must be deliberately read. Attrition announces itself — a resignation is impossible to miss. A missed target announces itself — the number is right there. A visible breakdown announces itself — everyone sees it. These signals arrive on their own, without any effort to detect them, so a company that does nothing deliberate about measurement will still receive them, loud and clear, at the end of the process. The leading signals, by contrast, are silent unless read: a dimension can deteriorate for months without announcing itself, because the deterioration is not visible until it produces the lagging outcome.

So companies default to lagging signals not because they prefer them but because they are the ones that arrive automatically, and reading leading signals requires deliberately building the capacity to read the dimensions before they produce outcomes. This is a real asymmetry of effort: the useless-for-prevention lagging signals come for free, and the valuable-for-prevention leading signals cost the effort of a deliberate reading. A company that does not invest that effort receives only the lagging signals, which means it operates in permanent reaction not by choice but by default — it is watching the only signals it gets without trying, which happen to be exactly the ones that arrive too late. Getting the leading signals requires choosing to read them, which is why prevention requires the deliberate measurement that reaction does not.

The cost of the lag

The lag between the leading and lagging signals is not neutral time; it is the window during which the problem compounds and the damage accumulates. During the months between a dimension starting to deteriorate and the resignation that finally shows it, the problem is not static — it is worsening, driving further deterioration, and often affecting more than the one person who eventually leaves. The lag is the period in which a small, cheap-to-fix problem grows into a large, expensive one, which is exactly the period a company managing on lagging signals cannot see. By the time the lagging signal arrives, the company has lost not just the chance to prevent the outcome but the months of compounding that happened in the dark.

This is why the cost of managing on lagging signals is larger than the cost of the individual outcomes. Each lagging signal represents not just its own damage — the departed person, the missed target — but the whole invisible period of deterioration that preceded it, during which the problem was doing damage the company could not see and could not stop, because it was not reading the leading signal that would have revealed it. The retention math makes this concrete for attrition: the cost of a departure is large, and most of it was incurred in the invisible period before the resignation, when the belonging was eroding unseen. Managing on lagging signals means paying that full cost repeatedly, because it means never seeing the deterioration until it has completed. The lag is where the damage lives, and lagging signals arrive after the lag is over.

Leading signals turn management preventive

The practical effect of reading leading signals is that it turns team management from reactive to preventive, which is a fundamental change in what management can do. A company managing on lagging signals can only respond to problems that have fully formed; a company reading leading signals can prevent problems before they form, by acting on the deteriorating dimension before it produces the outcome. This is the difference between a company that is always recovering from team problems and one that rarely has them reach the outcome stage, because it catches and addresses them upstream.

This preventive capability is the real return on measuring the dimensions, and it compounds. A company that consistently catches problems in the leading-signal window prevents a steady stream of lagging outcomes — the resignations that do not happen, the targets that are not missed, the breakdowns that do not occur — none of which are visible as events, because prevented problems leave no trace. This is why the value of leading signals is easy to underestimate: its payoff is the absence of outcomes, which is invisible in a way that the outcomes themselves are not. But the absence is real and large: a company managing on leading signals is not just responding faster; it is preventing the problems a lagging-signal company spends its time recovering from. The shift from lagging to leading is the shift from reaction to prevention, which is the shift from managing the damage to avoiding it.

Using both, in their proper roles

None of this means lagging signals are worthless — they have a role, just not the role of early warning. Lagging signals are the confirmation that the leading signals were read correctly: if a company reads its dimensions, acts on the deteriorating ones, and then sees its attrition and missed targets decline, the lagging signals confirm that the leading-signal-based action worked. Lagging signals are the ground truth against which the leading signals and the interventions are validated, which is a genuine and important role — it is just a role of confirmation after the fact, not of warning before it.

So the right practice uses both in their proper roles: leading signals for early warning and preventive action, lagging signals for confirmation and validation. The mistake is not using lagging signals; it is using them as the primary management signal, which puts a company in permanent reaction because the primary signal always arrives too late. Used as confirmation, lagging signals are valuable — they tell you whether your leading-signal management is actually working, closing the loop between the dimensions you read and the outcomes you care about. This is the same before-and-after logic as Day 14, 30 and 60: the leading signals aim and prevent, the lagging signals confirm, and together they form a complete picture that neither provides alone. Use both, but lead with the leading signals, because the ones that arrive on their own are exactly the ones that arrive too late to act on.

The false comfort of good lagging signals

One of the most dangerous situations in team management is a team with good lagging signals and deteriorating leading ones — because the good lagging signals produce a comfort that is entirely false. A team hitting its targets and retaining its people looks healthy on every lagging measure, so a company watching lagging signals concludes it is fine and directs its attention elsewhere. But the lagging signals are outcomes of past dimension health, and a team can be posting good outcomes from a dimension state that has already begun to deteriorate — the good numbers reflect where the team was, not where it is heading, and the deterioration will show in the lagging signals only later, once it has completed.

This false comfort is how strong teams are lost. A high-performing team's good results reassure everyone right up until the moment the deterioration that was invisible beneath the good results finally produces bad ones — the sudden resignation of a key person, the unexpected miss, the breakdown no one saw coming. It was not sudden; the leading signals had been deteriorating for months, hidden beneath lagging signals that were still good because they lagged. A company reading only lagging signals is most blind exactly where it feels most confident: a strong team with good numbers, whose leading signals it is not reading, can be deteriorating in plain sight and invisibly, because the numbers that would have to go bad to alert the company are the last thing to go bad. The good lagging signal is not evidence of current health; it is evidence of past health, and reading it as current is how the strongest teams deteriorate unnoticed until they break.

Leading signals are quiet by nature

Part of why leading signals get missed is that they are quiet in a way lagging signals are not. A resignation is loud; a deteriorating trust dimension is silent, because it produces no event until it becomes the resignation. This quietness is structural: leading signals are early-stage causes, and early-stage causes do not announce themselves the way completed outcomes do. A dimension can deteriorate substantially while producing no visible event at all, because the events — the resignations, the misses, the breakdowns — are what happen at the end, and the leading signal is by definition before the end.

This is why leading signals require deliberate reading and lagging signals do not: the lagging signal makes noise, and the leading signal is silent until it becomes the lagging signal. A company waiting to be alerted will be alerted only by the lagging signals, because those are the ones that make noise, and it will miss the leading signals entirely, because those make none. Reading leading signals means going looking for something that is not announcing itself — deliberately reading the dimensions to detect a deterioration that would otherwise stay silent until it completed. This is a different posture from waiting for signals to arrive: it is actively reading for the quiet early warning rather than passively receiving the loud late one. The quietness of leading signals is exactly why they must be sought, and exactly why a company that does not seek them operates on the loud signals that arrive too late.

Not every dip is a deterioration

A caution is worth adding, because reading leading signals well means reading them accurately, not anxiously. Dimensions fluctuate — a team's energy dips after a hard push, its alignment wobbles during a change — and not every dip in a leading signal is a deterioration that demands action. Reading leading signals well means distinguishing normal fluctuation from genuine deterioration, which requires reading the trajectory over time rather than reacting to every movement. A company that treats every dip as a crisis will exhaust itself and its teams responding to noise, which is its own failure mode, opposite to the lagging-signal company's but also costly.

The skill is in reading the pattern, not the point. A single low reading might be noise; a sustained downward trend is signal, and telling them apart requires reading the dimensions over time rather than reacting to any one reading. This is why leading-signal management is not the same as anxious over-monitoring: it is calm, trajectory-aware reading that acts on genuine deterioration and lets normal fluctuation pass. A leader who understands this reads the leading signals for direction and persistence, not for momentary position, and acts when a dimension is genuinely deteriorating rather than merely varying. Reading leading signals well is a discipline of pattern recognition, not of alarm — which is what keeps the practice sustainable and distinguishes it from the surveillance-flavoured over-reading that measurement without surveillance warns against.

Building the habit of reading early

The shift from lagging to leading signals is ultimately a shift in habit — from receiving the signals that arrive on their own to deliberately reading the ones that do not. This habit does not form by itself, because the default is to attend to the loud lagging signals that demand attention, and the leading signals will keep being missed until reading them becomes a deliberate, regular practice. Building the habit means establishing a rhythm of reading the dimensions before they produce outcomes, so that the leading signals are seen as a matter of routine rather than only when a lagging signal has already prompted an investigation.

This is the practical work of turning the leading-signal insight into an actual capability. Understanding that leading signals are better is not the same as reading them; the understanding is common and the practice is rare, precisely because the practice requires building a habit against the default of waiting for loud signals. A company that genuinely manages on leading signals has made reading the dimensions a regular discipline, embedded in how it runs its teams, so that deterioration is caught early as a matter of course rather than discovered late as a matter of crisis. The habit is what converts the leading-signal advantage from an idea into a result, and it is the thing most companies that grasp the idea still lack — because grasping that early signals are better does not, by itself, build the practice of reading them early. The advantage belongs to the companies that build the habit, not the ones that merely understand it.

A worked example

A company manages its teams on lagging signals — it watches attrition, delivery, and visible problems, and responds when they appear. One team's best performer resigns, and the company, reading the lagging signal, scrambles to respond: a counter-offer, a backfill search, an attempt to understand what happened. The investigation reveals that the person had been quietly disengaging for months — their belonging had been eroding since a change in the team that the company never saw, because it was not reading belonging, only watching for the resignation that eventually resulted. The lagging signal arrived accurately and far too late to keep the person, because the process that produced it had been running, unseen, for months.

Reading the leading signal would have changed the outcome. A reading of the team's dimensions would have caught the belonging erosion when it started, months before the resignation, in the window when it could still have been addressed — before the person had decided to leave, before the disengagement had hardened, while the connection could still have been rebuilt. Same team, same person, but caught early enough to keep, because the leading signal moved when the problem started rather than when it finished. The company managing on lagging signals lost the person and then reacted; the company reading leading signals would have seen the erosion and prevented the loss. The difference was entirely in which signal the company was watching, and lagging signals are always watched too late.

Read the signals that arrive early

Leading signals of team health — the dimensions — move before the outcomes do, so reading them warns of a problem while there is still time to act; lagging signals — attrition, missed targets, breakdowns — arrive after the damage is done, so they confirm problems too late to prevent them. Most companies manage on lagging signals, not by choice but by default, because those are the signals that arrive automatically, which happen to be exactly the ones that arrive too late. The lag between them is where the problem compounds and the damage accumulates, unseen by a company watching only the outcome.

The discipline is to deliberately read the leading signals — the dimensions — for early warning and preventive action, and to use the lagging signals in their proper role, as confirmation that the preventive action worked. This turns team management from permanent reaction into prevention, which is the real return on measuring the causes rather than the results. Read the signals that arrive early, not just the ones that arrive on their own, because the automatic signals are the late ones, and the whole difference between preventing a problem and cleaning it up is whether you were watching the dimension that moved months before the resignation, or waiting for the resignation itself.