Describe the difficulty, not the feature
A useful problem statement explains a customer’s situation without prescribing the solution. “We need a mobile app” is a proposal. “Field workers cannot check job changes while away from their desks” describes a difficulty that could have several solutions.
Make the context concrete
Identify the user, the task they are trying to complete and the conditions that make it hard. Avoid broad claims such as “users want convenience”. Ask what inconvenience means in practice and how you know it exists.
Connect the problem to consequences
Explain the effect on the customer and the business. Delayed job updates might lead to wasted journeys, missed appointments or repeated calls. Treat these as hypotheses until interviews or operational evidence support them.
Check whether it helps you choose
A good statement helps a team evaluate options. Compare a notification, a mobile view and a scheduling change against the same problem. If every idea seems equally relevant, narrow the statement or gather more evidence.
Define who needs help, what gets in their way and why solving it matters.
