LEARN. PRACTICE. GROW.Distinguish risk from issue
A risk is uncertain; an issue has already occurred. Define cause, event, and impact, and assign a response owner. After mitigation, residual risk still needs monitoring. The response itself can introduce secondary risks.
Change with evidence
A change request needs integrated assessment: scope, schedule, cost, quality, risk, and benefit. The designated authority decides. After approval, update affected plans. Budget approval and production change authorization serve different purposes.
Guided application
Record a risk as a condition, uncertain event, and objective impact, with an owner and monitoring signals. After mitigation, review residual exposure and new risks created by the response, such as dependency on another supplier. If failure occurs, address the current issue without losing history. An approved change needs reference and communication updates so teams work against the same commitment. In the July 2026 ECO, risk, change, issues, and governance belong to the Business Environment domain. This path’s examples make authority explicit; actual rules must be confirmed within the organization.
Triggers leading to action
A trigger should identify an observable condition and the planned response. If an alternative depends on no confirmation by Friday, absence on that date should produce owner action rather than another silent week. Check state, communicate consequences, and execute or revisit the response through agreed authority. The date passing does not close the risk. Also record response outcome to establish whether exposure actually decreased.
Explicit conditions for response and change
A response rule is useful only if the team can recognize when it applies. Consider a fictional threshold of two consecutive windows with p95 above 120 ms: the sequence 130, 110, 125 does not satisfy that condition, although monitoring remains appropriate. Do not change the threshold after observing the result to justify a preferred decision. If the competent authority has already approved a rehearsed rollback and its trigger occurs, coordinate that response within the existing mandate. An old procedure does not replace a current control whose applicability is confirmed. Also distinguish intent from resolution: requesting access is not obtaining it. Keep the impediment open with an owner, deadline, and impact until evidence establishes the needed condition.
The sponsor requests a database upgrade during the migration weekend. Analyze compatibility, rehearsals, effort, and rollback before committing.
Common pitfalls
Closing risk merely because mitigation ran; implementing change without updating references.
Related topics: Measure value and hand over autonomy · Suppliers, contracts, and acceptance
A useful decision connects evidence, impact, and authority.
Reference: PMP Examination Content Outline · PMP ECO July 2026; DR PMP 2026.5