September 7, 2026 · 6 min read
TL;DR: Requirements elicitation questions are technique-selection questions, and the scenario always names the constraint that picks the technique. In this bank brainstorming is keyed 4 times and offered as a distractor 20 times, the widest margin of any technique measured. Prototypes are keyed when words have already failed, focus groups when you need reactions, and workshops when you need agreement.
Most candidates can recite the elicitation techniques. Interviews, focus groups, facilitated workshops, brainstorming, questionnaires, prototypes, benchmarking. What the exam tests is narrower and harder: given a scenario, which one of these is right now, and which are merely reasonable.
Across the 100 questions in this bank that involve elicitation, one pattern dominates everything else. Brainstorming is the most frequently offered wrong answer in the whole category, appearing in 20 distractors against 4 keyed answers. It is worth understanding why, because the reason generalizes to the other techniques too.
Brainstorming produces options, and most exam scenarios are not short of options. They are short of a decision, or they already have the answer written down somewhere.
The clearest case: a project manager discovers a significant quality problem with a key supplier's deliverables, and the stem states that this supplier risk had been identified earlier in the project. One option is to call an urgent team meeting to brainstorm possible solutions. The keyed answer is to refer to the project's risk register for the predetermined mitigation actions. Because the risk was identified earlier, its response was already analysed and approved. Brainstorming, auditing every deliverable, or confronting the supplier all repeat analysis the team has already completed.
The same logic runs through a value engineering question. A construction project manager wants to improve the function-to-cost ratio, and one option is to have the team brainstorm functions to cut for cost savings. The keyed answer is to engage stakeholders to understand the critical functions first. Value engineering works on a ratio, so it needs both terms before it can improve either, and which functions matter is a question for the people who will use and operate the deliverable rather than for the delivery team.
Common trap: treating brainstorming as the neutral, collaborative first step in any ambiguous situation. In this bank it is the single most common wrong answer in the elicitation slice, and it is wrong for the same reason each time: it generates when the scenario needs deciding, checking, or asking someone specific. Before you pick it, look for a sentence in the stem saying the thinking has already been done.
Reach for a prototype when stakeholders describe the same feature differently, because that is the signal that words have already failed once.
One question puts exactly that on the page: while gathering requirements you find people picture the same feature very differently. The options include asking stakeholders to elaborate more clearly and booking a meeting for next week, parking the feature, and offering your own understanding for them to agree or disagree with. The keyed answer is to sketch a storyboard or prototype so stakeholders can see it, adjust it, and agree.
The explanation in the bank is the part worth carrying into the exam. Asking people to elaborate more clearly is the tempting answer that changes nothing, because it produces more words about the same unshared mental model. A storyboard or throwaway prototype replaces description with something everyone can look at, and the disagreement becomes visible and specific. Two people who both said "a summary screen" can now point at what they meant.
That is the general rule for prototyping on this exam. It is not a technique for gathering requirements from scratch. It is a technique for resolving requirements that have been gathered and turn out to mean different things to different people.
| The scenario says | Technique to pick | Why |
|---|---|---|
| People describe the same feature differently | Storyboard or prototype | Words have already failed once |
| The risk or response is already documented | None, use the register | The analysis is complete |
| You need reactions to a proposed offering | Focus group | Opinions from a selected group |
| You need cross-functional agreement | Facilitated workshop | Produces decisions, not opinions |
| A domain expert keeps clashing with the team | Bring them in early | Their knowledge can still change the design |
| The required functions are not agreed yet | Ask the stakeholders | You cannot improve a ratio without both terms |
Move them upstream, so their expertise lands where it can still change the design instead of arriving as criticism of something already built.
An observatory's telescope-time booking system has a user who knows the domain deeply, holds firm views about the technology, and routinely ends up in conflict with the team during demonstrations. The options include explaining that technical decisions belong to the team, making the user the technical architect, and continuing to show the product early so feedback arrives sooner. The keyed answer is to invite the user into the technical brainstorming sessions, where their expertise can shape the design early.
This is one of the four questions where brainstorming is keyed, and it is instructive that the reason has nothing to do with generating ideas. Showing the product early is what is already happening, and it is precisely where the conflict breaks out. Telling the user the decisions are not theirs escalates it, and handing them the architect's role displaces the team that has to build and support the thing. Bringing them in at the point where ideas are still being generated makes them heard and puts their knowledge where it can still matter.
So brainstorming is keyed here as a placement decision, not as an idea-generation technique. That is a useful reframe for the four keyed cases generally: when brainstorming wins, look for a reason connected to who is in the room rather than to how many ideas come out of it.
Patterns like this one are hard to spot from a technique list, and easy to spot after you have worked through a dozen scenarios where each wrong answer is explained rather than just marked wrong.
Why is brainstorming so often the wrong answer? Because it generates options, and most exam scenarios have already generated enough. Across this bank's elicitation questions brainstorming appears in 20 distractors against 4 keyed answers. When the analysis is done or a plan already exists, generating more ideas repeats work instead of acting.
When should I pick a prototype or storyboard? When stakeholders describe the same thing differently. Words have already failed at that point, so more discussion produces more words about the same unshared picture. A storyboard or throwaway prototype makes the disagreement visible and specific.
What is the difference between a focus group and a workshop? A focus group gathers reactions from a selected group of stakeholders or subject matter experts about a proposed offering. A facilitated workshop brings cross-functional participants together to reach agreement and define requirements, so it produces decisions rather than opinions.
If a risk was already identified, do I still elicit new options? No. The bank keys checking the risk register for the response that was already analysed and approved. One question offers brainstorming solutions to a supplier quality problem whose risk had been identified earlier, and that option is wrong because the work is already done.
PMP Practice's 2,141 questions are re-certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained, not just marked wrong, which is how a pattern like the brainstorming trap becomes obvious instead of anecdotal. Start the free 20-question sample — no card, no signup required to try it.
Why is brainstorming so often the wrong answer?
Because it generates options, and most exam scenarios have already generated enough. Across this bank's elicitation questions brainstorming appears in 20 distractors against 4 keyed answers. When the analysis is done or a plan already exists, generating more ideas repeats work instead of acting.
When should I pick a prototype or storyboard?
When stakeholders describe the same thing differently. Words have already failed at that point, so more discussion produces more words about the same unshared picture. A storyboard or throwaway prototype makes the disagreement visible and specific.
What is the difference between a focus group and a workshop?
A focus group gathers reactions from a selected group of stakeholders or subject matter experts about a proposed offering. A facilitated workshop brings cross-functional participants together to reach agreement and define requirements, so it produces decisions rather than opinions.
If a risk was already identified, do I still elicit new options?
No. The bank keys checking the risk register for the response that was already analysed and approved. One question offers brainstorming solutions to a supplier quality problem whose risk had been identified earlier, and that option is wrong because the work is already done.