LEARN. PRACTICE. GROW.Distinguish risk, issue, and assumption
A possible delay can materialize when a supplier confirms it will not deliver on time. Record the current situation, assess impact, and assign a response while retaining the original risk link and remaining uncertainty. An assumption is different: it may provisionally support the plan but needs an owner, confirmation deadline, and consequence if false. A monthly maintenance window, for example, is not a commitment merely because it appears in a spreadsheet. Review status using evidence rather than changing only the report color. A record is useful when it enables action and decisions, rather than merely storing descriptions.
Manage change without erasing the baseline
The current forecast and approved baseline answer different questions. The former shows what is now expected; the latter retains the authorized commitment used to assess variance. A request under review is not approval. Present all three with impacts and the needed decision. After a change is approved, update affected elements and confirm teams know the applicable version. If migration sequence changes, revisit dependencies, reservations, tests, and communication. Preserve rationale and relevant previous versions. This discipline also supports adaptive learning: a discovery can change the plan through the agreed process without being hidden or automatically rejected.
Respond to external context and obligations
News about rules, a supplier change, or technology support ending may change the project. Confirm source, applicability, timing, and the competent owner before assuming a specific obligation. Exercise policies are fictional and stated in the prompt; they do not interpret actual banking rules. After confirming a requirement, connect it to deliverables and evidence. A statement that people know the policy does not establish control execution. Also retain exception validity and conditions. If an exception requires reassessment on Friday, a previous good outcome does not automatically extend it into the following week.
Plan change for those doing the work
Technical installation, communication, and adoption are related but distinct outcomes. If the night shift represents 40% of volume and lacks access or practice, global usage of 60% may hide a specific barrier. Observe affected groups and coordinate authorized access, work-relevant training, and follow-up. Reorganization can also change who accepts the service and with which resources. Confirm affected commitments with new owners without automatically invalidating every old decision. Keep channels for hearing difficulties after delivery: dissatisfaction may reveal missing training, unsuitable design, or an unaligned expectation. Investigate before attributing resistance to people.
Evaluate new tools and comparisons
An AI demonstration can produce useful suggestions without proving automatic execution is appropriate. Before changing autonomy, define use, relevant failures, criteria, boundaries, oversight, and response. Ten known examples do not necessarily cover new or contradictory situations. The inspected NIST reference presents a voluntary risk-management approach rather than authorization to use data or change production. The same discipline of explicit conditions helps other comparisons: a consumption-reduction claim needs common boundaries, period, and units. Do not compare isolated servers with a solution including storage and parallel operation as if both measured the same set.
Close the improvement loop
A retrospective action should connect an observed problem to a change, an owner, and an effect review. Define what to measure before the experiment and track adverse consequences. If incidents move from 300 in 10,000 operations to 240 in 4,000, count decreased but the rate doubled from 3% to 6%. This requires investigation rather than an automatic success or blame claim. Retain learning and adapt applicable practices for other projects while respecting contextual differences. Economic calculation is also only part of the decision: reducing expected loss may offset response cost but does not remove mandatory conditions.
Guided exercise: the approved date is 30 November and the forecast moves to 12 December while a change remains pending. Write three committee-report lines distinguishing baseline, forecast, and requested decision. Then prepare the update needed if the change were approved, including dependent plans and owners.
Common pitfalls
Changing a baseline to hide variance; treating technical approval as complete authority; letting exceptions expire without review; labeling missing access as resistance; generalizing demonstration success; declaring improvement from counts across different populations.
Related topics: Stakeholders, mandates, and cross-team decisions · Integrated planning: capacity, dependencies, and forecasts · Governance, risk responses, and adaptation
Credible adaptation requires current information, decision boundaries, and history. Change must reach plans and people, and improvement must be observed under the conditions where it will be used.
Reference: PMP Examination Content Outline July 2026 · PMP ECO July 2026; DR PMP 2026.5