The Project Is Green. Everyone Knows It's Red.
It is Thursday afternoon. You are prepping the monthly portfolio review, and the status board is glowing a comforting shade of green.
Fourteen projects. Thirteen greens. One brave amber that everyone privately respects for its honesty.
Then the finance lead mentions, almost in passing, that the payments migration slipped again.
The CRM rollout has not touched its integration work in three weeks.
And the green data warehouse project is apparently green because the one person who knew it was in trouble left in August.
Welcome to the watermelon portfolio.
Green on the outside. Red all the way through the middle.
This is not usually about people lying.
Most project managers are honest people working under real pressure. The problem is that green is safe. Amber invites questions. Red invites even more questions, usually followed by a recovery plan, an executive meeting, and several people asking when everything will be green again.
So status drifts toward optimism.
Not in one big dishonest decision. One small rounding-up at a time.
"We're probably okay."
"We should make the date."
"Let's give it one more sprint."
Until eventually the portfolio says everything is fine while everyone in the room knows it is not.
A portfolio you cannot trust is worse than no portfolio at all.
At least with no portfolio, you know you are flying blind.
Why honest status is harder than it should be
Status reporting has an incentive problem.
If reporting green means nobody bothers you and reporting amber creates more work, people learn very quickly which color makes their week easier.
That does not make them bad project managers. It makes them human.
There are a few patterns behind most overly optimistic portfolios.
Amber has a social cost. The moment a project turns amber, someone wants an explanation. Then a recovery plan. Then another meeting to review the recovery plan.
"On track" often means different things to different people. On track against the original plan? The current plan? The plan after the scope change nobody formally approved?
The project is usually scoring itself. The same person accountable for success is also being asked to decide whether the work is healthy. That is an awkward position.
And then there is the stickiness of green.
A project that has been green for six months feels strangely difficult to turn amber. Doing so can feel like admitting something went wrong on your watch.
So teams wait.
One more week. One more sprint. One more vendor call.
And eventually amber arrives three days before red.
If you want more honest status, the answer is not telling people to "be more transparent."
You have to make honesty useful.
Stop asking for a color first
One of the simplest improvements is to stop beginning the conversation with:
What color is the project?
Start with the evidence.
For portfolio purposes, status is really asking one question:
Are we still likely to deliver the agreed scope, by the agreed date, within the agreed cost?
That is different from percent complete.
A project can be 80% complete and still be deeply red.
Instead of asking someone to choose green, amber, or red based on judgment alone, ask a few questions that are harder to hand-wave.
- What is the current forecast finish date, and has it moved?
- Has scope changed since the baseline?
- What is the current estimate at completion compared with budget?
- What is the next critical milestone or dependency?
- What is the biggest thing that could knock the project off course?
Now the color has something underneath it.
A green project might mean the forecast date is holding, scope is stable, cost remains within tolerance, and there is no active issue threatening the critical path.
And if the team cannot answer those questions?
Do not automatically make it green.
Make it gray.
Gray simply means we do not know enough yet.
Unknown is not failure.
Pretending unknown is green is.
The payments migration that was never amber
Take Project Atlas, a payments migration.
For four months, Atlas has reported green.
The PM, Dana, is good at her job. The team is working hard. Progress is happening. Nobody is hiding a disaster.
But the problems always feel like next month's problem.
Then the portfolio review looks at the evidence.
The original forecast was March.
Then it became April.
Now it is "late April, probably."
That is three forecast movements in a row.
Two small reconciliation requirements were also added in February and never formally rebaselined.
And the next major milestone depends on a shared integration specialist who is also committed to the CRM rollout during the same two weeks.
None of this requires interpretation.
Those are dates, scope changes, and a real resource conflict.
Green cannot survive contact with them.
Atlas turns amber.
And this is where the organization gets to decide whether status reporting is actually useful.
Dana does not get dragged into a meeting to defend why the project is amber.
Instead, the portfolio review looks at the conflict.
Atlas has a regulatory deadline. CRM has some schedule flexibility.
So the integration specialist goes to Atlas first, and CRM moves by two weeks.
That is a portfolio decision.
A real tradeoff, made while there is still time to make it.
The purpose of amber is not to document failure.
The purpose of amber is to create enough warning that someone can still do something.
If Atlas had stayed green until the resource conflict became unavoidable, the exact same problem would still exist.
The only difference is that leadership would discover it later, with fewer options.
Make amber cheap and hiding expensive
This is the cultural part that no dashboard fixes for you.
Amber and red need to become cheap to report and expensive to hide.
If a PM raises an amber status and immediately gets interrogated, blamed, and given three extra hours of reporting work, do not be surprised when your portfolio stays green.
You trained it to.
An amber should trigger a useful conversation:
What changed?
What help is needed?
Is there a decision the project cannot make on its own?
Does another project need to move?
Do we need to reduce scope?
Do we accept the risk?
That is what a portfolio review is for.
If the only goal of the meeting is to turn the amber boxes back to green, you are not managing the portfolio.
You are managing the dashboard.
Look for trends, not snapshots
One of the easiest ways to spot a watermelon project is to stop looking only at this month's status.
Look at the trend.
A finish date that moved once might be normal.
A finish date that moved in each of the last three reports is telling you something.
A budget that has been revised upward every month is telling you something.
A risk that has been "high" for six weeks with no change in mitigation is telling you something.
A milestone that keeps moving two weeks into the future is definitely telling you something.
The individual snapshot may still look green.
The direction of travel usually does not.
That is why historical status matters.
The question is not only:
Where are we today?
It is also:
Which way are we moving?
Where portfolio software helps
This is one of those areas where tooling can make good behavior easier.
Perspective PPM can keep baselines, forecasts, scoring, shared capacity, risks, and portfolio-level views in one place, making drift easier to see before it becomes a surprise.
It can also help expose things that are difficult to see when every project is reported separately, like multiple projects competing for the same specialist or forecast dates that have been quietly moving month after month.
But the software cannot fix the incentives.
A shared spreadsheet with five honest questions will beat an expensive PPM platform that everyone games.
The tool should make the truth easier to see.
The organization still has to decide that it actually wants to see it.
Fix the next portfolio review
You do not need to redesign your PMO.
Try a few changes in the next review.
First, define green, amber, red, and gray in plain language so everyone is using the same rules.
Then make the status follow the evidence instead of coming before it.
Look at forecast movement over the last few reporting periods, not just the date sitting in the current report.
Pay attention to projects that have been green for a suspiciously long time despite recurring issues.
And when someone brings you an honest amber, help them.
That reaction matters more than any status definition you write.
Because people remember what happens when they tell the truth.
The goal is not a greener portfolio.
It is a portfolio you can believe.