Ask the client to describe a recent occurrence of the problem, who was affected and what happened next. Explore the current workaround and the consequences they want to change. Keep proposed services provisional until you can connect them with evidence, constraints and a decision the client actually needs to make.
Ask for an incident rather than an adjective
Words such as confusing, slow and ineffective can refer to very different experiences. Ask for the most recent occasion when the difficulty occurred. Invite the client to describe the task, the starting point, the obstacle and what the person did next. A sequence of observable actions gives you something to investigate. Do not require them to identify the underlying cause before you have explored the situation.
Use neutral follow-up questions. What information was available at that moment? Who could make the decision? Where did the work stop? Avoid suggesting that your preferred service would obviously have prevented the problem. If the client cannot recall an incident, mark the description as a concern to explore. An uncertain concern can still matter, but it should not be rewritten as an established recurring failure.
Understand the workaround and the stakes
Current workarounds reveal both the cost of the difficulty and knowledge that a new service must preserve. People may rely on a spreadsheet, a colleague or a weekly meeting for good reasons. Ask what works about that arrangement before listing its weaknesses. Distinguish inconvenience from a consequence that makes change worthwhile, such as duplicated checking or a task that cannot proceed without specialist assistance.
Explore frequency and severity separately. A rare interruption may be serious; a frequent annoyance may be tolerable. Ask how any estimates were obtained and use ranges when records are incomplete. Do not multiply an informal time guess into a confident annual financial loss. The immediate output is an account of the problem and its significance, with the strength of the evidence clear.
Test whether your service addresses the problem
Only after understanding the incident should you map possible responses. A revised guide might help a missing instruction, while a permission bottleneck may require an operational decision. Explain which part you could investigate or change and which part belongs to the client or another specialist. This makes a recommendation useful even when the appropriate next step falls outside your usual offer.
Reflect the problem back in the client’s terms and ask for correction. A good summary names the affected task, the reported obstacle and the desired change without committing to a solution. Agree what evidence would strengthen or challenge that account. If a paid discovery activity is appropriate, define its purpose and output separately from the implementation service so the client can evaluate that decision fairly.
Keep a compact incident note with four entries: the attempted task, the point of difficulty, the workaround and the consequence reported. Read it aloud before discussing services. If the client changes any entry, preserve the correction in your working summary. This small artifact gives later recommendations an explicit basis and makes disagreement easier to resolve than a vague statement that the experience needs improvement.
Fictional example: a request for a new presentation
A fictional independent designer is asked to rebuild a sales presentation because it is “not working.” Rather than opening with visual options, she asks about the most recent use. The client explains that a prospective partner repeatedly asked which team would provide ongoing support. The slide deck had been shown, but nobody in the meeting could confirm the support arrangement.
The designer records a reported information gap and an unresolved ownership decision. She can clarify how the confirmed arrangement appears in the presentation, but cannot determine the commercial responsibility. Her proposed next step is a short content inventory after the client names the support owner. The revised brief separates that dependency from any design work. This fictional example demonstrates a scoping decision, not evidence that a new deck won business or improved conversion.
A checklist for your next step
- Request a recent incident.
- Describe the current workaround.
- Separate frequency from severity.
- Identify what your service can change.
- Confirm the problem summary.
Common questions
What if the client already wants a specific service?
Respect the request and ask which problem that service is intended to solve. The answer helps define scope without dismissing their experience.
Must I conduct extensive research before responding?
No. A short initial conversation can establish whether further investigation is needed. Keep conclusions proportionate to the evidence available.
Further reading
These primary resources provide related background. They do not validate the illustrative example or endorse AliveProfile.
AI-assisted drafting and automated technical checks. Examples are illustrative; no independent expert review or real-world outcome validation is claimed. Read our editorial policy.