LEARN. PRACTICE. GROW.Prepare a decision someone can make
In a fictional infrastructure project, a window must be confirmed to the supplier before the usual committee meeting. A useful report identifies the required decision, the authorized owner, the actual deadline, and consequences of no decision. If an authorized delegate is available, use that route and retain traceability for the committee. Do not invent approval by silence or change an external deadline only in a document. Also distinguish receipt from acceptance: a “received” message does not prove RUN accepted weekend coverage when the rule requires explicit confirmation. Project status should describe evidence, not the most convenient interpretation for keeping an indicator green.
Create a shared basis during conflict
Two teams can interpret the same failure incompatibly because they use different time zones, criteria, or boundaries. Before assigning responsibility, build a shared timeline and confirm assumptions with those who produced the records. Hierarchical authority does not turn an incorrect sequence into a valid explanation. In stakeholder engagement, confirm availability and mandate, including exception teams, shifts, and regions. A local holiday can turn an apparently complete meeting into a decision missing essential representation. If valid delegation exists, document it; otherwise adjust decision preparation. The shared goal still guides the conversation but does not erase legitimate differences in evidence and responsibility.
Actual capacity and applicable knowledge
One person does not perform two six-hour specialist reviews in parallel merely because a calendar shows simultaneous lines. If the window has ten hours and no authorized substitute exists, two hours of capacity are missing. RUN interruptions can reduce availability further. Replan with the team and make the trade-off between time, capacity, and scope visible while retaining required controls. During knowledge transfer, do not confuse literal repetition with independence. An operator may follow memorized names without understanding component roles. Exercises with controlled variations reveal whether the operator can adapt the procedure, identify a stop condition, and seek help at the right boundary.
Plan recovery backward from the deadline
A window ends at 02:00. After cutover, the plan reserves 20 minutes of validation, ten for decision, and 45 for rollback without overlap. Cutover must finish by 00:45 to preserve those 75 minutes. This is a scenario calculation, not a universal banking rule. If the forecast moves to 01:15, finishing before 02:00 is no longer enough: recovery no longer fits. Present impact and alternatives to the defined authority before consuming the margin. Do not silently reduce testing or recovery time to make the calendar appear feasible. Also confirm whether durations came from a comparable rehearsal or remain assumptions.
Compare costs without counting twice
A forecast must distinguish incurred cost, remaining work, and commitments already included within that work. With EUR 72 thousand incurred and EUR 38 thousand to complete, including EUR 12 thousand of orders not yet incurred, the forecast is EUR 110 thousand. Adding orders again would produce EUR 122 thousand through double counting. In a replacement decision, include avoidable or additional exit and transition costs. If continuing costs another EUR 20 thousand and replacement costs EUR 4 thousand cancellation plus EUR 13 thousand for the new supplier, the future difference is EUR 3 thousand, retaining equal scope and quality in the exercise. Common historical costs remain recorded but do not differentiate those future options.
Read the total and its component groups
An overall rate can change because performance changed, because the mix changed, or both. In the exercise, A moves from nine errors in 900 operations to two in 100; B moves from ten in 100 to 45 in 900. A worsens from 1% to 2%, B improves from 10% to 5%, and the total rises from 1.9% to 4.7%. Do not attribute aggregate movement to every group. Keep denominators, criteria, and populations explicit. Apply the same care to benefits: releasing 80 hours for backlog work creates useful capacity but does not establish cash savings if contracts and payments remain unchanged.
Authority and evidence have conditions
A financial delegation can require both a cost limit and no change in data classification. Meeting only the amount does not authorize ignoring the second condition. Likewise, a request approved for one version in one region does not automatically authorize another version elsewhere. Compare the actual change with the recorded decision. In a pilot, zero failures across 200 operations does not meet a criterion requiring one thousand operations and a complete closing cycle. Incomplete evidence proves neither success nor definitive failure. For risks, two individual probabilities of 10% do not determine the joint probability without dependence information. State the assumption before using the number in a decision.
Summary and application to RUN handover
Before closing a decision, confirm what was observed, what remains assumed, and who can execute its consequences. A license due for renewal after the project needs an owner, access, and a payment mechanism surviving closure. An API retired after delivery can compromise benefits expected over two years; analysis must cover that period. When improving a process, measure the complete flow: reducing approval from four to two days while adding three waiting days increases the total to five. Connect this lesson to integrated planning, quality, benefits, and governance. A useful decision makes its outcome, scope, limits, and next potential review signal clear.
A 01:15 cutover forecast apparently fits a window ending at 02:00 but leaves insufficient time for the required 75 minutes of validation, decision, and recovery.
Common pitfalls
Do not treat receipt as acceptance, released capacity as saved cash, aggregate percentages as group-level proof, or a monetary limit as the entire delegation.
Related topics: Plan with real capacity · Stakeholders, mandates, and cross-team decisions · Scope, value, and observable benefits
Make authority, population, time, and assumptions explicit; decide using evidence matching the promised outcome.
Reference: PMP Examination Content Outline July 2026 · PMP ECO July 2026; DR PMP 2026.7