Leading indicators that tell you a project is in trouble

Most projects don't fail suddenly. They drift. Status reports stay green for weeks, then amber briefly, then red, and by the time anyone acts, the only options left are a late delivery, a smaller scope or both.

Status colors are lagging indicators. They reflect what has already happened. To intervene while there's still room to act, you need leading indicators: signals that appear weeks before the schedule visibly slips.

Eight leading indicators of project trouble

1. Scope growing faster than completion

If items are added faster than they're completed, the finish line is moving away. Track scope added since commitment as a percentage. A sustained increase is one of the most reliable early warnings.

2. Completion rate below forecast

Compare items completed per week or sprint with what the forecast assumed. Two or three periods below the assumed rate means the forecast is already wrong. See Delivery forecast accuracy.

3. Dependencies slipping

A dependency on another team that misses its needed-by date predicts a delay, even if the primary team is on track. See Cross-team dependencies.

4. Decisions waiting

Questions to the business owner that stay unanswered for more than a few days slow the team and often signal waning ownership. See Why orphaned projects fail.

5. Risks rising without mitigation

New risks are normal. Risks that rise in likelihood or impact without a mitigation owner are a warning. Watch the trend, not just the count.

6. Key assumptions breaking

Every commitment rests on assumptions: availability of a specialist, a vendor's delivery date, a stable requirement. When one breaks, the commitment is at risk, whatever the current status says.

7. Work in progress climbing

When teams start more items than they finish, work in progress grows, and cycle times lengthen. It's often a sign of blocked work or unclear priorities.

8. The team avoiding the date

Listen for hedged language: "should be fine," "if nothing else comes up," "we're still finalizing." Teams often sense trouble before the data shows it.

Turning indicators into early action

Indicators only help if they trigger a response. Set simple thresholds:

The "act" column should name a specific conversation, not just "monitor closely."

What early action looks like

Acting early gives you options that disappear later:

• Cut scope to protect the date, choosing the least valuable items.
• Move the date with weeks of notice rather than days.
• Add help from another team while there's still time for them to contribute.
• Re-validate the value case. If the project will now cost much more, is it still worth finishing? See Stage gates without bureaucracy.

Make early warnings safe

The biggest obstacle to early warning is culture. If raising a risk leads to blame, people will wait until the risk is undeniable. Leaders can change this by:

• thanking people who raise concerns early;
• responding to warnings with questions, not criticism;
• celebrating avoided problems, not just recovered ones.

How Aizu helps

Aizu's delivery confidence views put capacity and delivery signals next to scope, dependencies and risks, so a commitment can be questioned before it slips. Risks are rated on a five-by-five likelihood and impact matrix and stay visible at the portfolio level, open gate checks show where assumptions need confirming, and delivery evidence from Jira or Azure DevOps keeps the picture current. Related: Tracking project performance.