Where this was said
Why writing down every customer request can work against you
At 1:36 · chapter starts 0:40
Jason Fried opens with a confident defence of deliberate forgetting: the signal worth acting on is whatever keeps coming up repeatedly without being written down. The moment you put something on a list, you've manufactured an obligation — and product decisions made from obligations rather than genuine signal rarely lead anywhere good. He's careful to distinguish between productive listening and obsessive documentation: the former sharpens your instincts, the latter creates noise. His one carved-out exception is the 'Support Voice of the Customer' project [2] — Jason Fried "Support Voice of the Customer project: 37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually …" 02:25 , where particularly vivid customer language or unusual scenarios get captured — not for feature planning, but for vocabulary mining. He illustrates this with a charming anecdote: early Basecamp customers were organically calling their projects 'base camps,' an insight that eventually prompted 37signals to consider that naming convention in Basecamp 3. It's a story that shows what listening without writing down can still surface when you're paying real attention.
Hearing the same request repeatedly is your signal — not a written list. The moment you write something down, you create an obligation. Most individual feedback reflects one person's scenario, not the product's true direction.
37signals maintains a dedicated project called 'Support Voice of the Customer' to capture unusually insightful customer language and unique scenarios.
Early Basecamp customers organically called their projects 'base camps,' a usage insight that led 37signals to consider renaming projects accordingly in Basecamp 3.
