Preview — full styling will appear after the next deploy completes.

bmad-method

Advanced Elicitation

Drawing out requirements stakeholders cannot articulate

Advanced Elicitation is the BMAD grooming pattern for stories where stakeholders know what outcome they want but cannot specify what to build. Socratic questioning, negative space probing, and example-driven techniques replace traditional requirements gathering.

flowchart TD
    VS([Vague Story<br>or Outcome Request]) --> SQ[Socratic Questioning<br>BA Persona]
    SQ --> Q1[What changes if<br>this works?]
    SQ --> Q2[What happens<br>when this breaks today?]
    SQ --> Q3[What have you<br>already tried?]
    Q1 --> NS[Negative Space Probing<br>what must never happen?]
    Q2 --> NS
    Q3 --> NS
    NS --> EX[Example-Driven Validation<br>walk through a real case]
    EX --> PR([Problem Statement<br>not feature list])
    PR --> PM_P[PM Persona writes stories<br>from problem statement]

Many stories fail not because they are technically ambiguous but because the stakeholder could not say what they actually needed. They described a solution rather than a problem, omitted constraints they assumed were obvious, or conflated several needs into one vague request. Advanced Elicitation is the structured approach to unpacking these stories before the PM persona writes a single line.

The primary technique is Socratic questioning: rather than asking "what do you want?" (which produces a solution description), you ask "what would you do differently if this worked?" and "what happens today when this breaks?" These questions surface the real constraint and the real success state. The BA persona runs the elicitation session and its goal is a problem statement, not a feature list.

Negative space probing identifies the things that are not obvious but should be: "What would make this solution worse than the current approach?" "What have you already tried that didn't work?" "What does this system never need to do?" Answers to negative-space questions often reveal the constraints that would have silently broken an implementation that looked correct on paper.