Delivery risk rarely announces itself. It creeps in through assumptions, dependencies, and quiet blockers. By the time metrics move, the behaviours that caused the movement have been present for weeks or months.
That's the core idea behind finding the reds — the microbehaviours that predict performance drift long before any dashboard catches up. There are dozens of them. But three appear earlier, and more reliably, than the rest. Every delivery leader should know them.
1. An "extra" top priority
Watch what happens to the number of top-level objectives over a cycle. In a healthy team, the number goes down — priorities consolidate, decisions get made, focus sharpens.
In a drifting team, the number goes up. What was three objectives becomes five. What was five becomes eight. Every new initiative arrives with a sponsor explaining why it has to be a top priority "too." Nobody ever kills the old ones — they just quietly slip down the list while still carrying a priority-one label.
This isn't a prioritisation failure. It's a behavioural failure of saying NO. And it shows up weeks before the dashboard turns red.
2. Back-channels to get things done
The official system is meetings, decisions, tickets, reviews. The back-channel is the Slack DM, the quiet phone call, the "can you just sort this out for me" conversation that routes around the process.
A small amount of back-channel activity is normal. A growing amount is a red.
Back-channels appear when the official system is perceived as too slow, too political, or too risky. They feel like heroism. They are actually a leading indicator that the system has lost the trust of the people running work through it. The more back-channels grow, the less the official system tells you about reality — and the harder it becomes to see what's actually happening.
3. No mechanism to say NO
This is the quietest of the three and the most predictive. In teams with healthy focus, NO has a structure: "Not now — the bucket is full." "Not that — the risk is irresponsible." "Not you — another team owns this work."
In drifting teams, NO has no structure. So it doesn't happen. Every request feels urgent. Every idea feels important. Every stakeholder feels entitled to attention. The priority list inflates until the whole thing collapses under its own weight.
If your team cannot say NO in a way that is defensible and repeatable, focus will keep drifting — no matter how many retros you run.
These are the warning, not the problem
None of these behaviours are catastrophic on their own. All of them are predictive. They show up in language, in energy, in consistency, in momentum, in engagement. They are rarely hidden — they are simply unacknowledged.
The goal isn't to eliminate reds. The goal is to surface them early enough that the cost of change is still low. Reds lose their power the moment they become discussable.
The Find the Reds play walks through exactly how to name a red without blame, connect it to impact, invite perspective, and decide the smallest next step. Get the full play with the free IMIRT Playbook.