The Green Status I Would Not Sign

Filed by: D.B. Trench

Field line: If green needs conditions, write the conditions where the color cannot hide from them.

The draft status update arrived with four green circles and the confidence of a document that had never spoken to testing.

Overall status: green.

Schedule: green.

Scope: green.

Risks: green.

The comments underneath were less relaxed.

Testing had lost six working days. Two vendor defects were still open. The business owner had approved an earlier workflow, not the workflow currently being built. The integration lead had written “manageable” three times, which is usually how a professional asks for help without alarming anyone above Director level.

The update was not exactly lying. It was arranging the truth in a way that made the truth less useful.

The sponsor’s edit was waiting in the margin:

Can we keep this green? Amber will create noise.

I understood the concern. Amber can invite amateur governance. One person asks for a recovery plan. Another asks for “deep dive” slides. Someone who has not read the last three updates begins a sentence with “Help me understand.” Suddenly the PM is managing the reaction instead of the issue.

But green has a cost too.

Green travels upward. Green becomes memory. Green makes next week’s problem look sudden.

Nothing was sudden. It was already sitting in the notes, wearing a nicer color.

I did not argue about the circle first.

A PM who spends every ounce of political capital on every color teaches the organization to stop listening. The point was not to win the paint. The point was to make the assumptions visible.

So I changed the sentence under it.

Overall status is amber pending confirmation of three items: revised test cycle completion, vendor defect closure or acceptance, and business approval of the updated workflow. If these are not confirmed by Friday, the launch date requires a decision: reduce launch scope or accept increased post-launch defect risk.

That sentence made people uncomfortable, which was useful. Not because discomfort is noble. Because the sentence named the actual work.

The sponsor called.

Do we have to say amber?

“No,” I said. “We have to say what green means.”

That did not win the color battle.

The published deck stayed green.

That happens more often than people admit. A PM can write the right sentence and still lose the dashboard. The organization may prefer the color because the color is easier to defend than the evidence.

So the commentary changed instead.

Green is maintained on the basis that recovery evidence is confirmed by Friday. If testing, defects, and workflow approval are not confirmed by then, the project will require a scope or risk decision before launch.

It was not my preferred status.

It was also not a clean green lullaby anymore. This version had a tripwire.

By Friday, one defect had closed. One had not. Testing had recovered four of the six missing days, not six. The business owner finally reviewed the current workflow instead of the historical artifact everyone had been admiring.

The following week, the status moved to amber without surprise.

Nobody got to say the issue had emerged suddenly. It had been in the record while it was still inconvenient.

Sometimes that is the only win available. Not getting the dashboard to tell the whole truth immediately. Getting enough truth into the update that the next soft sentence has less room to stand.

At 3:11, someone tried to change “decision required” to “decision pending.”

I changed it back.

---

Status record check: Use this when the color is politically important but the evidence underneath it is still conditional.

Public line: “Green can stay only if the conditions that make it true are stated in the update.”

Evidence line: “Status depends on confirmation of [test evidence/defect closure/business approval] by [date].”

Break condition: “If not confirmed, [scope/risk/date] decision is required before [event].”

Field channel: Get The Dispatch — weekly field reports for PMs managing the work beneath the official update.