Foster continuous improvement
In the app: Project → Closeout → Lessons learned · Project → Meetings (retrospectives)
PMP ECO · Business Environment (26%) · Task B6. Learn as you go, change something because of it, check the change worked, and pass what you learned to the rest of the organisation.
What it is
Continuous improvement is a loop, not a log:
- Reflect regularly: a retrospective at the end of each sprint, phase or stretch of work (in predictive projects too), plus whatever surfaces day to day.
- Capture the lesson: what happened, and why.
- Decide what will change: an action, an owner and a date. If it's real work, put it in the backlog.
- Apply it, on this project if the remaining work can benefit, or in the organisation's processes if it's for the next one.
- Verify it worked, with evidence.
- Share it as an organisational process asset (OPA), so the next project starts from it.
This is the kaizen idea (small, steady improvements) and the plan-do-check-act cycle applied to how the project works. A lesson that's written down but changes nothing hasn't been learned.
Why it matters
- Lessons captured during the project help this project. The next floor, sprint or package benefits. Lessons captured only at close help the next project, if anyone reads them.
- A lesson nobody acts on comes back as an issue. Usually on the same project, a few months later.
- Evidence keeps it honest. "We changed the process" is a claim; "the next slab didn't crack" is a result.
Where you do it in VanillaPM
- Meetings with the type Retrospective record each review.
- Closeout → Lessons learned is the improvement loop:
- tiles: lessons (and how many came from retrospectives), loop closed (applied or verified, out of those that need an action), open loops, in the org library, and the last retrospective;
- the stages: captured → action planned → applied → verified, plus lessons kept for reference;
- Open loops: lessons with no action decided, an action with no owner or date, an action overdue, a task done but the lesson not marked applied, or applied with no evidence;
- each lesson: phase, when it was raised and at which retrospective, the action with owner and date, its task, applied to, evidence, and its copy in the org library.
- Make it a task puts the action in the backlog, assigned to its owner.
- Share with the organisation publishes the lesson to the org library's Lessons learned folder.
Free download: Lessons learned register template (Excel, CSV).
Walked example — Coral Ridge Resort
Coral Ridge has eight lessons: five from two retrospectives (after site & substructure, and after the first three floors of the frame), three from day-to-day work.
Loops that closed:
- Curing covers blew off during night pours (frame retrospective). Wind lifted the sheets on the floor 3 slab and it cracked. Action: weighted blankets and a wind check before every night pour. Applied to floors 4 and 5. Evidence: the floor 4 slab has no shrinkage cracks. Verified, within the project, a week later.
- Sequencing piling around the tides: applied to the sea-wall and jetty pours, verified, and shared to the org library.
- Too few boreholes before tendering the piling: too late for this site, so it went into the organisation's site-investigation procedure and the library, for the next coastal tender.
Loops that didn't:
- Underestimated customs lead time on imports, raised in July. The action (three weeks of customs float on every remaining import, HS codes agreed before shipping) had an owner and a date in August. It wasn't done, and it never became a task. In November, the lifts got stuck at customs (ISS-006).
- Lock brand finishes at design stage, a recommendation raised in May. No action was ever decided. In October, the brand rejected the cladding sample (ISS-004).
Both are now red at the top of the list. The loop is closed on 43% of the lessons that need an action (3 of 7).
The workspace — the theory behind each screen
Every screenshot is the actual sample project, not a mock-up.
1 · The improvement loop at a glance
The theory: continuous improvement. Reflect regularly, act on what you learn, and check that it worked. The measure isn't how many lessons are logged, but how many changed something.

Reading the screenshot: 8 lessons, 5 from 2 retrospectives. Loop closed 43%: 3 of 7 applied or verified. Open loops 2 (red). In the org library 2. Last retrospective 1 Nov 2026. The stages: Captured 1 → Action planned 3 → Applied 1 → Verified 2, and 1 kept for reference. Open loops: Lock brand finishes at design stage (no owner, no action decided, 170 days since it was raised), and Underestimated customs lead time on imports (Farah Karim, action overdue by 100 days).
✅ Do hold a retrospective at the end of every phase or stretch of work, not only at the end.
❌ Avoid counting lessons as progress. Count the changes they led to.
2 · A lesson without an action is just a complaint
The theory: lessons learned register. Each lesson needs a specific action, an owner and a date. Without them it's an observation.

Reading the screenshot: Underestimated customs lead time on imports, Action planned, 1.5 Building Envelope · raised 9 Jul 2026. Action: add three weeks of customs float to every remaining import order-by date, and agree HS codes with customs before shipping · Farah Karim · by 8 Aug 2026. Red: action overdue by 100 days. It still offers Make it a task: it never became work. Below it, Lock brand finishes at design stage, Captured, raised 30 May: no action decided.
✅ Do turn an action into a task the moment it has an owner, so it's planned like other work.
❌ Avoid "lessons" that sit in a register while the same problem happens again.
3 · Applied on this project, and verified
The theory: plan-do-check-act. The change is applied, then checked with evidence. Lessons learned during the project improve the rest of the project.

Reading the screenshot: Curing covers blew off during night pours, What didn't go well, Verified. 1.4 Superstructure · raised 1 Nov 2026 · at Retrospective: frame, floors 1–3. Action: weighted curing blankets and a wind check before every night pour · Imran Hossain · by 8 Nov 2026. Applied to: floor 4 and 5 slabs. Evidence: floor 4 slab: no shrinkage cracks; the blankets held in a 40 km/h wind.
✅ Do write down where the change was made and what showed it worked.
❌ Avoid marking a lesson done because the action was announced.
4 · Into the organisation's process assets
The theory: organisational process assets. Lessons that matter beyond this project go into the organisation's knowledge: its procedures, templates and lessons library.

Reading the screenshot: Too few boreholes before tendering the piling, Applied, from the substructure retrospective. Action: a denser borehole grid before tendering piling; a fixed-price option once the ground is known. Applied to: the organisation's site-investigation procedure. Evidence: published in the organisation library for the next coastal tender. Org library: Lesson: Too few boreholes before tendering the piling.
✅ Do share the lessons the next project needs, while the people who learned them are still
here.
❌ Avoid an archive of every lesson, unsorted. Share the ones that change how work is done.
Best practices & pitfalls
- Do run blameless retrospectives, so people say what really happened.
- Do keep improvement actions small and specific; a big change is a change request.
- Do review open loops in the same meeting that reviews issues and risks.
- Pitfall: a write-only lessons log. If nothing changes, the loop is broken.
- Pitfall: waiting for the closing workshop. By then, half the people and most of the detail are gone.
On the PMP exam
Expect continuous improvement, retrospectives (and agile's inspect-and-adapt), lessons learned throughout the project, kaizen, plan-do-check-act, and organisational process assets. The best answers act on a lesson during the project and update the OPAs, rather than only documenting it at the end. When a team keeps hitting the same problem, the right move is a retrospective and a specific change, not a reminder to "be more careful".