User Needs vs Feature Requests
Treat the requested feature as evidence about a larger job. · Product Judgment · Lesson 03 · 3 min
User Needs vs Feature Requests · 3 min
Situation
“Can you add CSV export?”
A customer asks to export every order. It sounds straightforward, but the request could hide reconciliation, reporting, migration, a backup requirement, or a missing integration.
Each purpose implies different data, frequency, permissions, and reliability requirements. An Export button alone does not tell you which outcome to support.
Investigate
Ask what happens after the click.
“Walk me through the last time you needed the file. What did you do with it next?” is more useful than “Would filters help?”
Watch the destination spreadsheet. If the customer repeatedly deletes columns and copies one total into accounting software, the real friction may be reconciling payouts rather than accessing raw data.
Mental model
A request contains a proposed mechanism.
Separate the desired progress, the current workaround, and the customer's suggested implementation.
The suggestion is valuable because users understand their own constraints. Still, they may not know the product's other possibilities. Respect their knowledge without outsourcing solution design to whoever asks most forcefully.
Compare
Export, report, or integration?
A monthly accountant may be well served by a stable CSV with clear column meanings. A warehouse needing updates every minute may need an integration. A manager checking one total may need a simple report.
Do not build all three to avoid choosing. Find the highest-value repeated need and the least costly way to serve it reliably.
Decision
Offer a testable response.
“We think your main difficulty is matching orders to payouts. We can test a reconciliation export with order IDs and payout IDs before designing a general report builder.”
Specify freshness, permission scope, and expected volume. Test the exported file in the actual destination workflow, not just whether the download works.
Remember this
Follow the requested feature into the user's work.
The work before and after a feature often reveals the requirement that matters most. A good response can differ from the requested implementation while satisfying the underlying need.