September 8, 2026 · 7 min read
TL;DR: Brainstorming is keyed 4 times in this bank and offered as a distractor 20 times, one of the sharpest negative splits measured across the whole question set. The pattern behind the misses is a single rule: brainstorming loses whenever the project already has the answer recorded somewhere, or whenever the problem has already been diagnosed. It wins at the point where new material genuinely has to be generated and nothing has generated it yet.
Brainstorming reads as collaborative and inclusive, which is why it works so well as a distractor. The exam is not testing whether you value the team's input. It is testing whether you noticed that the work has already been done.
Because the stem usually tells you a plan already exists.
The cleanest case involves a supplier. A project manager discovers a significant quality problem with a key supplier's deliverables, and the stem states plainly that this supplier risk had been identified earlier in the project. Calling an urgent team meeting to brainstorm possible solutions is offered. Keyed is referring to the project's risk register for the predetermined mitigation actions. The explanation gives the reasoning: because this supplier risk was identified earlier, its response was already analysed and approved, so the project manager executes the planned response rather than improvising a new one. Brainstorming, auditing every deliverable, or confronting the supplier all repeat analysis the project has already done and paid for.
The same shape recurs with issues rather than risks. A development team hits a technical obstacle that puts a scheduled delivery at risk. Calling an emergency meeting with all stakeholders to brainstorm solutions is offered. Keyed is recording the problem in the issue log for structured tracking, because a technical obstacle already threatening a delivery date is an issue rather than a risk: it has happened, and what it needs is an owner and a resolution date.
And when the problem has passed beyond your authority entirely, brainstorming is offered again and loses again. A team struggling with compliance requirements has crossed the organisation's tolerance threshold, and the customer contract carries a very high late fee. Brainstorming with the team and working out a solution together is offered. Keyed is escalating to the senior manager responsible for compliance, and the explanation names brainstorming among the responses that are sound for a problem still inside the project manager's control, which this one no longer is.
| What the stem says | Where the answer already lives | Keyed instead of brainstorming |
|---|---|---|
| The risk was identified earlier | Risk register | Execute the planned response |
| A technical obstacle now threatens delivery | Issue log | Record it with an owner and a date |
| The problem has crossed the org's tolerance threshold | Above your authority | Escalate to the accountable manager |
| A member reports no progress for several days | Nowhere; it is private | Hold a one-to-one |
| Ideas have already been collected | Nowhere; they need sorting | Affinity diagram |
Four times, and each one sits at the point where new material has to appear.
Completing a SWOT. Executives present strengths and opportunities in glowing terms while revenue has fallen, and the chief executive asks for a more complete view. Keyed is brainstorming and capturing the organisation's weaknesses and the threats it faces. Half of the analysis exists; the other half has to be generated.
Structuring a stalled risk workshop. A team running risk identification is struggling to generate ideas, and the project manager decides to give them structure. Keyed is asking them to brainstorm around unwanted human behaviour, system behaviour, and ambiguity. The explanation is the useful part: the team is not short of willingness, it is short of structure, because "what could go wrong" is too open a question to answer from a standing start, so the facilitator's job is to supply categories that prompt recall. Note that the distractor here is also a brainstorm, asking the team to brainstorm the qualitative and quantitative risks, which fails because those are analysis categories rather than recall prompts.
Eliciting requirements the last project got wrong. A customer says earlier projects never delivered what they actually needed. Keyed is running a focus group with the customer's experts and brainstorming requirements with them, because the failure was in how elicitation was done, and the fix puts the customer's own experts in the room with a facilitator, using brainstorming to widen the set before it is narrowed.
Getting value from a difficult expert. A user who knows the domain deeply and holds firm views keeps clashing with the team during demonstrations. Keyed is inviting the user into the technical brainstorming sessions, where their expertise can shape the design early. Showing the product early is offered and loses because the explanation points out it is what is already happening, and precisely where the conflict breaks out.
Common trap: brainstorming a problem that has already been diagnosed. Two records make this sting. A team member reports no progress for several days in the daily standup, and running a brainstorming session with the team to find an alternative way to complete the task is offered. It loses to a one-to-one, because several days of reporting no progress in a public forum usually means the obstacle is something the person will not say in front of the team: a dependency on someone senior, a skill gap, a competing demand from their line manager, or something personal. In the second, a team is new, inexperienced and short on capability, and using brainstorming and root cause analysis to get to the heart of the problem is offered. It loses because the stem already named the problem, so there is nothing left to diagnose; the keyed answer builds capability instead. The bank explains these rather than just marking them wrong, and the rule that falls out is worth carrying: brainstorming produces candidates, so it is wasted wherever the candidate is already known.
Tools that operate on ideas rather than producing them.
Working through scope management, a project manager has collected a large number of ideas during requirements sessions and needs to sort them into groups for review and analysis. Brainstorming is offered. Keyed is affinity diagrams, and the explanation is direct: brainstorming and facilitated workshops are how the ideas were produced in the first place, so reaching for either now repeats a step the stem says is already done. Mind mapping is called the near miss, because it does organise ideas but arranges them radially rather than grouping them.
Root cause analysis draws the same boundary from the other direction. An analyst applies a technique that establishes the basic underlying reason behind a variance, a defect or a risk, noting that one reason can sit behind several. Brainstorming is offered and loses, because it generates candidate risks rather than tracing their causes. The explanation also flags that Ishikawa analysis and cause-and-effect diagramming are two names for the same tool, which is the clue that neither can be the single technique the question wants.
When is brainstorming the keyed answer on the PMP exam? When the task is genuinely to generate new material and nobody has generated it yet: identifying risks with structured prompts, completing a SWOT analysis, eliciting requirements with the customer's own experts, or bringing a difficult expert user into design sessions early. It wins at the front of a process, not in the middle of one.
Why is brainstorming wrong so often? Because the exam offers it where a plan, a log or a register already holds the answer. If the risk was identified earlier, the risk register holds the agreed response. If the obstacle has already happened, the issue log is where it belongs. Brainstorming in those scenarios repeats analysis the project has already paid for.
What is the difference between brainstorming and an affinity diagram? Brainstorming produces ideas. An affinity diagram sorts a large number of existing ideas into groups for review and analysis. If a stem says ideas have already been collected, the sorting tool is what is being asked for, and brainstorming repeats a step already done.
Is brainstorming the right response to a team member reporting no progress? No. The bank keys a one-to-one conversation. Several days of reporting no progress in a public forum usually means the obstacle is something the person is unwilling to say in front of the team, and a group ideation session does not make it safe to name.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: The Risk Register: 17 Keyed, 50 Distractors, and the Split Is Whether You Read It or Hide In It and Requirements Elicitation: Which Technique the Scenario Actually Wants. Risk and impediment tasks are mapped on the Business Environment study page.
When is brainstorming the keyed answer on the PMP exam?
When the task is genuinely to generate new material and nobody has generated it yet: identifying risks with structured prompts, completing a SWOT analysis, eliciting requirements with the customer's own experts, or bringing a difficult expert user into design sessions early. It wins at the front of a process, not in the middle of one.
Why is brainstorming wrong so often?
Because the exam offers it where a plan, a log or a register already holds the answer. If the risk was identified earlier, the risk register holds the agreed response. If the obstacle has already happened, the issue log is where it belongs. Brainstorming in those scenarios repeats analysis the project has already paid for.
What is the difference between brainstorming and an affinity diagram?
Brainstorming produces ideas. An affinity diagram sorts a large number of existing ideas into groups for review and analysis. If a stem says ideas have already been collected, the sorting tool is what is being asked for, and brainstorming repeats a step already done.
Is brainstorming the right response to a team member reporting no progress?
No. The bank keys a one-to-one conversation. Several days of reporting no progress in a public forum usually means the obstacle is something the person is unwilling to say in front of the team, and a group ideation session does not make it safe to name.