Generic questions yield generic lies. When you ask a target customer, "How do you usually handle your business taxes?", they describe an idealized version of their workflow. They tell you about their digital filing cabinets, their meticulous weekly bookkeeping, and their tidy receipts.
However, if you ask, "Walk me through what happened when you submitted your quarterly taxes last month," the story changes. They reveal that they panicked at 11:30 PM on deadline night, sorted through crumpled receipts in a shoebox, and paid a late filing penalty. Specifics reveal ground truth; generalizations hide incompetence and operational reality.
The Three Anchors of Hard Behavioral Evidence
Reliable discovery data requires three foundational anchors:
- Chronological Anchor: A specific date, week, or cycle (e.g., "Last Thursday during the product release").
- Financial Anchor: Actual currency, subscriptions, or staff salaries committed to addressing the obstacle.
- Artifact Anchor: Concrete physical or digital tools employed (e.g., a specific Excel template, a Zapier webhook, or a whiteboard).
✘ The Generic Opinion Question
Prompt: "Do you find project management tools confusing to navigate?"
Customer: "Yeah, most tools out there are really cluttered and could be streamlined."
✔ The Event-Driven Specific Prompt
Prompt: "What tool did you open first to plan your sprint this morning, and what was the hardest part of that session?"
Customer: "We use Jira, but it took me 45 minutes to assign story points because our custom fields broke."
Dissecting Past Incidents: The Reverse Timeline Technique
To drill down to the ground truth of customer behavior, guide the subject backwards through their recent workflow experience:
- Identify the Endpoint: What was the ultimate outcome? (e.g., "We missed our client deadline by 48 hours.")
- Trace the Immediate Antecedent: What directly triggered that failure? (e.g., "The legal team had not reviewed the master services agreement.")
- Examine Prior Remediation Efforts: Did they look for software or consultants? (e.g., "We looked at contract management tools but abandoned them because onboarding required enterprise setup fees.")
General Opinions vs. Concrete Inquiries
| Abstract Question (Avoid) | Concrete Equivalent (Use) | Insight Produced |
|---|---|---|
| "How much would you pay for automated backups?" | "What did you pay your managed IT vendor during the last server crash?" | Verified price tolerance based on real spending history |
| "Do you prefer mobile or desktop dashboards?" | "Where were you physically located when you last checked that status?" | Authentic user context without subjective design opinions |
| "Is team communication a major bottleneck?" | "How many messages did you have to review to resolve yesterday's issue?" | Quantifiable volume of operational friction |
Pros and Cons of Rigid Incident Anchoring
Pros: Removes vanity responses; uncovers actual operational workarounds; equips your engineering team with concrete customer use cases rather than vague user personas.
Cons: Requires more patience during interviews; interviewees may need a moment to recall specific dates; you conduct fewer, more detailed interviews instead of high-level surveys.
Stop asking people what they think, feel, or anticipate. Drill into what they recently experienced, what they attempted, and what they paid. Concrete past specifics are the only reliable roadmap to a commercially viable business.