A small empty frame hanging from a hook in a wall panel, with a drill bit lying on the table below.

5of 7

Feature requests: uncover what customers need

A requested feature is one possible solution, not necessarily the problem itself. Understand the situation behind the request, identify the outcome customers need and test which approach fits.

Build & Validate
Customer discovery

By the EWOR Team2 min read

"We need an export button" sounds like a specification. It may actually point to a handover that the current workflow makes difficult. Building the button immediately risks solving the wrong problem, while dismissing the request could mean missing valuable insight into the customer's constraints.

Start by understanding the outcome behind the request. You are investigating one customer's situation, not yet synthesising the entire research programme into a problem statement.

Go back to the last time they needed it

Ask when the customer last needed the feature. What were they trying to complete? What happened immediately before and afterwards? Who depended on the result? How did they manage without it?

In a hypothetical example, a manager requests a spreadsheet export because an external accountant needs approved figures each month. The manager currently re-enters those figures manually. The underlying goal may be to hand over accurate, approved information without duplicating work, rather than simply to have another download option.

That interpretation is still provisional. The accountant may require a specific file format, making the export a genuine requirement rather than a casual preference.

Separate outcome, mechanism and constraint

Write three short notes. The outcome describes what the customer is trying to accomplish. The mechanism captures the solution they requested. The constraints identify conditions any acceptable solution must meet, such as compatibility, approval requirements or limited connectivity.

Include enough context to make the need useful. "Be more productive" is too broad. "Transfer approved monthly figures without re-entering them" describes a specific outcome while leaving room for different solutions.

Include emotional or social outcomes when the customer expresses them, such as confidence that a handover is complete. Do not infer an unstated motivation and present it as established fact.

Check your interpretation with the customer

Reflect the goal back in plain language and ask what you have missed. Then compare your interpretation with another specific occasion or an authorised demonstration of the current workaround. Agreement with your summary is useful, but check it against another example before assuming it explains every case.

Look for differences between people making seemingly identical requests. One may need an export for an audit, another for analysis and another to leave the system. The same feature request can conceal very different needs.

Compare solutions without dismissing the request

Use the clarified goal and constraints to compare possible approaches. The requested feature may still be the best solution. Understanding the underlying need is not a reason to dismiss what customers ask for.

Before promising a feature, identify the smallest investigation that can distinguish between the options. What evidence would show that each approach achieves the goal under the customer's actual conditions? The requested feature may prove best, but it should not win simply because it was mentioned first.

No comments yet.

Be the first to comment on this signal.

Get the next signal before everyone else.

Frameworks and contrarian theses for outlier founders, straight to your inbox. No fluff, no recycled advice, weekly.

The EWOR Signals newsletter

Continue learning

Related modules