Lessons learned only help when the next project can see them, so capture them while the work is fresh and keep them where you will start next time.
You finish a job, promise yourself you will never quote a kitchen remodel without checking the cabinet lead time again, and three months later you do it anyway. The lesson was real. It just lived in your head, or in a wrap-up email nobody opened twice. This guide covers what lessons learned are, how to capture them in under an hour, and how to keep them in view when the next project begins.
What Are Lessons Learned?
They are the things a project taught you that should change how you run the next one. A 2006 PMI conference paper by Sandra Rowe and Sharon Sikes puts it plainly: lessons learned “are the documented information that reflects both the positive and negative experiences of a project.”
Both halves matter. A lesson can be a mistake to avoid (“we never confirmed who signs off on the copy”) or a practice worth repeating (“the Friday photo update kept the client calm”). Teams that only record what went wrong lose the habits that made a project go well.
You will hear other names for the same idea: a project post mortem, a retrospective, a wrap-up, or an after-action review. The format changes, but the question stays the same: what do we do differently next time? For solo work, the answers often sit right alongside your running project notes, which is a good sign that they belong close to the work.

Why Lessons Get Lost
Writing lessons down takes discipline. Finding them again when they matter is harder, and even large, well-funded organizations struggle with it.
In a 2002 GAO review of how NASA shares project lessons, auditors surveyed every NASA program and project manager. In the prior two years, 43 percent had not submitted a single lesson to the agency’s database, compared with 23 percent who had. Another 27 percent did not know the system existed. And 58 percent said the processes and systems did not let them retrieve the right lessons at the right time, while 53 percent found lessons useful less than a quarter of the time.
One manager described the problem in a line most people will recognize: “It is difficult to weed through all the irrelevant lessons to get to the few ‘jewels’ that you need to find.” Managers also named a simpler barrier, the lack of time to share what they knew.
The PMI paper describes the same pattern at smaller organizations. Its five-step process runs identify, document, analyze, store, and retrieve, and for teams without a defined process it notes that the retrieve step “is rarely used.” So the lesson sits in a folder, technically saved and practically gone. A decision log has the same weakness if nobody can see it, which is why placement matters as much as writing.
When to Capture Them
Most teams wait for the final meeting. The PMI authors warn that on a large project, waiting until the end means “you miss some of the key lessons,” because people forget, and the people who worked on early phases may have moved on.
Three moments work better:
- When it happens. Write one line the day you hit the problem or notice the win.
- At the end of each phase. A five-minute check after design, after the build, after launch.
- At the end of the project. A short session to sort, merge, and decide what changes.
If you already do a weekly review, add one question to it: what did this week teach us? The same paper also suggests starting the conversation early, saying the best time to begin “is during the project kick-off meeting.”
How to Run a Short Session
You do not need a facilitator or a half-day workshop. For a freelancer or a team of five, 45 minutes is enough.
- Book it within a week of finishing. Memories fade fast, and the details are what make a lesson useful.
- Ask everyone the same three questions beforehand. The PMI paper recommends what went right, what went wrong, and what needs to be improved.
- Gather the answers on one page and group duplicates before the meeting starts.
- Talk through each group and agree on what actually caused it. Stay on the process, never on blame.
- Turn each lesson into an action. Instead of “communication was poor,” write “send a written recap after every client call.”
- Name an owner and a place. Decide who changes the checklist, proposal, or template, and where the lesson will live so the next project sees it.
Questions to Ask
- What surprised us, good or bad?
- Where did we lose the most time?
- What did the client ask for that we did not expect?
- Which decision would we make differently, and what did we know at the time?
- What should we keep doing exactly the same way?
- What one change would have saved the most stress?
A Simple Template
A lessons learned template does not need many fields. Each entry can be a short block with:
- Project and date
- What happened (one or two sentences, facts only)
- Impact (time, money, quality, or client trust)
- Lesson (written as a rule for next time)
- Action and owner (what changes, who changes it)
- Where it applies (which kind of project or client)
Here is a made-up example. A freelance web designer finishes a five-page site three weeks late because the client’s page copy arrived after the design was approved. The entry reads: “Copy came in after design sign-off and forced a rework. Lesson: get final copy before design starts. Action: add a copy deadline to the proposal and the creative brief. Owner: me. Applies to every website project.”

