PMI change management is the Project Management Institute’s approach to change at two levels. At the project level, a formal change control process governs changes to scope, schedule, and cost. At the organizational level, structured practices help the people affected adopt new ways of working. PMI is the nonprofit professional association behind the PMBOK Guide and the PMP credential, and it treats these two jobs as connected but separate.
This article explains why both matter, how to run the change request process step by step, and how to handle the people side. It also covers which certifications and training fit each path. You get a worked example and a change request template you can copy into your own project.
Lean Six Sigma Experts has helped organizations improve processes since 2011, and the work keeps returning to one point: an improved process only pays off when people adopt it. That is why we treat change control and change management as parts of one discipline.
Why PMI change management matters
PMI change management matters because projects rarely finish as planned. Unmanaged changes are how budgets and schedules drift without anyone deciding they should. A formal process turns "can you just add this?" into a documented decision with a known cost.
Two jobs under one name
The phrase covers two disciplines, and mixing them up is the most common mistake. Change control governs changes to the project itself. Organizational change management governs how people take up the result. PMI covers the first in the PMBOK Guide and the second in its practice guide, Managing Change in Organizations, which it positions as informing portfolio, program, and project management.
| Change control | Organizational change management | |
|---|---|---|
| Focus | Changes to scope, schedule, cost, deliverables | How people adopt new processes, tools, roles |
| Core question | Should we approve this change? | Will people actually use the result? |
| Main tools | Change request, change log, change control board, change management plan | Stakeholder analysis, communication plan, training, reinforcement |
| Typical owner | Project manager and change control board | Sponsor, change lead, line managers |
| PMI source | PMBOK Guide, Perform Integrated Change Control | Managing Change in Organizations: A Practice Guide |
What goes wrong without it
Without change control, scope creeps in through hallway requests, and nobody can say which change caused the overrun. Without people-side management, you deliver a system that works technically and still fails because staff keep using the old spreadsheet. A tool nobody adopts delivers none of the benefits that justified it.
Change control protects the plan, and change management protects the benefits.
How to run PMI-style change control on a project
Run change control by sending every request through one fixed sequence: identify, analyze, document, present, decide, communicate, implement. The PMBOK Guide calls its version Perform Integrated Change Control. It runs from kickoff to project close, so a change in week 2 and a change in week 40 get the same treatment.
The seven steps
Each step has one owner. That is what stops requests from stalling between people.
| Step | What happens | Who |
|---|---|---|
| 1. Identify | Someone raises the change | Any stakeholder |
| 2. Analyze impact | Assess effect on scope, schedule, cost, risk, quality | Project manager and team |
| 3. Document | Record the request, options, and recommendation in the change log | Project manager and team |
| 4. Present | Take the request to the change control board (CCB) | Project manager |
| 5. Decide | Approve, partially approve, reject, or defer | CCB |
| 6. Communicate | Tell affected stakeholders the decision | Project manager |
| 7. Implement | Update plans and do the work | Project team |
The CCB can be one person on a small project or a committee on a large one. The project manager may or may not sit on it. Requests usually fall into three types: corrective action, preventive action, and defect repair.
A worked example
Say you run a 12-week CRM rollout with a $120,000 budget. In week 5, the sales VP asks for a custom reporting module. Your impact analysis shows three extra weeks and $18,000 in extra cost, which is 15% of the budget. The CCB approves the change on one condition: the sponsor releases the extra funds. You log the decision and update the baselines to 15 weeks and $138,000. Everyone now sees the trade-off, and the VP owns the choice.
A change request template
Keep the form short enough that people actually fill it in. These fields cover what a reviewer needs:
Change request ID:
Date submitted / Requester:
Description of the change:
Reason for the change:
Expected benefits:
Impact on scope:
Impact on schedule:
Impact on cost:
Impact on risk and quality:
Options considered:
Supporting documents:
Decision (approve / partial / reject / defer):
Approver and date:
One owner per step and one log for every request is what makes change control work.
How to manage the people side of change
Manage the people side by treating adoption as a deliverable with its own plan, owner, and measures, started at kickoff instead of at go-live. PMI’s practice guide frames this as identifying change elements in your project plans and building strategies to guide the organization through them.
Five practices that carry the work
Most people-side plans reduce to the same five practices:
- Assess the impact. List who changes what, and how much. A new approval step affects a team differently than a new system.
- Secure an active sponsor. The sponsor explains why the change matters and removes blockers. A sponsor who only signs the budget is not enough.
- Plan communication. Write down the message, audience, channel, and timing for each group in a change communication plan.
- Train near go-live. Training given months early is forgotten. Give it close to the moment people need the skill.
- Reinforce. Check usage after launch, fix friction, and recognize people who adopt the new way.
Many teams use the ADKAR model from Prosci (Awareness, Desire, Knowledge, Ability, Reinforcement) as a diagnostic. If people are not using the new process, ask which of the five stages they are stuck at. The answer tells you whether you need better messaging or more training.
Measure adoption with data
A change plan without adoption measures is a hope. Pick two or three numbers before launch, such as the share of staff using the new system weekly, error rates, and cycle time before and after. Our consulting work is engineering-based, so we favor measured results over anecdotes, and the same rule applies here.
Treat adoption as a deliverable, and measure it like one.
PMI change management certification and training options
Project-level change control is built into PMI’s mainstream credentials, so you do not need a separate certificate for it. For the people side, you choose between PMI’s own learning material and credentials from other bodies. Check pmi.org for its current offerings before you commit, since programs change.
Credentials that cover change control
The PMP is PMI’s flagship credential, and change control is part of the project management knowledge it tests. The CAPM is the entry-level option if you are earlier in your career. Both give you the vocabulary used in this article: change request, change log, and CCB.
Training for the people side
For organizational change, you have several routes. PMI’s learning hub includes a change management essentials page for project managers, and its practice guide is the core reference. Outside PMI, the Association of Change Management Professionals offers the Certified Change Management Professional (CCMP), and Prosci offers ADKAR-based practitioner certification.
| Your goal | Good fit |
|---|---|
| Learn project basics, including controlling | Project Management Execution course ($900, about 10 hours online) from Lean Six Sigma Experts |
| Run formal change control on larger projects | PMP |
| Specialize in the people side | CCMP or ADKAR-based practitioner training |
| Tie change to process improvement | Lean Six Sigma Yellow to Master Black Belt training |
If you are new to project work, the Project Management Execution course gives you an overview of initiation, scheduling, and controlling. Lean Six Sigma belt training, online or on-site, pairs well with either path, because it teaches you to prove that a change worked.
Match the credential to the job: PMP for control, a change specialty for adoption.
Common mistakes and a simple starting checklist
The most common mistakes are skipping impact analysis, letting changes bypass the log, and treating communication as an announcement. Each one is cheap to fix once you spot it.
Process mistakes
- Approving changes verbally. If it is not in the change log, it did not happen. Verbal approvals are how a "small" request turns into an unexplained overrun.
- Skipping impact analysis. A yes or no without a cost and schedule figure is a guess. Always attach numbers.
- Making the CCB too big. Large boards slow every decision. Match the board to the size of the project, and let small changes follow a lighter path.
People mistakes
- Announcing instead of communicating. One email at launch is not a plan. Use two-way channels, such as team huddles and question sessions.
- Ignoring resistance. Resistance is information. Ask what people lose under the new process, and address it directly.
- Stopping at go-live. Adoption dips after launch unless someone keeps checking usage and removing friction.
To start this week, create one change log, adopt the request template above, and name a CCB. Then write a one-page adoption plan with three measures.
Putting PMI change management to work
PMI change management comes down to two disciplines. Change control keeps the project plan honest through a documented sequence of requests and decisions. Organizational change management makes sure the people affected adopt what you deliver. Use the seven-step process for the first, the five practices for the second, and choose the credential that matches your role.
If you want help building a change plan for a process improvement effort, or training for your team, reach out to Lean Six Sigma Experts to talk through your situation.