When Results Slip, Teams Rarely Say Why: Reading the Early Warning Signs

Results rarely collapse without warning

A quarter that misses is almost never the first sign of trouble. It is the point at which the trouble becomes visible to people who were not close enough to see it earlier. In the teams we work with, the sequence is remarkably consistent: something small stops happening months before the numbers move.

The order in which teams usually fail

1. Early signals — people stop asking questions, meetings shorten, small commitments slip.
2. Behavioural signals — absence rises on specific days, a reliable performer starts to withdraw.
3. Output signals — rework increases, deadlines move by a day at a time, one person is holding everything up.
4. The reported result — the number misses.

By the time the result is reported, three layers of evidence have already gone past. The skill is reading them while they are still cheap to act on.

Signal one: the questions stop

A healthy team asks questions: why are we doing this, could we do it differently, who actually owns this. When things are going well that noise is easy to tolerate. Under pressure it is often the first thing suppressed — and the silence gets read as alignment when it is usually resignation.

Signal two: meetings get shorter and quieter

Shorter meetings can look efficient. When the same meetings also lose their friction — fewer disagreements, nobody volunteering for the awkward piece of work — it more often means the team has stopped believing the discussion changes anything.

Signal three: hero dependency

One or two people always "save" delivery. It looks like commitment and is usually a structural failure: work only one person can do, decisions only one person can make. When the hero finally takes leave, the result is not a dip. It is a stop.

Signal four: rising rework

The same work coming back a second time is the clearest early output signal. It is rarely a capability issue. It is usually ambiguous briefs, missing decisions, or a team that has stopped raising the concern at the point where it could still be fixed.

Signal five: absence concentrated on one team

Rising absence on a specific team is not a coincidence sitting next to slipping results — they are usually the same story told twice. People pull back from a situation that has become untenable before the work visibly fails. Read the two together and the explanation is often obvious.

Four questions that explain most misses

1. What changed in the last six months that we did not adjust for?
2. Who is carrying something they were never formally assigned?
3. What decision is being avoided, and by whom?
4. What would this team say if we asked them what will fail next?

The fourth is the highest-yield question and the least asked — usually because leaders suspect they already know the answer.

What makes it worse

Pushing harder is the default response and usually the wrong one: more reporting, more urgency, more oversight. It generates activity without adding capacity, and it suppresses exactly the information you need. People stop raising problems once raising a problem is treated as a performance issue.

Comparing teams publicly, adding dashboards nobody asked for, and replacing one visible person also rarely help. Each treats the symptom you can see and leaves the system that produced it intact.

A reset that works

• Name the situation accurately, without blame. "We are missing delivery, and it is not because people are not trying" is more useful than a motivational speech.
• Separate the causes: capacity, clarity, capability, culture. Teams that try to fix all four at once fix none.
• Re-establish one standard and hold it. Which one you choose matters less than the team seeing it actually enforced for a month.
• Read absence data alongside delivery data. By team, in the same conversation.

Where capability fits

Two capabilities carry most of the recovery: the ability to give clear, direct feedback without it turning into an incident, and the ability to run a short, honest reset conversation that ends in commitments rather than goodwill. Both are trainable in a session or two — and both decay without practice.

Our free workforce health check gives you a quick read on where the structural strain sits. If you want a deeper view of how your leaders behave under pressure, Leadership360 is the assessment we use. Or contact us to talk through what you are seeing.