The project was green until the week it wasn't

For eleven weeks I reported green. Every Thursday I filled in the same slide, changed a date or two, and moved on. I was not lying. Each individual thing I knew about looked survivable on its own: a late environment, a firewall change waiting on another team, one engineer stretched across two workstreams, a supplier who had gone quiet.

In week twelve all four arrived at once, and the project went red in a single meeting. What made it painful was not the news. It was that everything in the room had been visible for a month, and I had been the one deciding, quietly and by default, that none of it was worth raising yet.

The reason I kept it green was not dishonesty. It was that each item had a story attached. The environment was late, but the vendor had promised Friday. The firewall change was queued, but the other team said it was routine. Every item had a sentence that made it sound handled, and I told myself the sentence rather than the date.

What I missed is that risk is not a list of items. It is the distance between what you have committed to and what you can currently evidence. That distance had been growing for a month while the status colour stayed still, because the colour measured how I felt about the plan rather than what the plan could survive.

There was also a quieter cost. The people around me had seen the same four things. Because I never named them, they assumed I had a plan they were not party to, so nobody raised them either. Silence at the top of a project teaches everyone below it to stay silent too.

I would report the trend, not the status. Green with three things drifting is not the same as green, and the person reading your report cannot tell the difference unless you say so.

A status report exists to let someone else act in time. If your report would not have changed anyone's behaviour, it was decoration. Say what is drifting, say what you need, and name the date by which the decision stops being cheap.