PMP Choosing the Right Strategy for Handling Project Change

Change strategy matters because not every change should be handled the same way. PMP questions in this area usually test whether the project manager can choose a response path that fits the scale, urgency, value impact, and governance needs of the change instead of applying one rigid rule to every situation.

Strategy Depends on Context

The same project might handle different changes differently:

• a small corrective adjustment may need quick review and local update
• a scope change with cost or schedule consequences may need formal approval
• a regulatory or safety change may need immediate escalation plus controlled analysis
• an adaptive backlog reprioritization may follow product decision rules rather than heavyweight baseline control

The stronger answer usually selects a strategy that is proportionate and still defensible.

    flowchart TD
	    A["Change identified"] --> B["Assess size, urgency, impact, and governance needs"]
	    B --> C["Select handling strategy"]
	    C --> D["Use the right approval, analysis, and implementation path"]
	    D --> E["Communicate the selected strategy clearly"]

Strategy Is Not Just Approval Mechanics

A change strategy may involve more than deciding who approves. It also includes deciding:

• how much analysis is needed
• whether the change should be bundled, deferred, piloted, or split
• how urgently stakeholders must be informed
• whether the current method calls for baseline revision, backlog refinement, or staged rollout

The weaker answer usually either over-controls small changes or under-controls major ones.

Example

A project receives a request to add a small report field and another request to integrate a new external service that affects security review, schedule, and vendor coordination. The stronger move is not to route both requests identically. The project manager should choose a light-touch strategy for the small change and a more formal strategy for the cross-plan change.

Common Pitfalls

• Using the same level of control for every change.
• Treating urgency as a reason to skip the strategy decision.
• Failing to match the strategy to the delivery method.
• Choosing the politically easiest path instead of the most defensible one.

Check Your Understanding

Sample Exam Question

Scenario: A project receives two changes on the same day. One is a small label correction with no cost or schedule impact. The other introduces a new compliance check that affects approval timing, resource availability, and delivery sequence. The sponsor asks the project manager to “just use one standard path for both.”

Question: What should the project manager examine first?

• A. Use the same minimal path for both changes to keep administration simple
• B. Reject both changes because one standard path was requested
• C. Implement both changes immediately and document later
• D. Choose a strategy for each change based on impact, urgency, and control needs

Best answer: D

Explanation: The strongest answer is D because the two changes clearly have different impact profiles. Strong change management chooses a handling strategy that matches the nature of each change rather than forcing every request through identical control intensity.

Why the other options are weaker:

• A: Simplicity alone does not justify weak control on a major change.
• B: Rejecting both skips the actual analysis.
• C: Implementation before strategy selection bypasses governance.

Key Terms

• Change strategy: The chosen path for evaluating, approving, and implementing a proposed change.
• Proportionate control: Applying a level of rigor that fits the impact of the change.
• Handling path: The practical route a change takes from proposal to decision and implementation.