Module 1: The Problem — Why Smart People Still Miss the Middle
The Failure Pattern
Requirements gathering is usually taught as a single, undifferentiated skill: ask good questions, listen carefully, document what you hear. That framing is incomplete. It treats “gathering information” as one activity, when in practice every piece of client information exists at a specific level of abstraction — and the skill that actually determines whether requirements are usable is the ability to identify which level you’re operating at, moment to moment, in real time. Most practitioners have never been taught that these levels exist. As a result, they default to failure patterns covered in full in Module 4: chasing detail too early, capturing narrative without ever translating it, or over-correcting into forced confirmations. Both of the first two patterns are notable for the same reason: each one is indistinguishable from competence while it’s happening. Spelunking presents as thoroughness. Blindness presents as attentive listening. Neither triggers the self-correction signal you’d expect from an obvious mistake, because in the moment, nothing feels wrong. The defect is only observable downstream — in scope gaps, in rework, in a statement of work that is precise about the wrong things and vague about the right ones.
Where the Cost Actually Lands
The failure is rarely visible in the discovery call itself. It surfaces three steps removed from the original conversation:
- In scoping, when no one can produce the sentence that defines what was actually being asked for
- In the SOW, where specificity and vagueness are distributed at random rather than by design
- In UAT, when a requirement the client considered obvious was never captured because it was never translated out of process narrative
- In the client relationship, where the practitioner is perceived as having listened well and still delivered the wrong scope — the more damaging failure, because it’s harder to diagnose and repair
Illustrative Case
A client states that billing errors are costing them renewals, that leads aren’t qualified. A practitioner without altitude awareness has two default responses: pursue proration logic and invoice cycles immediately (spelunking), or record the statement as a pain point and move on (blindness). Neither response produces the sentence a scoping team actually needs: a specific statement of what the billing system must be able to do. That sentence doesn’t emerge from listening harder. It emerges from knowing that a gap exists between “pain point” and “buildable requirement,” and deliberately working to close it.
The Underlying Claim
This is not a matter of raw talent. It is the presence or absence of a specific, learnable capability: an active, running check of what level of abstraction the current statement occupies, and whose statement it is, paired with a deliberate practice of moving information between levels rather than staying wherever the client happens to leave it.