The Fight I Let Pass

Filed by: D.B. Trench

Field line: A PM who corrects everything teaches the organization to ration attention.

The sentence was wrong.

Not dangerous wrong. Not career-limiting wrong. Not the kind of wrong that walks into launch readiness with a concealed invoice.

Just wrong enough to irritate a PM who had spent the last month watching language get used as bubble wrap.

Stakeholder alignment continues to progress well.

It sat in the steering update between two cleaner facts: security access had been approved, and the vendor environment would open on Monday.

The stakeholder line was soft. Alignment had not progressed well. Two regional leads still disliked the reporting order. Finance wanted a reconciliation note in the pilot pack. Operations wanted the exception view moved higher. Nobody had thrown a chair, which is not the same as alignment.

My first instinct was to correct it.

That instinct has saved projects.

It has also wasted political capital on sentences that did not deserve a full excavation crew.

The team had the decision it needed for the week. The pilot scope was locked. The unresolved preferences were logged as post-pilot review items. No one was using the alignment sentence to hide a launch risk, approve unpaid scope, or move accountability away from the people holding it.

The sentence was soft.

It was not load-bearing.

That distinction matters more than most PMs admit, especially the ones who have recently learned how to write sharper emails.

There is a stage in a PM's development when every vague phrase starts to look like an enemy combatant.

“In progress.”

“On track.”

“Mostly aligned.”

“No major concerns.”

Some of those phrases are traps. Some are just lazy office fog. If you spend the same force on both, the organization learns to hear your precision as noise.

That week, there were two real fights.

The first was a security exception that would block vendor testing if it did not clear by Thursday.

The second was a sprint commitment that assumed one analyst could finish three data-mapping decisions while also supporting UAT and a production issue from the previous release.

Those were worth the sentence.

The alignment line was not.

So I left it alone.

Not because it was accurate. Because correcting it would not change the next operational decision.

Instead, I used the comments section where it mattered.

Two regional reporting preferences remain open and are logged for post-pilot review. They do not change Monday's environment opening or the approved pilot path.

That sentence did the useful work without picking a fight with the decorative fog.

The sponsor did not notice.

The team did.

The analyst asked later why I did not push harder on the alignment wording.

“Because we already had the decision,” I said. “And we need them to listen on Thursday.”

Thursday arrived with the security exception still unsigned.

That was where the sentence had to spend its weight.

Vendor testing cannot begin Monday unless the security exception is approved by Thursday at 3:00 p.m. If approval is not received, the project must either move vendor testing or remove the dependent pilot scenarios from the release path.

That one got the call.

That one got the uncomfortable silence.

That one got the decision.

The alignment sentence stayed soft in the deck. Nobody fixed it. Nobody applauded my restraint. There was no governance medal for not arguing with a paragraph.

But the security exception cleared.

The analyst got help with the mapping decisions.

The team entered Monday with the two facts that mattered most: the environment was open, and the pilot path was not pretending unresolved preferences had disappeared.

Some project records need a fight.

Some only need a boundary.

A PM who corrects everything teaches the organization to ration attention. Use the sharp sentence where the sentence protects a decision, a date, a person, or the record. Let the harmless fog drift past when the work underneath is already protected.

Not every false sentence deserves your political capital.

For the next time your red pen starts warming up:

---

Battle-selection check: Use this when a statement is imperfect, but you are deciding whether it is worth spending political capital.

Spend the sentence when: the wording hides a decision, shifts accountability, masks risk, authorizes work, affects cost/date/scope, or creates future blame.

Let it pass when: the operational decision is already protected, the ambiguity is not load-bearing, and a bigger issue needs attention soon.

Boundary line: “The wording can remain high-level, provided the operational conditions are recorded: [condition], [owner], [date], [consequence].”

Field channel: Get The Dispatch — weekly field notes on which fights deserve the sentence and which ones do not.