a builder's codex
codex · operators · Shreyas Doshi · ins_doshi-truth-one-level-down

Three customer stories beat every strategic framework because the truth is always one level down

By Shreyas Doshi · Product advisor and writer · 2026-05-16 · essay · Get to the Core of the Thing

Tier A · TL;DR
Three customer stories beat every strategic framework because the truth is always one level down

Claim

Binary strategic debates feel rigorous but require no actual customer knowledge. Three specific customers with specific frustrations and one falsifiable differentiation bet replace any 2x2.

Mechanism

Framework debates stay abstract because they require no evidence. A team can argue "platform vs. point solution" indefinitely without naming a single real customer frustration. Anchoring the conversation to three concrete customer stories with named frustrations forces the evidence to exist before strategy begins. The one-paragraph brief that must follow makes abstraction structurally impossible.

Conditions

Holds when: teams default to frameworks before gathering specific customer evidence; consultants open engagements with canvases rather than customer interviews; strategy work debates abstractions without named customer stories.

Fails when: customer research is already done and the team has named frustrations with evidence; the debate is the evidence-gathering phase itself.

Evidence

Doshi's essay argues that most strategic work stays at the wrong altitude. The intake gate he proposes requires three things before any framework work begins: specific customer frustrations, a concrete differentiation bet, and real evidence.

"Do you actually know what your customers need, can you conceive real differentiation in the face of stiff competition, and can you build that?"

The compression:

"The truth is one level down. Always."

Signals

Counter-evidence

Frameworks have value once evidence exists. The claim is about sequence, not whether frameworks are useful. Teams with deep customer knowledge can use any framework productively.

Cross-references

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