REWORK

Snapshot · REWORK

Don't write it down

Explore episode Jul 15, 2026

Where this was said

Why writing down every customer request can work against you

At 2:48 · 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, 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.

Business
Don't Institutionalize Customer Feedback

Don't write it down · Jul 15, 2026 Business

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.

Similar snapshots