Your project status is Amber. What does that really mean?

What the interviewer is really testing

• Honesty. Do you report what's true, or what's comfortable?
• Ownership. When something is at risk, does your status come with a plan to fix it?
• Judgement. Do you know the moment when you need help from above, and do you ask for it in time?

The weak answer vs the strong answer

Here's the weak answer: "Amber means slightly delayed."

It sounds reasonable, but it tells the sponsor nothing. Delayed by how much? Why? What are you doing about it? And does anyone need to help?

Interviewers want to hear that you use status as a decision tool, not a colour.

What Green, Amber and Red really mean

Here's how I define the three colours, and how I use them.

1. Green: on track, with evidence. We're on track for scope, schedule, cost and quality, and no help is needed. But Green still needs evidence: milestones met, defects under control, risks being managed.
2. Amber: at risk, but recoverable. We can recover with actions the team already controls. Maybe a dependency is late, or defects are trending up. It's a warning, not a failure.
3. Every Amber has a recovery plan. What we're doing, who owns it, and the date we expect to be back to Green. Without that, Amber is just a feeling.
4. Red: we need a decision from above. We can't recover on our own: we need a decision on scope, more budget, more people, or a new date. Red isn't a confession. It's a request for a decision.
5. No watermelon reporting. Green on the outside, red on the inside. Projects rarely go from Green straight to Red. When they do, the status was wrong for weeks. Report early, and honestly.

A real example

Here's a real example. I'll keep the client anonymous.

On a US healthcare payer program, a third-party interface for eligibility files had been reported Green for six weeks. Every week, the vendor said it was "nearly ready".

When I checked the evidence, there was no tested build. So I changed our status to Amber, with a recovery plan. We built a stub so testing could carry on, set up daily calls with the vendor, and agreed a firm date of two weeks for a working build.

That date passed without a build. So I moved the status to Red, and asked the sponsor for a decision: release everything else on time, and phase that interface into the next drop.

The result: the rest of the release went live on time, and the interface followed three weeks later. The sponsor wasn't surprised, because they'd seen it coming for weeks.

After that, we made it a rule on the account: no Amber without an action, an owner and a date, and no Green without evidence.