Digging Beneath Feature Requests
Uncover the real motivation behind what customers say they want you to build
Digging Beneath Feature Requests is a technique for extracting genuine customer motivations from the surface-level solutions they suggest. When customers request specific features, they are doing your job for you and usually doing it poorly. They know what their problems are, but they do not know how to solve them. Your job is to understand the underlying motivation so you can design a better solution.
The technique involves asking 'why do you want that?' when a customer suggests a feature, and then continuing to dig until you reach the root motivation. A customer who requests a way to export data to a specific file format might actually need to share reports with a colleague who uses different software. The feature request is a proposed solution; the real need is seamless collaboration, which could be solved in many better ways.
This framework also applies to ideas that customers volunteer during good conversations. When a prospect gets excited and flips to your side of the table, they will start suggesting possibilities and features. Write these down but do not rush to implement them. Instead, dig into why they want each thing. The motivations and constraints behind feature requests are critical; the specific requested features are almost always wrong.
- Customers own the problem; you own the solution
- People know what their problems are but do not know how to solve those problems
- Feature requests are just the customer's proposed solution to an underlying need
- The motivations and constraints behind requests are critical; the specific features are not
- Startups are about focusing and executing on a single scalable idea, not jumping on every good suggestion
- Capture the feature requestWhen a customer suggests a feature or idea, write it down. This shows you are listening and respecting their input. Do not dismiss it outright, but do not commit to building it either.
- Ask why they want itDig into the motivation behind the request. Ask why they want that specific feature, what problem it would solve, and how they are currently dealing with the situation. The goal is to separate the symptom from the disease.
- Understand the constraintsExplore what prevents them from solving the problem themselves. What have they tried? What obstacles exist? Understanding constraints helps you design solutions that actually work within their real-world limitations.
- Synthesize the underlying needTranslate the feature request into a need statement that is independent of any specific solution. This gives you the freedom to design a better approach while still addressing what the customer actually cares about.
Finance professionals were spending hours daily emailing spreadsheets to each other and requesting better messaging tools. When asked why they bothered with all this emailing, they revealed the real motivation: ensuring everyone was working from the latest version of each spreadsheet. The requested solution was a messaging tool; the actual need was version control for shared documents.
Fitzpatrick observed that when founders started having good customer conversations, they would often over-correct by building exactly what customers requested, effectively creating products by committee. He recognized that customers are excellent at describing problems but poor at designing solutions, and developed this digging technique to bridge the gap between what customers say they want and what they actually need.