No project goes from green to red in a single reporting cycle. By the time a status report finally admits trouble, the conditions that caused it have usually been in place for months. The warning signs were there. They were simply easy to explain away.
After years of leading delivery and recovering troubled initiatives, I have learned that the most useful signals are rarely in the dashboard. They show up in how people talk, how decisions get made, and what quietly stops happening. Here are ten of the most reliable — and what each one usually says about the system underneath it.
1. The status has been "green" for too long
Complex projects encounter friction constantly. A status report that stays green for months on a multi-year, multi-vendor initiative is not a sign of health. It is usually a sign that reporting has drifted away from reality.
What it usually means: The organization punishes bad news, so it arrives late. Or the metrics being reported measure activity rather than progress toward outcomes.
2. Milestones keep moving, but the end date does not
When interim milestones slip and the go-live date stays fixed, the schedule is absorbing risk silently. That compression has to land somewhere — usually in testing, training, or data conversion.
What it usually means: No one has the authority, or the willingness, to re-baseline. The end date has become a political commitment rather than a planning output.
3. Decisions are waiting on decisions
Open decisions pile up on the RAID log. Workstreams build around assumptions because the answer they need has not come back from leadership, the vendor, or the business owner.
What it usually means: Decision rights are unclear. Governance exists on paper, but it does not have a defined path or a deadline for resolving issues.
4. The same risks appear on every report
A risk register that never changes is not being managed. If the top five risks look identical quarter after quarter, they are being documented, not mitigated.
What it usually means: Risks have owners in name only. There are no trigger points, no response plans, and no escalation when mitigation stalls.
5. Key people are quietly disengaging
The subject matter experts stop showing up to working sessions. The business sponsor delegates the steering committee to a deputy. The vendor rotates its strongest consultants off the account.
What it usually means: People have privately concluded the project is in trouble and are distancing themselves from it. Disengagement is often the most honest status report you will get.
6. Scope is growing without a matching change in time or budget
Requirements expand through small, reasonable-sounding additions. None of them goes through formal change control because each one seems too minor to bother with.
What it usually means: The scope baseline was never firmly set, or change control is seen as bureaucracy instead of protection.
7. Testing keeps getting compressed
Testing is the first phase to lose time because it sits at the end of the schedule. When test cycles shrink from weeks to days, defects do not disappear. They move into production.
What it usually means: The schedule is being protected at the expense of quality. Leadership may not realize the trade being made on their behalf.
8. The vendor and the client describe the project differently
Ask the vendor what is complete, then ask the client team. If the answers do not match, the contract, the acceptance criteria, or the definition of done has gaps.
What it usually means: There is no single source of truth for progress. Accountability is diffused across organizational lines, and each side is managing to its own version of success.
9. Workarounds are becoming the plan
Manual processes, spreadsheets, and temporary fixes start appearing in the cutover plan as permanent features. "We will fix it after go-live" becomes a recurring phrase.
What it usually means: The solution is not meeting core business needs, and the team is masking the gap rather than surfacing it.
10. No one can clearly explain what "done" looks like
Ask five stakeholders to describe success, and you get five answers. Some talk about go-live. Others talk about adoption, cost savings, or compliance.
What it usually means: The project lost its connection to business outcomes. Without a shared definition of done, every trade-off becomes a negotiation.
What to do if you recognize your project
One warning sign is a reason to look closer. Three or more is a reason to act. The good news is that early recognition gives you options that disappear later: re-baselining, resetting governance, or restructuring a vendor relationship are all far easier at month six than at month eighteen.
Start with an honest, independent assessment. The goal is not to assign blame. It is to understand where the project actually stands so leadership can make decisions based on facts rather than optimism.