Business foundations / 4 MIN READ

Separate a customer problem from the first solution you hear

Distinguish a requested feature from the underlying task, constraint, and uncertainty before deciding what to build.

A customer says, “I need a dashboard.” It is tempting to start drawing charts. But the request does not yet explain what the customer is trying to do, what is difficult about it, or whether a dashboard would fit their working conditions. Treat the proposed solution as a useful opening to a conversation, rather than the whole definition of the problem.

Keep four things separate

When recording a conversation, distinguish what the person asked for from what you know about the situation. A simple note can have four parts:

These categories prevent a neat request from becoming a premature specification. They also remind you that your interpretation may differ from the customer's own explanation.

Ask about an actual occurrence

Move from the general request to a specific example. You might ask, “When did you last need that?” or “Can you walk me through what happened?” Follow the sequence: what triggered the task, what information was available, what the person did next, and where the difficulty appeared.

A recent example will not establish how common a problem is across a market. It can, however, help you understand what this person means. Record gaps as gaps. If they cannot remember a detail, do not quietly replace it with an assumption that supports your preferred idea.

Consider an illustrative scenario

The following scenario is invented to show the distinction. A manager at a small repair business asks for a dashboard showing every open job. During the conversation, they describe a customer calling for an update. The latest job note was on a colleague's phone, and that colleague was unavailable.

The reported want is a dashboard. The task is answering a customer's status question. The described difficulty is access to the latest note when its author is absent. A possible constraint is that staff record updates while working away from a desk.

None of that proves a dashboard is wrong. It simply suggests that attractive charts might leave the central difficulty untouched if updates still do not reach a shared record.

Understand the existing workaround

Ask what happens now, including the parts that work well. In the example, staff might send messages, make calls, or leave handwritten notes. Each workaround may reveal requirements: speed, access, familiarity, privacy, or the ability to work without a reliable connection.

A workaround is not automatically evidence of willingness to buy a replacement. People sometimes tolerate an inconvenience because changing tools would create a larger one. Ask what makes the current approach worth keeping, as well as what makes it frustrating.

Write a problem statement with room for doubt

A useful draft describes a person, a task, a circumstance, and a difficulty without naming your preferred product. For the invented scenario: “When a customer requests an update, the manager sometimes cannot access the latest job note because it remains with an unavailable colleague.”

Words such as “sometimes” should reflect what was actually reported. Do not turn one example into “all repair businesses struggle with communication.” Keep the source of the statement in your private notes: who described it, when, and what remains unverified.

Compare options against the same task

Only then consider alternatives. A shared note, a clearer handoff, a short update routine, and a dashboard might address different parts of the situation. Compare them using relevant constraints rather than visual appeal alone.

Choose one uncertainty for the next conversation or small test. Perhaps the key question is whether staff can record a short update at the point of work. Use the question-to-opportunity worksheet to keep the observation, interpretation, and next check separate. The goal is not to reject customer suggestions. It is to understand them well enough to respond thoughtfully.