Record Project Lessons Learned

Published on October 5, 2026 QuoteX

How to Record Project Lessons Learned in the Project Management Center

Welcome back to our series on the Project Management Center. So far, we've covered how to log Project Assumptions, track Project Issues, and document Project Key Decisions.

In this final article of the project tracking series, we will focus on PSC Project Lessons Learned.

Capturing lessons learned is a critical part of the project lifecycle. Whether a process went exceptionally well or terribly wrong, documenting these insights ensures that your team (and future teams) can repeat successes and avoid repeating mistakes. Here is how to log a lesson learned using the Project Management Center.

Step 1: Navigate to the Lessons Learned Related List

Begin by opening the specific project record (e.g., Sales Cloud Implementation - Acme Inc).

Click on the Related tab to view the related lists. Scroll down until you locate the PSC Project Lessons Learned section. (You'll notice above it that we have already logged 1 Key Decision regarding the Sprint 1 demos).

To add a new lesson, click the New button on the right side of the "PSC Project Lessons Learned" header (indicated by the red arrow).

Step 2: Fill Out the New Lesson Learned Form

A modal window titled "New PSC Project Lesson Learned" will open. Complete the following fields to document the experience:

1. Title (Required): Provide a concise summary. In our example, we used: "Account for Local Holidays in Sprint Planning".
2. Type: Select whether this was a "Good" or "Bad" lesson. In this case, we selected "Bad" because it resulted in a schedule delay.
3. Lesson Learned Detail: Describe what happened. We wrote: "During Sprint 1 planning, we failed to account for the regional Labor Day holiday week. This resulted in the customer's UAT testers being unavailable on the initially scheduled dates, forcing us to push the Sprint 1 demos back by one week."
4. "Other" Detail: Use this field for a brief, supplementary note if needed (e.g., "Regional holiday calendar was not factored into resource allocation during the initial kickoff.")
5. Suggested Resolution: Document how to prevent this issue in the future. For example: "Implement a mandatory 'holiday check' step during the project kickoff and sprint planning phases. We should request the customer's regional holiday calendar upfront and proactively adjust sprint capacity to account for planned time off."
6. Impact: Describe the outcome. We wrote: "Sprint 1 demos were delayed by one week. Minor timeline slippage on the overall project schedule."

System Information (Right Side):

1. The PSC Project and Currency fields will auto-populate based on the project record you came from.
2. Include on Status Report: Check this box if you want this lesson to be visible on the external status report. (Note: For "Bad" lessons, you may want to keep this unchecked for external reports and only share it internally).

Step 3: Save the Lesson

Once all fields are populated, click the Save button.

You will be returned to the project's Related tab, where the "PSC Project Lessons Learned" related list will now show a count of (1), displaying your new lesson alongside its unique lesson number and type.

Why This Matters

By utilizing the Lessons Learned related list, you create a centralized knowledge base. Instead of insights being lost when a project closes, they are permanently attached to the project record. This allows Project Managers to review past projects and apply those learnings to future implementations, leading to smoother execution and better client outcomes.

Knowledge Article Number: KA-00450