Respect the request; investigate the reason
“We need Shopify,” “We need an app,” and “We need a new website” are solution statements. They may be correct, but they should be treated as hypotheses until the underlying need is understood.
| Question | Practical answer |
|---|---|
| Request | “Fix our checkout.” |
| Investigation | Where does checkout fail? Who is affected? How often? |
| Underlying problem | Critical conversion and operational issues in the existing setup. |
| Decision | Fix locally or move toward a more scalable platform? |
How to disagree professionally
Do not say “your idea is wrong.” Say “I see why this would solve the immediate problem. I also want to show you what happens if we look at the next 12–24 months.” That turns disagreement into a decision conversation.
Challenge the solution without challenging the client
The safest way to question a request is to be curious about the reason behind it. “What makes you think this will solve the problem?” is less confrontational than “That is the wrong solution.”
Keep three statements separate
Request: add a popup.
Problem: returning visitors are not seeing relevant offers and repeat purchase behavior is low.
Outcome: improve relevant repeat-purchase engagement without increasing support or page friction.
Once the layers are separated, a popup can still be the final answer. The point is that it should win because it fits the problem and constraints, not because it was the first idea in the conversation.
Take three common client requests—“new dashboard,” “redesign the homepage,” “add an app”—and write the problem and outcome that could sit behind each request.