Watch the status reports on any large program between October and December. Something happens to the colors. Red becomes amber. Amber becomes green. Nothing in the program has changed. The calendar has.
October is when next year's money gets decided. Budgets are being locked, headcount is being defended, year-end reviews are being written. Every program lead knows that a red status in October is not a report. It is an invitation to have the funding cut, the scope questioned, or their name attached to a problem right before bonus season.
So the bad news waits. Not forever. Just until January, when the budget is signed, the reviews are filed, and the same program can be re-baselined as a new year planning adjustment.
Nobody is lying. Everybody is waiting.
I have never met a program lead who set out to deceive an executive. What I have met, in almost every recovery I have taken over, is a team that knew in October and reported in January. The gap between those two months is where most of the damage happens, because it is exactly the window in which the program could still have been fixed cheaply.
The mechanism is quiet. A milestone slips, and the slip is described as re-sequencing. A vendor misses a date, and the miss becomes aligning on timelines. Testing finds more defects than planned, and the go-live date stays where it was, because moving it now would raise questions nobody wants to answer before December.
Four signs the green is seasonal
You do not need access to the team to see it. The status report tells you, if you know where to look.
The color improved but nothing closed. A program that moves from amber to green should have resolved something you can name. If nobody can tell you what closed, the color changed because the audience changed.
Risks are being monitored instead of owned. A risk with a named owner and a date has a future. A risk being monitored has a narrator. When the risk section fills up with monitoring language in the fourth quarter, someone has decided not to escalate until the budget is set.
The go-live is protected by language, not evidence. On track pending vendor confirmation means not on track. Remains achievable means someone already did the math and did not like the answer.
Next year's plan quietly absorbs this year's work. Open the roadmap for next year. If deliverables promised for this December now appear as first quarter items, and nobody called it a slip, the slip already happened. It was just booked in a different year.
Why it costs more than it looks
A three month delay in recognizing a problem is not a three month delay in the program. Every week a team works toward a plan everyone privately knows is wrong, it builds work that will have to be undone. By January you are not fixing the original problem. You are fixing the original problem plus a quarter of decisions made to keep it quiet.
And the budget you just approved was sized for the green version of the program, not the real one. So the first conversation of the new year is a funding gap, which is precisely the conversation everyone was trying to avoid in October.
What to do before you sign the budget
Ask one question in every review this quarter: what would have to be true for this program to be red right now, and how do we know it is not? It is not an accusation. It gives the team permission to say what they already know, in the month when saying it still buys you options.
Then reward the first person who answers honestly. The fastest way to end seasonal green is to show, once and in public, that red in October is safer than red in January.
If you are reading a status report this week and the colors feel too good for the program you know, paste it into the status report translator. It reads the language, not the color.
