A situation you may recognize
“Improve communication” appears in every closeout report. It sounds reasonable, but the next team cannot tell which decision, record or meeting should change.
Three practical steps
- Collect examples during delivery, close to the event. Include the context, evidence, consequence and views of the people involved rather than relying only on recollection at the end.
- Separate the observable event from possible causes. Test explanations respectfully, identify contributing conditions and describe a practical action that a future team can implement.
- Assign an owner for changing guidance, templates or procedures. Check whether the change was adopted on the next project and whether it helped.
Who works together
A facilitator supports an open review across disciplines. Contributors explain events; process owners implement improvements; leadership makes room for learning without suppressing accountability.
Illustrative example
Illustrative case: late vendor drawings repeatedly delayed foundations. The lesson specifies a vendor information schedule with interface dates and named reviewers, rather than a general request for earlier communication.
A mistake to avoid
Avoid blame labels and unsupported causal claims. A list of complaints is not an actionable learning record.