III.6 — Continuous Improvement

III.6 · Last updated: 22/08/2026

Where this task sits

III.6 — Continuous Improvement is the sixth task in the Business Environment domain of the 2026 ECO. The domain carries 26% of the exam.

It has the shortest title in the domain — and only three enablers:

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

All three point the same direction: from the project outward to the organization. This task is less about improving the project itself and more about making sure the knowledge the project produced stays with the organization.

🔴 Do not trust the number

Good news on III.6: the number stayed put, and a "III.6" tag in older material also points at continuous improvement.

But two numbers moved inside the same domain: III.3 is now change control (in older material that number pointed at external business environment changes) and III.4 is now impediments and issues (in older material that number was support for organizational change). For the general shape of this trap, see what changed in the 2026 PMP exam.

This task's own risk is different: it looks small. Three enablers, a short title, and usually two or three questions' worth of space in prep material. So it gets skipped. As the sections below show, PMBOK® 8 does not treat continuous improvement as a separate topic at all — it builds it as a mindset distributed across the whole book, and the exam asks it that way.

Continuous improvement is a mindset, not a task

The Standard for Project Management handles the subject at the level of attitude rather than tooling: adopting a continuous improvement mindset optimizes processes, boosts efficiency, and enhances maturity growth for the whole organization, leading to better project outcomes and overall organizational success for present and future endeavors (PMBOK® 8, Standard p.43).

The same page goes further and ties it to quality: foundational to embedding target quality thresholds is continuous improvement and waste elimination (PMBOK® 8, Standard p.43).

What the mindset buys you is written down too: fostering a culture of continuous improvement and forward-thinking action enables project managers to anticipate challenges, address them promptly, and align processes with evolving project and stakeholder needs, thereby enhancing overall project resilience and success (PMBOK® 8, Standard p.37).

Translated for the exam: the answer to "when does continuous improvement happen" is not "at closure."

Where lessons learned are collected

The ECO's first enabler says "utilize lessons learned." In PMBOK® 8 the address for this is the Manage Project Knowledge process, and it both produces and consumes lessons learned.

Its tools and techniques include knowledge management, information management, after-action reviews, in-progress postmortems, storytelling, and retrospective meetings. Its outputs are the lessons learned register, project management plan updates, and organizational process asset updates (PMBOK® 8, Guide p.25).

So all three ECO enablers sit side by side on a single process's output list.

The Guide covers the planning side too: determining how and when lessons learned and retrospectives will be conducted throughout the project helps support knowledge management. Identifying which information should be collected both during the project and at its closure is essential; additionally, project managers should establish how historical information and lessons learned will be made available (PMBOK® 8, Guide p.26).

That last clause matters: writing the lesson down is not enough — it has to be findable.

After-action reviews (AARs)

The Guide's tools section describes the most concrete instrument of continuous improvement.

After-action reviews are a simple, structured process used to analyze what happened, why it happened, and how it can be done better, by the participants and those responsible for the project or activity. They originate from the U.S. Army and are designed to improve team performance by reflecting on actions taken and outcomes achieved. They are typically conducted at the end of a project or after significant milestones (PMBOK® 8, Guide p.145).

They have two components (PMBOK® 8, Guide p.145):

• Diagnostic process — diagnosing what went well and what did not, identifying both strengths and weaknesses.
• Documentation — findings are documented and shared with relevant stakeholders so valuable lessons are captured and disseminated.

The phrase "after significant milestones" is the distinguishing detail on the exam: an AAR is not only a closure tool.

Retrospectives and knowledge transfer

On the adaptive side the same work runs through retrospectives. Listing what should be done at the end of an iteration, the Guide names two separate activities: facilitate knowledge-sharing sessions to transfer insights and information among the team; and hold retrospectives to reflect on the iteration and/or release, identifying lessons learned and opportunities for improvement in future work (PMBOK® 8, Guide p.33).

That phrase "opportunities for improvement" turns the retrospective from a ceremony about the past into a forward-looking instrument.

The same item appears among the indicators of good governance: lessons learned/retrospectives are managed throughout the project (PMBOK® 8, Guide p.37). Throughout — not at the end.

Making the knowledge stick is a matter of culture. The Standard notes that by promoting a culture of continuous improvement and reflective practice, the project management team helps ensure lessons learned are captured and shared, enhancing the team's collective expertise. This culture drives project success and prepares individuals for more complex functions in future projects (PMBOK® 8, Standard p.31).

Updating organizational process assets (OPAs)

The ECO's third enabler points straight at OPAs — and what most candidates miss is how broad an OPA is.

Per The Standard, organizational process assets may, depending on the industry, organization, and working model, include the plans, processes, documents, templates, and knowledge repositories specific to and used by the performing organization. These assets influence the management of the project. OPAs may include any artifact, practice, or knowledge from the performing organization (PMBOK® 8, Standard p.19).

The asymmetry here gets tested: EEFs influence the project but the project cannot change them; OPAs are updated by the project. This ECO task asks for exactly that update direction — when the project ends, the organization's templates, processes, and knowledge repository should be better than they were.

What gets improved may be the governance itself

The most overlooked target of continuous improvement is the framework running the project.

The Guide writes it into the governance section: to help ensure continuous improvement, feedback loops are incorporated into the governance framework, allowing for periodic reviews, lessons learned, and iterative adjustments to governance practices (PMBOK® 8, Guide p.10).

So governance is not set up and left alone; it is itself subject to continuous improvement. The same logic applies to change management — for how what you learn during a project reshapes the process, see III.3 — Manage and Control Changes.

Translated for the exam: the right response to "the process is not working" is not to keep applying the process, it is to update it.

About the citations

The page numbers above refer to the PMBOK® Eighth Edition (PMBOK® 8); references to the 2026 ECO are marked as "ECO."

⚠️ 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 explains the book; it does not replace it.