Turn a request into a written spec.
What it really is
On the surface, Gathering requirements can look like a single technique you either know or you don't. The real skill underneath is being able to sit with a customer, listen, and uncover what actually matters — and that's the part that actually transfers from one situation to the next. Here it shows up as a concrete, repeatable habit: turn a request into a written spec.
Why it matters
The highest-leverage information lives in the customer's head, and they rarely hand it over. A Delta earns it through trust and good questions.
What good looks like
- You ask open questions and actually listen to the answer.
- You dig past the first answer to the real problem.
- People feel understood, not sold to.
Where it overlaps
This is a cross-cutting skill: it also draws on Product Design. The points you earn here count toward Gathering requirements's global total and toward its primary capability, Customer Relationships.
Common trap
Pitching instead of listening, or asking leading questions that plant the answer.
How to practice
The rep: Turn a request into a written spec.
Do it on a real problem, not a hypothetical — under the kind of pressure where it's tempting to skip. Land it and you earn the Requirements Gatherer badge. Repeat it until it stops feeling like a technique and starts feeling like instinct.