---
id: ins_pattern-of-pain-customer-research
operator: Hiten Shah
operator_role: Serial SaaS entrepreneur (FYI, KISSmetrics, Crazy Egg)
source_url: https://hitenism.com/
source_type: essay
source_title: "Hiten Shah — Pattern of Pain customer research methodology"
source_date: 2026-03-03
captured_date: 2026-05-02
domain: [product, pmm, research-discovery]
lifecycle: [voc-research, positioning]
maturity: applied
artifact_class: workflow
score: { originality: 4, specificity: 5, evidence: 4, transferability: 5, source: 3 }
tier: A
related: []
raw_ref: raw/expert-content/experts/hiten-shah.md
---

# Find the Pattern of Pain, and don't rush past it. Most teams fail by not digging deep enough.

## Claim
Product comes before Strategy; Strategy comes before Business Model. Companies routinely rush to monetization before proving the product is indispensable. The customer-research move that prevents this: surface the "Pattern of Pain", the recurring problem that emerges after enough qualitative interviews with a demographically similar cohort. Interview discipline: ask for stories not feedback, request opinions not help, hit 10-20% talk time, repeat back what you heard to trigger correction.

## Mechanism
The most common research mistake is not digging deep enough when a customer mentions a problem, moving to the next question instead of asking why. Shah's Draftsend failure: built a voice-to-document product without discovering that the real Pattern of Pain in documents was finding/organizing files, not presenting them. That failure produced FYI, which solved the actual most painful problem. Working-backwards adaptation: write the launch blog post and Product Hunt materials (including fake reviews) before any code, to force the team to articulate the customer's future reality.

## Conditions
Holds when:
- The team has access to enough demographically-similar customers for pattern detection.
- Interviewers can resist their own product enthusiasm and stay non-directive.

Fails when:
- The cohort is too small or too varied for pattern emergence (2-3 interviews are anecdote).
- Pre-PMF startups so early they don't yet know the right customer to interview.

## Evidence
> "Product comes before Strategy, and Strategy comes before Business Model."

> "The most common customer research mistake — not digging deep enough when a customer mentions a problem, rushing to the next question instead of asking why."

· Hiten Shah (synthesized from operator's published work)

## Signals
- Founder logs interview talk-time and aims for ≤20%.
- Roadmap velocity is stage-dependent: weekly pre-PMF, monthly post-traction, quarterly at scale.
- Pattern-of-Pain is named in the product brief, not implied.

## Counter-evidence
For products built on quantitative behavioral signal (PLG with millions of users), interview-based Pattern of Pain detection is slower than analyzing in-product data. Some founders argue that customer interviews systematically under-weight novel problems users can't yet articulate.

## Cross-references
- (none in current corpus)