Skip to content
← Insights

The 5 Red Flags of a Failing Program

Programs rarely fail on the day someone finally says so. They fail months earlier, in a status meeting where everyone agreed the report was green and nobody in the room believed it.

By the time a sponsor uses the word "recovery," most of the money is spent and the options are narrow. The warning signs were there the whole time. They were visible and they were explainable, which is exactly why they got explained away. Here are the five that show up most often, and what to do when you spot them.

Red flag 1: The status is green and the dates keep moving

A healthy program has bad weeks. A program that reports green for six straight months while the go-live date slides twice is telling you its reporting is broken. Status colors describe how the team feels about the plan. Dates describe what happened.

Red flag 2: Nobody can name who decides

Ask three leaders who owns the call on scope. If you get three names, or a committee, then decisions are being made by whoever happens to be in the room, or they are sitting unmade. Count the decisions that have been open for more than two weeks. That number tells you more about program health than most dashboards do.

Red flag 3: The risk log has stopped changing

A live risk log gets new entries, closed entries and revised scores. A dead one has the same twelve risks it had at kickoff, all rated medium, all owned by the PMO. When the log goes quiet, risk has moved into hallway conversations, where nobody owns it and nobody tracks it.

Red flag 4: The vendor has gone agreeable

A vendor who pushes back is a vendor who still plans to deliver. When the pushback stops and every request gets "yes, we'll look into it," check the staffing. The senior people you met during the sales cycle rotate off. Change requests start arriving in batches. The vendor has moved from delivering the work to protecting its margin and its paper trail.

Red flag 5: The business has stopped showing up

Sponsors skip steering committee. Subject matter experts send delegates, then stop sending anyone. Testing gets staffed with whoever is free that week. The people who have to live with the outcome have quietly concluded it will not arrive, and they are spending their time where they expect a return.

Takeaway 1: Check the report against evidence every month

Pick three claims from the latest status report and ask for the proof behind each. If the report says integration testing is 80 percent complete, ask to see the test results. If it says a milestone was met, ask what was delivered and who accepted it.

Example: A program reports "data migration on track." The evidence request turns up two successful trial loads out of a planned six, with the other four scheduled into the last three weeks before cutover. The status was accurate by the letter of the plan and useless as a signal. One hour of checking bought the sponsor eight weeks of warning.

Takeaway 2: Measure decision speed

Keep a short list of open decisions, with the date each was raised and the name of the one person who owns it. Review it weekly. Anything older than ten business days goes to the sponsor with a recommendation attached.

Example: A retail systems rollout stalls because store operations and IT disagree on the cutover window. The question sits in meeting notes for five weeks. Once it lands on a decision log with one owner and a deadline, it is settled in four days. The disagreement itself was small. Nobody had been told the call was theirs to make.

Takeaway 3: Have the uncomfortable conversation while it is still cheap

Each red flag has a direct question behind it. Ask the vendor's account lead who rolled off the team last quarter and why. Ask the sponsor what would bring them back to the table. Ask the program manager what the report would say if there were no consequences for writing it.

Example: A sponsor asks that last question in a one-on-one. The program manager answers that the date has been out of reach since the second scope change, and that she said so twice in writing. Both statements check out. The replan that follows costs three months. Finding out at go-live would have cost the program.

What to do this week

One red flag calls for a conversation. Two call for a review. Three or more mean the program is already in recovery, whether or not anyone has said the word, and the right move is an independent look at what is true before more budget goes in.

None of these checks needs a new tool or a new framework. They need someone willing to ask for evidence and then sit through the answer. Most organizations have people who could do it. Few have made it anyone's job.

Start with the program you are least worried about. That is usually the one whose reporting you have stopped questioning.