Lessons Learned Is Not a Therapy Session

Filed by: D.B. Trench

Field line: If the lesson cannot change the next project, it is only a memory with better formatting.

The lessons learned session had pastries.

That was the first warning.

Not because pastries are bad. Pastries are useful when morale has been through equipment testing. But pastries can also signal that the organization would prefer a comfortable ending to a useful one.

The facilitator opened with the usual categories: what went well, what could be improved, key takeaways.

Within fifteen minutes, the board had filled with the traditional harmless nouns.

Communication.

Alignment.

Earlier engagement.

Clearer roles.

Better planning.

Stakeholder visibility.

All true.

All too vague to save anyone next time.

“Communication” did not approve the vendor variation two weeks late. A sponsor did.

“Alignment” did not let three stakeholders approve one requirement while meaning three different products. The sign-off process did.

“Better planning” did not create the testing crunch. The project accepted scope changes after pilot scripts were built and never moved the date.

Generic lessons are where accountability goes to relax.

So I asked for one example under each noun.

Communication about what? Alignment between whom? Earlier engagement with which group? Clearer roles for what decision? Better planning against which constraint?

The board got quieter and more useful.

Communication became:

Vendor date-impact assumptions were not documented before schedule approval.

Alignment became:

Business, finance, and executive users approved the same reporting requirement with different expected outputs.

Earlier engagement became:

Regional night-shift workflow was not included in pilot testing.

Better planning became:

Launch schedule assumed 258 hours of work against 147 confirmed available hours.

Now we had material.

Not feelings. Controls.

Then the official summary came back softened.

Continue to improve communication and stakeholder engagement across future releases.

There it was.

The lessons had been washed and folded.

I did not rewrite the whole summary. That fight would have consumed the afternoon and produced a prettier fog.

I added an appendix.

Six controls. Owners. Where they should appear next time. No adjectives.

Vendor commitments require written assumptions, named resources, reviewed documents, and date-impact conditions before schedule baseline.

Pilot design must include high-volume region, shift coverage, incomplete-record scenarios, and legacy workaround cases before rollout recommendation.

Schedule approval must compare required effort against confirmed available hours before launch readiness date is accepted.

The facilitator thanked me and called it “additional detail.”

Then the final published deck dropped the appendix into the back, after the thank-you slide, where controls go when the organization wants credit for learning without changing the kitchen.

That was not a win.

It was still worth doing.

Three months later, a junior PM found one line in the appendix and used it to challenge a testing assumption on the next release. Not because leadership had mandated the control. Because she had inherited enough smoke to recognize a firebreak.

That did not redeem the lesson.

It only proved the lesson was not completely dead.

A good lessons learned session does not need to be harsh. It needs to be specific enough to change behavior, even if the first version of behavior is only one PM refusing to repeat the same fog.

The test is not whether everyone felt heard.

The test is whether the next project inherits a control instead of a slogan.

For the next debrief where everyone reaches for comfortable nouns:

---

Lessons-to-controls test: Use this when the debrief produces nouns like communication, alignment, engagement, roles, planning, or visibility.

Translate the noun: “What specific event caused this lesson?”

Build the control: “What owner, action, evidence point, or decision rule should exist next time?”

Record line: “Lesson: [specific failure]. Control for next project: [owner/action/evidence point].”

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