Customers say they want feature X, but is that the job or just a solution they've imagined?
The short answer
Almost always it's a solution they've imagined, and building it verbatim is how founders ship features nobody uses. The job hides one layer beneath the request: ask what they'd do if that feature existed, and what they're doing today without it. Your job is to trade their proposed solution for the underlying struggle it was meant to solve, then decide the real fix yourself.
Go deeper, your way
3 hand-picked resources, 3 link-checked. Pick how you want to dig in.
📖 Book
✓ Link checkedPaidBeginner
Why we picked it
The single best thing ever written on customer conversations. It teaches you to ask about the customer's life and past behaviour, not your idea, so you can't be lied to. If a founder reads one thing before talking to a single customer, it's this.
Why we picked it
The faster horse line gets quoted to justify ignoring customers entirely, and that reading is wrong. Vlaskovits, a customer development author, unpacks why a customer asking for a faster horse is still handing you the real job (get me there quicker), even though they named a solution they could imagine. It reframes a feature request as a signal about intent, which is exactly the muscle this question is about. Read it as a way to think, not a rule.
Why we picked it
When a customer hands you feature X, the Five Whys is the simplest technique for drilling from that request down to the real job underneath. This piece lays out the method in plain product terms, developed at Toyota and now a staple of product discovery, so you can run it on your next request in ten minutes. It is a concrete tool to pair with the mindset from the other two picks. Use it as a first pass, not a rigid procedure.