Keep the Lessons Where the Next Project Starts
Elizabeth Harrin, writing for the Association for Project Management, sums up the goal: “Doing something differently next time is the ultimate goal.” Her practical advice is to build a “look at lessons from past projects” step into the start of your process, so the lessons are read when they can still change something.
That only works if the lessons are easy to reach. Searching is already a drag for many people. In Microsoft’s 2023 Work Trend Index, 62 percent of respondents said they struggle with too much time spent searching for information. A lesson you have to dig for at kickoff usually stays buried.
Opal is built for that kind of placement. Your workspace is a large grid, like a desk. Keep one document for lessons, written with Opal’s interactive notes, in a fence near where new projects start. When you open a new job, open the lessons document and the new proposal side by side and read the two together. Many people remember where they put something more easily than what they named it, so “the lessons doc at the top right of the desk” is easier to reach than a file name. That is spatial memory doing the work.
When a project wraps, move its fence’s contents into a binder so the active desk stays clear while the history stays close. If your lessons already live in a Google Doc, add it to the desk and edit it from Opal. You can publish a document as a read-only page for a client, and on the Studio and Workshop plans you can share a fence so a collaborator sees the lessons beside the files they apply to. It fits neatly with the rest of your freelancer tools.
Opal is a visual workspace for notes, docs, and files. It does not offer a formal lessons register with approval workflows, tagging rules, or portfolio reporting and metrics. If your organization runs a PMO that analyzes lessons across hundreds of projects, a tool made for that will serve you better. Plans start with Day Desk at $9 per seat per month, or $7 per month billed yearly, and the full list is on the pricing page.

Common Mistakes to Avoid
- Waiting until the end. By then the details are gone. Capture one line when it happens.
- Vague lessons. “Plan better” changes nothing. Write the specific rule you will follow.
- Only the bad news. Record what worked too, or you will drop good habits by accident.
- Blame. People stop sharing when a session starts assigning fault. Focus on the process.
- Filing and forgetting. A lesson nobody reads at the next kickoff was never really learned.
Key Takeaways
- Lessons are what a project taught you, good and bad, written so the next project can use them.
- Finding lessons later is often harder than writing them. In a 2002 GAO survey, 58 percent of NASA managers said they could not retrieve the right lessons at the right time.
- Capture lessons as they happen, at phase ends, and in a short wrap-up session.
- Write each lesson as an action with an owner.
- Keep the lessons where every new project begins, and read them at kickoff.
FAQ
What are lessons learned?
They are the documented knowledge a project gave you, from both what went well and what went wrong, written so future projects can repeat the good and avoid the bad. Most teams capture them during and after a project and review them before the next one starts.
Is it lesson learned or lessons learned?
Both are correct. The plural is the standard term in project management for the practice and the document. Use “lesson learned” for a single item, and “lessons learnt” is the common British spelling.
What are the 5 steps of lessons learned?
A common version, described in a 2006 PMI conference paper, is identify, document, analyze, store, and retrieve. The last step, getting the right lesson in front of the right person at the start of a new project, is the one teams skip most often.
What’s another way to say lessons learned?
Common alternatives include project post mortem, retrospective, after-action review, wrap-up, and project debrief. Agile software teams usually call theirs a retrospective.
When should you hold a lessons learned meeting?
Hold a short session within a week of finishing a project or a major phase, while details are fresh. Add quick notes as things happen, and review past lessons at the next kickoff.
Does Opal have a free plan?
No. Opal’s plans are paid. Day Desk is $9 per seat per month, or $7 per month billed yearly, and Studio and Workshop add more workspaces, items, storage, and fence sharing. Current details are on the pricing page.
Can I use Opal on my phone?
Opal runs in the browser today. You can open it in a phone browser, but the desk is built for a larger screen where you can see a lessons document and a new project side by side. Native apps are on the roadmap and are not available yet.
When is Opal not the right fit?
If you need a formal register with approval workflows, required fields, and reporting across many projects, use a project management tool built for that. Opal fits when you want lessons, notes, and files kept together on a desk where you will see them.
What Opal Is For
- Opal gives your notes a desk: notes, docs, files, and links laid out where you can see them
- Fences that keep each project’s notes, files, and lessons together
- Items you can open side by side, so past lessons sit next to the new plan
- Come back to a project and pick up where you left off without rebuilding context
Guide: Why productivity apps keep failing you
Get the blueprint by email — same one from the lead magnet page. No spam.
