“Can you add a bulk export?”
It is a reasonable request, clearly stated, and easy to put on a roadmap. A team that ships it will close the ticket and move on. A team that asks one more question may discover that the actual problem is that the monthly report takes three hours to assemble, and that the export button saves eleven minutes of it.
The request was not wrong. It was compressed.
Requests are solutions wearing a disguise
People do not experience their needs as abstract problems. They experience them as friction inside a workflow, and they propose the fix that seems most obvious from where they stand. By the time the request reaches a product team, it has already been translated into a solution.
That translation is useful. It tells you what someone believes would help, but it is not the same as the problem. Treating it as the problem is how teams end up with a long list of features that each address a fragment of the same underlying friction.
Five layers are usually worth unpacking:
The requested solution. What did they ask for, in their words?
The job. What were they trying to accomplish when the friction appeared?
The trigger. What happened immediately before they wanted this? Was it a monthly ritual, an exception, a handoff, a customer question?
The workaround. What do they do today instead? A spreadsheet, a copy-paste, a colleague, a delay. The workaround is often the most honest description of the problem.
The cost. What does the workaround cost them: time, errors, trust, money, risk? If the cost is small and infrequent, the solution may still be worth building, but it should be priced accordingly.
The workflow extends past your product
One of the most common framing errors is drawing the boundary of the problem at the edge of the product. A team sees the click, the form, the export. The user sees the report, the approval, the meeting where the number gets questioned.
When you map the full workflow, the intervention often moves. Sometimes the best answer is not a feature at all. It might be a default, a permission, a clearer error message, a change to the data model, documentation, a service, a partnership, or removing something that created the friction in the first place.
None of those are as satisfying to demo as a new button. All of them can be more effective.
The feature is the tip of the problem. Ship only the tip and the problem grows back.
Why teams default to features
Features are legible. They can be estimated, scheduled, shipped and counted. A change to a default is invisible in a release note. A conversation about incentives does not fit in a sprint.
There is also an ownership problem. A feature belongs to a team. A workflow that crosses three systems and two departments belongs to nobody, which makes it harder to fix and easier to ignore.
That is precisely why the product role matters. Someone has to be responsible for the whole problem, not just the part that fits inside the product boundary.
Saying no without dismissing
Unpacking a request is not the same as rejecting it. The goal is to honour the underlying need while being honest about the proposed solution.
A useful response has four parts:
- Restate the problem. “It sounds like the monthly report is the real friction, and the export is one way to make it faster.”
- Ask about today. “What do you do right now? How long does it take? What goes wrong?”
- Propose the smallest intervention. Sometimes it is the requested feature. Often it is a smaller change that addresses more of the workflow.
- Be explicit about what you are not doing. “We are not going to rebuild the reporting engine this quarter. Here is what we can do, and here is what would change our mind.”
That last part matters. Vague reassurance is worse than a clear no, because it leaves the person planning around a feature that may never arrive.
The test
Before committing to a feature, try to write the problem statement without naming the solution. If you cannot, you do not understand the problem yet. If you can, you have a much better chance of choosing the right intervention, and of noticing when the requested feature is only a small part of it.
The feature was never the problem. It was the shape the problem took when it reached you.