Reading a Delivery Confidence drop correctly
The number going down is not the finding. The factor that moved is the finding.
The most common mistake is treating the score as a verdict and reacting to its direction. A drop of eleven because three items are newly blocked is a different situation from a drop of eleven because someone finally set real due dates.
The second is a scoring artefact of doing the right thing. Read the factors first.
Drops that usually mean act now
Two patterns are worth interrupting your day for:
- A blocker chain where the blocking item is barely started — everything behind it is already late, it just has not shown up as overdue yet.
- Unassigned high or critical work. Five points each is deliberately punchy, because unowned urgent work is the failure that compounds fastest.
Drops that usually mean wait
Stale items right after a holiday, or a review queue that grew because one reviewer was out, will recover on their own. The daily snapshot is what tells you which you are looking at: one bad day is noise, five is a trend.
When the rule is wrong
Sometimes the score is simply wrong about your team — a project where three days without an update is normal will look stale forever. That is a real limitation, not a misunderstanding, and the honest response is to weigh the factor accordingly rather than pretend the number is neutral.
It is a decision aid computed from your data. It is allowed to be wrong; it is not allowed to be unexplainable.