Key Concepts
Projects are full of small inefficiencies, and unless we make a habit of finding and fixing them, they compound. Continuous improvement is the work of capturing what we learned, updating the way we run projects, and applying the improvements before the next one.
Challenging the process may sound rebellious, and that is a deliberately motivating framing. We should always encourage teams to innovate, grow, and improve. “Continuous improvement” can sound lame or too much like hard work to some people. “Challenge the process” is something I can get behind.
The point of this task is simple: projects are full of small inefficiencies, and unless we make a habit of finding and fixing them, the inefficiencies compound. Every project we run is a chance to learn what works, what does not, and what we should change before the next one. The work has three parts: capturing what we learned, updating the way we run improvements as we go, and feeding what we learned back into the wider organization so the next team does not start from scratch.
3.6.1 Utilize Lessons Learned
When we think about lessons learned workshops for traditional waterfall projects, we often only consider sessions held at the end of the project. Lessons learned reviews should be considered after every project phase. Rather than a single look back at the end of the project, there should be more regularly scheduled events that generate information stored in the lessons learned register.
Lessons Learned Register
The Lessons Learned Register is the document used to record knowledge gained during a project. It is designed so the knowledge can be used in this project and then transferred into the broader Lessons Learned Repository used across all projects in the organization. The information typically captured includes the category and description of the situation, the impact, recommendations, and proposed actions. The register can record successes, failures, challenges, problems, and other content as appropriate
Lessons Learned Repository
At the end of a project or phase, the information from the Lessons Learned Register is transferred into the organizational Lessons Learned Repository. The repository is what makes lessons reusable. A register that lives only inside one project ends with the project. A repository that other teams can search before they start has compounding value: the next team starts from a higher base than the last one did.
Capturing Both Positive and Negative Lessons
Organizations need to capture both positive and negative experiences. People are sometimes hesitant to discuss failures even though there is often more to be learned from setbacks than successes. Project managers can encourage sharing both positive and negative information by not shooting the messenger and by being appreciative and interested in hearing about problems as much as solutions. Be aware of how you react to news from your team; do not condition them to withhold bad news.
Some practical tips for getting the most out of lessons learned sessions:
- Consider multiple sources of lessons. What did we learn from implementing organization strategy, scheduling and planning, vendor management, working with customers, teamwork, conflict management, and other areas?
- Model the desired behavior. Be open and transparent about negative information and errors made on the team to demonstrate it is acceptable to communicate this type of information. “I noticed an error on the status report and am sending it out again” is a small example.
- Record findings in the Lessons Learned Register so they survive past the meeting.
- Use a neutral facilitator, especially when a session covers difficult content. People speak more honestly when the facilitator is not the person whose decisions are under discussion.
- Use consistent templates and storage so lessons are easy to find later.
- Get leadership involved to help embed the knowledge across the organization. Without leadership engagement, lessons rarely change behavior outside the team that captured them.
Retrospectives
Agile approaches swap out end-of-phase and end-of-project lessons learned reviews for much more frequent retrospectives that occur every sprint or iteration. The retrospective is a workshop that captures insights similar to a Lessons Learned Review. At a minimum, the retrospective asks: What went well? What can be improved? What should we try next?
There is nothing stopping hybrid and traditional projects from adding retrospectives to their planned work. There may not be the same freedom to change process. Some environments are regulated for safety or compliance reasons. Even so, getting together and reviewing what can be improved is usually a valuable and appreciated use of people’s time when the constraints are explained.
3.6.2 Help Ensure Continuous Improvement Processes are Updated
Capturing lessons is the easy part. Acting on them and updating the way the team and the organization work is where most improvement programs stall. The goal of this enabler is to keep the improvement loop itself running well: not just running retros, but acting on what they produce, and updating the improvement process when it is not working.
What Updating the Process Looks Like in Practice
- Adopt a structured change management approach, so process changes are evaluated and rolled out, not just announced.
- Frequently assess and refine governance processes so they continue to fit the project as it evolves.
- Apply lessons learned into planning and implementation activities, so the next phase or release benefits from what we learned in the current one.
- Confirm decisions from retrospectives are visible, owned, and tracked. A retrospective action that nobody is responsible for is not a decision; it is a hope.
Action Wheel
A useful tool for retrospectives and improvement reviews is the Action Wheel. Drawn on a whiteboard, the quadrants are labeled Do More of, Do Less of, Start Doing, and Stop Doing. The format used is less important than confirming we regularly engage the team in ways to improve. Once practical ideas have been suggested, follow through on some experiments. Asking for improvements and then ignoring them is a sure-fire way to disengage people.
Ideas and Experiments Board
Teams can bring better visibility to their improvement ideas and experiments by using boards that show content, progress, and outcomes. An ideas and experiments board treats process improvement the same way the team treats product work: small batches, visible status, and measured outcomes. Some experiments will work and become standard practice; others will not, and we close them out and try the next thing. Both outcomes are valuable as long as we learn from them.
As well as creating better processes for your organization, challenging the process also builds your team’s sense of autonomy. When people help define how they work, they feel a stronger sense of ownership and commitment to it, which is a powerful motivator.
Autonomy, Mastery and Purpose
Daniel Pink, author of “Drive: The Surprising Truth about what Motivates Us,” explains people are motivated by the internal concepts of:
• Autonomy
• Mastery
• Purpose.
Autonomy means giving people control over how they work. Including control over:
- Task – the work they do and how they undertake it
- Time – when they choose to work in the day, week, year
- Technique – How they perform tasks and from where
- Team – How they organize, interact and collaborate
Experiments, retrospectives, lessons learned and challenging the process all contribute to building a sense of autonomy for work.
Mastery describes the pleasure we get from doing what we love and following our passion. We are in the zone, or what Pink calls finding our flow. “Flow” is the term to describe the state of mind when time seems to disappear, and we are just immersed in the task.
Mastery comes from:
Flow – having the time, space and freedom to find and exercise your passion for a profession
Goldilocks Tasks – Not too difficult and not too easy, but just right. We need enough Goldilocks tasks to stretch, engage and indulge our desire for completion and satisfaction.
Mindset of learning – people want to learn new skills and extend their capabilities. When we create learning opportunities at work, people are more motivated.
Purpose describes tapping into people’s belief that there should be more to work than just making money and success. Instead, aligning company goals with individual’s aspirations for doing good and meeting a higher guiding principle.
We may not work for organizations with compelling goals or inspirational objectives. However, we can create a sense of purpose within our teams for delighting customers or surpassing targets. We should not underestimate the motivational effects of developing autonomy, mastery and purpose with our teams. They form more potent motivators than those based on rewards and recognition alone.
Plan-Do-Check-Act (PDCA)
Plan-Do-Check-Act, originally from Shewhart and refined by Deming, is the underlying cycle most continuous improvement methods reach for. Plan an improvement, do it on a small scale, check the result, then act to standardize, adjust, or abandon. The plan-build-demo-retrospective rhythm of an agile iteration mirrors PDCA closely. PDCA also works well overlaid onto traditional and hybrid projects, as long as the team has the authority to actually act on the results.
Kaizen
Kaizen is the practice of continuous, incremental improvement, especially of work processes. The Kaizen mindset assumes that small improvements made consistently outperform occasional large reorganizations. On project work, Kaizen looks like the team adjusting how they run stand-ups, refining the definition of done, tightening the handoff to operations, or removing a redundant approval step. None of these is dramatic. Together they make the next project meaningfully easier to run.
3.6.3 Update Organizational Process Assets (OPAs)
The third part of continuous improvement is the part that survives the project. If lessons stay inside the team and process changes stay inside the project, the organization keeps starting every new project from the same place. Updating Organizational Process Assets is how lessons earned on one project become the starting position for the next.
What Counts as an OPA Update
Anything that changes how the organization runs projects qualifies. Common candidates include:
- Templates for charters, plans, status reports, and closure documents
- Process descriptions for change control, risk management, and compliance reviews
- Definition of Ready and Definition of Done examples for the agile community of practice
- Updated risk checklists and prompt lists, including emerging categories such as IT security and sustainability
- Vendor evaluation criteria and contract templates
- Revised governance reporting formats and escalation thresholds
- Lessons learned entries for the organizational repository
How Updates Get Made
OPAs are usually owned by the Project Management Office. Project teams do not typically have authority to change organizational templates and standards on their own; they recommend changes, the PMO evaluates and updates. The job of the project manager is to make sure recommendations get raised in a form the PMO can act on. That means writing the change clearly: what was the lesson, what change to which OPA does it suggest, what evidence supports the change, and who can validate it.
The discipline is straightforward and often skipped under end-of-project pressure. The teams that do update OPAs are the ones whose lessons end up shaping how the organization runs every project after them. The teams that do not update OPAs see the same problems show up on the next project, and the one after, until somebody finally bothers.
Closing the Loop
Continuous improvement is a loop with three connected parts: capture lessons honestly, update the way the team works, and feed what we learned back into the organization through OPA updates. Each part is useful on its own. All three together is what turns one project’s experience into organizational capability.
Deliverables and Tools
- Lessons Learned Register – The document used to record knowledge gained during a project, including category, description, impact, recommendations, and proposed actions. Captures successes, failures, and challenges as appropriate.
- Lessons Learned Repository – The organizational knowledge base where lessons from the registers of multiple projects are stored and made available to future teams. The mechanism that makes lessons reusable.
- Retrospectives – Frequent workshops at the end of each sprint or iteration that ask what went well, what can be improved, and what should be tried next.
- Action Wheel – A retrospective technique using four quadrants labeled Do More of, Do Less of, Start Doing, and Stop Doing to structure improvement ideas.
- Ideas and Experiments Board – A board that treats process improvement the way the team treats product work: small batches, visible status, measured outcomes.
- Plan-Do-Check-Act (PDCA) Cycle – A continuous improvement cycle from Shewhart and Deming: plan an improvement, do it on a small scale, check the result, then act to standardize, adjust, or abandon.
- Kaizen – The practice of continuous, incremental improvement, especially of work processes. Small consistent improvements compounding over time rather than occasional large reorganizations.
- Organizational Process Assets (OPAs) – The organizational templates, processes, checklists, and knowledge bases that get updated as lessons are learned. The way improvements survive beyond the project.
- Communities of Practice – Cross-project groups where lessons and good practices are shared, often the mechanism by which process improvements are spread.
Related Topics
- 1.3 Lead the project team
- 1.7 Help ensure knowledge transfer
- 2.7 Plan and optimize quality of products and deliverables
- 2.10 Manage project closure
- 3.1 Define and establish project governance
- 3.3 Manage and control changes
- 3.4 Remove impediments and manage issues
- 3.5 Plan and manage risk
- 3.7 Support organizational change
- 3.8 Evaluate external business environment changes
- PMP Mind Map
FAQ
Why bother with continuous improvement?
Small inefficiencies compound across a project unless we make a habit of finding and fixing them.
What does the work involve?
Three parts: capturing what we learned, updating the way we run projects, and applying the changes.
What does challenging the process mean?
Encouraging teams to innovate, grow, and improve instead of accepting how we have always done things.
How does this task fit into the 2026 PMP exam?
Task 3.6 sits in the Business Environment domain of the 2026 Exam Content Outline. The 2026 PMP Exam page has the domain and task breakdown and what changed in the new exam.
Congratulations! You earned the Continuous Improvement badge.