Minutes That Hid the Decision

Filed by: D.B. Trench

Field line: Minutes do not have to lie to make a decision disappear.

The meeting ended with three people saying “good discussion.”

That should worry any PM with a pulse.

Good discussion is what people say when the conversation used energy but did not produce a decision sturdy enough to carry into the next week.

The topic was launch scope. The project had two reporting features left, one unresolved approval, and a testing window already holding its breath.

The sponsor needed to choose: keep both features and move the date, cut one feature and protect the date, or keep everything and accept a launch risk that would not look good under fluorescent lighting.

Nobody wanted the third option written down.

That made it the option most likely to happen by accident.

The draft minutes arrived the next morning:

The team discussed launch scope and agreed further alignment is required. PM to coordinate next steps.

A beautiful little burial.

The decision had not been made. The options had not been preserved. The risk had been turned into a calendar task. The words further alignment were doing the work of a small disposal truck.

I sent the correction.

For accuracy, please revise to show that no launch-scope decision was made. Options remain: move launch date and keep both reporting features, remove Feature B and protect launch date, or proceed with both features and accept increased launch risk. Decision required by Wednesday noon to avoid testing impact.

The response was polite.

We want to avoid overloading the minutes with operational detail.

That is one of the great sentences of civilized project damage.

I tried once more.

The final minutes came back softer:

The team discussed launch scope. PM to coordinate next steps and return with recommendation.

The decision had been buried again. Cleaner this time.

There was no dramatic confrontation after that. No brave scene where truth kicked down the conference-room door. The minutes were approved. The file closed around the softer version because the people with authority preferred the softer version.

So I sent a separate decision note to the core team and saved it with the project record.

Operational note: no decision made on launch scope as of Tuesday. Options remain open. Testing impact begins if decision is not made by Wednesday noon. PM recommendation: remove Feature B to protect launch date.

Wednesday noon passed.

Feature B stayed in by drift, not by decision.

Two weeks later, Feature B produced the defect everyone had been trying not to name. The official conversation treated it as new information.

It was not new.

It was just newly expensive.

The decision note did not save the project. It did not force the committee to admit what happened. It did not make the official minutes braver.

It did one smaller thing.

It kept the PM from being alone with a rewritten memory.

A decision note is not a tantrum. It is a backup generator for organizational memory. Sometimes it lights the room. Sometimes it only keeps your own instruments alive.

Both uses matter.

This is not the part where the sentence saves the project. Sometimes it only saves the evidence. For the next time the official record starts sanding the corners off a decision:

---

Decision-note fallback: Use this when official minutes turn an unresolved decision into “alignment,” “discussion,” or “next steps.”

Official minutes may say: “PM to coordinate next steps.”

Backup record should say: “No decision made as of [date]. Options remain [A/B/C]. Impact begins [date/time].”

When it matters: When the same avoided decision returns later as a defect, delay, cost, or “new information.”

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