A customer asks for a dashboard, but the underlying problem may be that staff cannot find yesterday's unresolved requests. Building the requested screen without understanding the task can solve the visible suggestion while missing the costly problem.
For founders reviewing discovery, separate a feature request from evidence of demand. Both are useful, but they answer different questions.
What does a feature request establish?
It establishes that someone expressed a preference or proposed a solution in a particular context. It does not by itself establish frequent use, purchasing authority or willingness to change the current process.
Ask about the last time the relevant problem occurred, what the person did and what consequence followed. Preserve the original request while collecting the context needed to interpret it.
Build an evidence ladder for the request
Use a fictional office manager asking for an enquiry dashboard. The proposed worksheet keeps observations distinct from founder assumptions.
| Evidence level | Example question |
|---|---|
| Requested feature | What would the dashboard help you do? |
| Recent event | When did you last need that information? |
| Current workaround | How did you find it then? |
| Consequence | What happened because it was difficult? |
| Existing commitment | What time, money or process already addresses it? |
A person can describe a genuine problem without being the buyer. Record their role in using, approving and purchasing a solution separately.
Avoid turning interest into a sales conclusion
An enthusiastic answer to a hypothetical product description is not equivalent to an actual purchase or repeat usage. Keep the language in the findings proportional to what was observed.
For example, write that a respondent requested a way to review unresolved enquiries and described a spreadsheet workaround. Do not rewrite that as the market demanding an AI dashboard unless other evidence supports that broader claim.
The current-workaround guide provides a focused way to explore existing behaviour before choosing a solution.
Translate the request into a testable product decision
Choose the smallest experiment that can resolve the main uncertainty. A manual unresolved-request summary may test the value of the information before a complete dashboard is built.
My StackFlight case study describes a product for collecting and reviewing source responses. It does not claim that collecting feature suggestions automatically validates product-market fit.
Retain disconfirming evidence too. If respondents already solve the task cheaply or rarely need the information, that can support narrowing or rejecting the feature rather than treating every request as a development obligation.
Should we ignore feature requests?
No. Use them as a starting point for understanding the underlying task and context.
Does willingness to try prove willingness to pay?
No. Those are different commitments and should be reported separately.
What should we record first?
Keep the original request, recent example and current workaround in the product discovery brief.