III.6 — Continuous Improvement

III.6 · Last updated: 11/10/2026

Knowledge that flows from the project to the organization

III.6 — Continuous Improvement is the sixth task in the Business Environment domain of the 2026 ECO, and the domain carries 26% of the exam. It has the shortest title in the domain and few enablers:

• Utilize lessons learned
• Help ensure continuous improvement processes are updated
• Update organizational process assets (OPAs)

The three share a direction. Each is concerned with making sure the knowledge produced in the project does not vanish when the project ends, so that the organization is better prepared for the next one. The task therefore looks less at managing today's project better and more at writing what the project leaves behind into the organization.

A task with a short title and three enablers is easy to skip. PMBOK® 8, however, does not confine continuous improvement to one chapter. It spreads the idea across many parts of the book, from the principles and governance to knowledge management and agile iterations, and exam questions usually ask about it in that scattered form, tucked inside a scenario about something else.

A mindset comes first

The Standard treats the subject at the level of attitude. According to the book, adopting a continuous improvement mindset optimizes processes, increases efficiency, and contributes to the maturity of the whole organization, which leads to better project outcomes in present and future endeavors alike (PMBOK® 8, Standard p.43). The same page connects continuous improvement to quality, saying that continuous improvement and waste elimination are foundational to embedding target quality thresholds. These practices help the team refine its processes and use resources better.

The book shows what the mindset looks like in practice elsewhere. A culture of continuous improvement and forward-thinking action lets project managers anticipate challenges, address them promptly, and adjust processes to changing project and stakeholder needs (PMBOK® 8, Standard p.37). The same holds at team level, where a culture of continuous improvement and reflective practice makes sure lessons learned are captured and shared, and grows the team's collective expertise (PMBOK® 8, Standard p.31).

From this angle, "at closure" cannot be the answer to the question of when continuous improvement happens. Closure is only one of the moments when it takes place.

Putting lessons learned to use

The ECO's first enabler goes beyond collecting lessons learned and asks you to utilize them. In PMBOK® 8 that work happens in the Manage Project Knowledge process. The Guide defines it as the process of using existing knowledge and creating new knowledge to achieve the project's objectives and contribute to organizational learning. Its two benefits mirror those two directions: one is drawing on the organization's prior knowledge to improve the project's outcome, and the other is capturing the new knowledge the project creates for the organization's operations and future projects (PMBOK® 8, Guide p.24).

The process's tools include after-action reviews, in-progress postmortems held while the project is still running, storytelling, and retrospectives. Its outputs are the lessons learned register, project management plan updates, and organizational process asset updates (PMBOK® 8, Guide p.25). So all three of the ECO's enablers sit side by side in the inputs and outputs of a single process. The lessons learned register is both an input and an output of that process, and the Guide defines it as the document or repository where knowledge gained during a project, phase, or iteration is recorded to improve the future performance of both the team and the organization (PMBOK® 8, Guide p.123).

The Guide also wants this work planned in advance. Deciding how and when lessons learned and retrospectives will be carried out over the project supports knowledge management, and the project manager also has to set up how historical information and lessons learned will reach this project and the ones after it (PMBOK® 8, Guide p.26). Writing lessons down is not enough on its own, because a lesson nobody can find is a lesson nobody can use.

The knowledge transfer side of the topic, especially the difference between documented knowledge and tacit knowledge held in people's heads, is covered in detail in Domain I under I.7 — Help Ensure Knowledge Transfer. The two tasks draw on the same process and appear on the exam in closely related scenarios.

At milestones and at the end of each iteration

The tools section of the Guide describes the most concrete instrument of continuous improvement. The after-action review (AAR) is defined as a simple, structured process in which participants and those responsible analyze together what happened, why it happened, and how it could be done better. It originated in the US Army and is usually held at the end of a project or after significant milestones (PMBOK® 8, Guide p.145). The review has two components, a diagnostic stage that sets out what went well and what did not, followed by documenting the findings and sharing them with the relevant stakeholders. Because it can also follow a milestone, the AAR is more than a closure tool.

Adaptive projects repeat the same work at the end of every iteration. The Guide lists two separate end-of-iteration activities: holding knowledge-sharing sessions to pass insight and knowledge around the team, and running a retrospective to evaluate the iteration or release and identify lessons learned and improvement opportunities for future work (PMBOK® 8, Guide p.33). That wording makes it plain that the retrospective looks forward.

The success measures of governance point the same way. One of the expected outcomes the Guide gives for the Governance performance domain is that lessons learned and retrospectives are managed throughout the project. The same table includes, as a check item, that lessons are fed into ongoing processes and not just gathered at the end of the project (PMBOK® 8, Guide p.37). Collecting lessons at closure is covered under II.10 — Manage Project Closure.

Updating organizational process assets

The third enabler concerns OPAs, and what candidates most often miss is how broad that concept is. According to The Standard, organizational process assets can include plans, processes, documents, templates, and knowledge repositories specific to the performing organization, depending on the industry, the organization, and its way of working, and they influence how the project is managed. Any artifact, practice, or knowledge of the organization can fall within that scope (PMBOK® 8, Standard p.19). Among the knowledge repositories the book lists is the historical information and lessons learned repository, which holds project records, closure information, and performance information from earlier projects (PMBOK® 8, Standard p.21).

The exam usually tests the concept by contrasting it with enterprise environmental factors (EEFs). The Standard defines EEFs as conditions that the project team cannot directly control but that influence, constrain, or direct the project (PMBOK® 8, Standard p.18). OPAs sit inside the organization and can arise from what a project, program, or portfolio produces (PMBOK® 8, Standard p.17). This task asks you to put that second property to work. By the time a project ends, the organization's templates, processes, and knowledge base should be in better shape than before it started.

Updating OPAs is not the job of one process either. Alongside Manage Project Knowledge, the process for monitoring risks also lists organizational process asset updates among its outputs (PMBOK® 8, Guide p.100), which is how something learned on the risk side reaches the organization's next project.

Improving the processes themselves

The second enabler asks for continuous improvement processes to be kept up to date. The implication is that the way the work is managed is a subject for improvement, alongside the deliverables. The Guide says so openly in its governance section. Feedback loops are built into the governance framework to support continuous improvement, and they make room for periodic reviews, lessons learned, and iterative adjustments to governance practices (PMBOK® 8, Guide p.10). In adaptive teams the same loop runs inside the team. The Guide says these teams drive continuous improvement through iterative planning, shared decision-making, and focused communication, which can lead to successful self-governance (PMBOK® 8, Guide p.34).

The governance framework itself thus stops being a structure that is set up once and left alone; how it is set up is covered in III.1 — Define and Establish Project Governance. When a question describes a process that is not delivering the expected result, the option that reviews and updates the process usually fits this task's logic better than one that simply applies the same process more strictly.

About the citations

Every page number above refers to the PMBOK® Guide, Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked "ECO" separately.

⚠️ PMBOK® 8 contains two separate books in one volume, and their page numbering is independent:

• The Standard for Project Management — cited as Standard p. X
• A Guide to the Project Management Body of Knowledge — cited as Guide p. X

This page cites both books; which number belongs to which book is stated in every citation. The numbers are the books' printed page numbers.

This page describes the book; it does not replace it.