Notes ·
A Quiet Defence Of Slow Discovery
Engineering-led startups underrate slow discovery. Three reasons it pays off, and one reason it almost never gets prioritised.
Ji-Ho Kim · Product strategy / Discovery / Writing rituals
Slow discovery is unfashionable. The folk wisdom of the venture cycle prefers visible iteration: ship something, talk to a customer, ship again. Slow discovery is the discipline that asks an uncomfortable question first and listens to the answer for longer than feels comfortable.
Three reasons it pays off in pre-product-market-fit teams. It produces evidence that is harder to argue with internally because it is collected over weeks rather than days. It exposes false consensus among co-founders earlier than a fast iteration cycle would. And it shifts the team away from the trap of mistaking velocity for direction.
The reason slow discovery rarely gets prioritised is not philosophical, it is operational. Most early-stage teams do not have a writing ritual that can hold the artifacts a slow discovery cycle generates. Without that ritual, the slow part collapses into a folder of notes nobody reads. The Product Strategy program installs the ritual first; the discovery practice follows.