Get email alerts on the Continuous Improvement topic
No spam. Unsubscribe anytime.
Committee urges lessons‑learned log and space to record what went right
Summary
Members recommended adding a lessons‑learned section and space in the template for regional teams to reflect on what worked and what didn't so best practices can be applied across projects.
Get email alerts on the Continuous Improvement topic
No spam. Unsubscribe anytime.
Several members told staff the template should capture both negative lessons and successes so the commission can learn what approaches yield better outcomes. Members suggested a short, running narrative and a log that documents significant changes and lessons learned over the course of a project.
"So it sounds like we should perhaps add a heading on lessons learned that can be... a running list of lessons learned," a commissioner said. Troy Haluska added that documenting what "went right" on projects that remain on schedule and budget could help replicate success across other projects.
Staff agreed the committee could use periodic portfolio discussions separate from the quarterly reports to synthesize lessons across projects and to surface recommendations for process improvements.
AI generated
The text on this page is AI generated. Summaries, highlights, analysis, and video transcripts are all produced from the original source material.
AI can make mistakes, so if you spot one, and we will fix it for everyone.
Note: the source content is unaltered by us. Any content source we link to, be it a video, an audio recording, or a document, is presented exactly as its publisher released it. That publisher is usually a government body, sometimes an individual official or another organisation.

