a builder's codex
codex · operators · Hiten Shah · ins_pattern-of-pain-customer-research

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

By Hiten Shah · Serial SaaS entrepreneur (FYI, KISSmetrics, Crazy Egg) · 2026-03-03 · essay · Hiten Shah — Pattern of Pain customer research methodology

Tier A · TL;DR
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:

Fails when:

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

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

Open the interactive view → View original source → Markdown source →