Waiting Is Almost Never the Answer, Except When It Is

TL;DR: Across this bank, answer options that wait, defer, or take no action are keyed 3 times against 50 as distractors. That makes it one of the most lopsided patterns we have measured. But the three keyed cases are not accidents, and they share a feature you can test for: you are waiting on a control or an owner that has to come first, not on the situation to explain itself.

Candidates learn quickly that the PMP exam wants a project manager who acts. Then they meet a question where three options all involve doing something energetic and one says wait, and they discard the wait option on reflex. Usually that reflex is right. Occasionally it throws away the answer, and the difference is not a matter of judgment or feel. It is structural.

We counted it rather than guessing. Options phrased as waiting, deferring, taking no action, continuing to monitor, or doing nothing appear 53 times as answer choices across the 2,141 questions here. Three of them are keyed.

Why is waiting wrong 50 times out of 53?

Because in almost every scenario, the information needed to act has already arrived, so waiting buys nothing and costs time.

Look at what the distractors are actually waiting for. A team's velocity drops in the fifth iteration and nobody knows why, and one option says do nothing because the team has slipped back into storming. Another says do nothing because the first four iterations happened to hold the easier stories. Both are guesses dressed as restraint. The keyed answer works with the team to find the root cause.

That shape repeats. Community leaders send a written letter with three specific objections to a park project's habitat plan; one option waits for the next scheduled stakeholder meeting to raise it. A building-safety act passes that takes effect in seven months; one option waits until it is in force before changing anything. A team member's output has fallen because they were handed a technology stack they have never used; one option waits for them to build proficiency on their own, since ramp-up takes time.

Every one of those is a real thing a busy project manager might do. None of them is keyed. What they have in common is that the information needed to act already exists. The letter lists the objections. The act has a text and a date. The investigation already isolated the skill gap. Waiting in those scenarios does not buy clarity, because clarity has already arrived. It just moves the same decision later, with less time to make it.

Passive acceptance of risk is the same error in a costume. One question describes a team deciding a subcontractor availability risk is worth living with rather than acting on. The distractor takes no action of any kind and deals with it only if the subcontractor becomes unavailable. The keyed answer sets aside a contingency reserve sized to cover a short-notice replacement. Accepting a risk is a decision, and decisions produce work. Doing nothing is what happens when nobody decided.

Common trap: "The activity has float, so the slip does not matter." One bank scenario has a raw material delivery running two weeks late on a non-critical activity, with the contractor offering to cover the cost of running the old system in the meantime. "Do nothing, because the project itself is not being delayed" is offered, and it is a distractor. A committed date moved and money changed hands. Neither of those becomes exempt from change control because the work happened to have slack. The keyed answer raises a change request and takes it to the board. This bank puts that do-nothing option in front of you deliberately, and explains why it fails rather than just marking it wrong.

When is waiting actually the keyed answer?

Three times in 2,141 questions, and the three are worth reading together because they are not random.

The first two are the interesting pair. In both, acting now is not merely hasty, it is illegitimate. The project manager who assigns resources on a verbal go-ahead is exercising authority the charter has not yet granted. The project manager who writes the WBS alone from experience with similar modules produces a decomposition the people doing the work never agreed to, and that WBS is about to become the basis of every estimate on the project. In both cases, moving fast means skipping the thing that makes the next step valid. A week of delay is cheap next to a schedule built on assumptions.

The third is different again and easy to misread. Doing nothing there is not passivity, it is scope discipline. The project delivered what it agreed to deliver, the client signed it off, and installation is a different project. The distractors around it are generous: submit a change request to absorb the installation work, pitch in as a favour, write a separate charter. Two of those are more work than the keyed answer, which is the tell. The exam is not testing whether you will help. It is testing whether you know where this project ends.

So the test to run is not "does this option feel proactive." It is: what am I waiting for, and does it have to come first? A signature that confers authority has to come first. The people who own an estimate have to come first. A stakeholder meeting three weeks out does not, a law taking effect in seven months does not, and a team member spontaneously learning a new stack does not.

FAQ

Is "do nothing" ever the right answer on the PMP exam? Rarely, and never as a way to avoid work. Across this bank, options that wait, defer, or take no action are keyed 3 times against 50 as distractors. The three keyed cases are all situations where acting would be premature or out of scope, not situations where the project manager simply hoped a problem would resolve itself.

What separates a keyed "wait" from a distractor "wait"? Ask what you would be waiting for. If it is a control that has to exist before you can legitimately act, such as a signed project charter, or a person who owns the decision, waiting is the disciplined answer. If it is a future event that will make the problem clearer or someone else's move, it is a distractor.

Why does passive acceptance of a risk usually get marked wrong? Because accepting a risk is a decision that produces work. One bank question has a team decide to live with a subcontractor availability risk; the keyed answer sets a contingency reserve sized to cover a short-notice replacement. "Take no action of any kind and address it only if it occurs" is the distractor sitting right beside it.

Does having float mean I can leave a change undocumented? No. In one bank scenario a delivery slips two weeks, the activity is off the critical path, and the contractor offers to cover the cost. "Do nothing, because the project itself is not being delayed" is a distractor. The keyed answer raises a change request, because a committed date moved and money changed hands.

Try it yourself

PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, and every wrong answer is explained, not just marked wrong, so you learn why the do-nothing option was there in the first place. Start the free 20-question sample. No card, no signup required to try it.

Related reading: Diagnose Before You Act covers the pattern that usually replaces waiting, and Risk Response: Planned vs Unidentified covers what active acceptance looks like in practice. The Process domain study guide sets out where these decisions sit in the 2026 ECO.

Source: PMI, PMP Examination Content Outline.

FAQ