“I already told them what to do.” That sentence often arrives with the assumption that the remaining problem is the other person’s character. They’re stubborn. They’re afraid of success. They don’t really want help.
Maybe. But before you settle on that explanation, inspect the advice. Was it requested? Did it address the real problem? Could the person carry it out with the resources they actually have? Did you account for the consequences they’d face and you wouldn’t?
A recommendation can be technically sound and practically unusable. Understanding that distinction can save a relationship, improve a consulting engagement, and spare you the frustration of repeating the same apparently obvious answer.
Imagine a solo consultant saying they need more clients. Someone advises them to post daily on social media. That might be useful if visibility is the bottleneck. It does very little if the consultant already receives inquiries but can’t explain the offer clearly or consistently deliver profitable work.
The visible complaint isn’t always the best diagnosis. “I’m overwhelmed” might mean too much work, unclear priorities, conflicting commitments, or a role that requires decisions the person isn’t authorized to make. Recommending better time management treats these as equivalent.
Ask for the sequence. What happens before the problem appears? What does the person do next? Where does it become costly? A concrete account often exposes a point of failure that a broad label hides.
Before proposing a solution, summarize what you think the problem is and ask whether you’ve understood it. “You have enough leads, but most are looking for a cheaper version of a service you no longer want to deliver.” That gives the person a chance to correct the map before you tell them which road to take.
“Just leave” is easy advice when you don’t have to replace the income. “Just hire someone” is easy when you aren’t funding the payroll. “Just confront them” is easy when you don’t depend on the relationship being discussed.
The word “just” deserves inspection. It often stands where the transition plan should be. A recommendation can describe a desirable destination while ignoring the route, the resources, and the hazards along the way.
In a hypothetical workplace example, an employee may agree that a recurring responsibility should belong elsewhere. They may also know that declining it abruptly would disrupt a customer commitment. The useful plan needs to cover the handoff. Repeating “set boundaries” doesn’t perform that work.
Ask what would make the recommendation difficult to carry out. Look for specific constraints: money, permissions, time, dependencies, contractual duties, or access to information. Some constraints can be changed. Others require a different plan. You won’t learn which by treating every objection as an excuse.
When you advise someone, you aren’t only transmitting information. You’re also proposing a role for yourself in their decision. A helpful suggestion can be heard as “I understand something you haven’t considered.” An unwanted lecture can be heard as “I don’t trust you to manage your own life.”
That doesn’t mean the interpretation is always fair. It means your intention isn’t the only information available. Timing, tone, history, and whether the person invited your input all affect the conversation you’re having.
Research by Gavan Fitzsimons and Donald Lehmann found that unsolicited recommendations contradicting consumers’ initial impressions could provoke reactance and contrary choices in their studies. The result doesn’t mean unsolicited advice always backfires. It does give us a reason to distinguish the content of advice from the conditions under which it is offered.
You can make those conditions clearer with a short question. “Would another perspective be useful?” isn’t a magic phrase. It is an opportunity for the person to choose the role they want you to play. Accept the answer, including when the answer is “not right now.”
Suppose a business owner resists narrowing their offer. You see unfocused positioning. They see long-standing clients who would be confused or disappointed. Their reluctance may include a commitment you should understand before trying to remove it.
Ask what they fear losing if they follow the recommendation. Income? Identity? A relationship? A sense of competence? The answer doesn’t automatically veto the change. It helps reveal what a workable transition must protect or honestly trade away.
For the hypothetical owner, a staged change might preserve current clients while clarifying the offer for new ones. The principle remains the same, but the implementation now respects the actual situation. Advice often becomes more acceptable after it becomes more complete.
There’s a close connection here with resistance to change. Before assigning a personality flaw, ask what the current arrangement makes possible. A bad arrangement can still be solving a problem that your proposal hasn’t addressed.
Some advice asks for a new identity when the person needs a manageable action. “Become more assertive” leaves them to invent the behavior, choose the moment, handle the reaction, and judge the result. That’s a lot of design work hidden inside two words.
A smaller recommendation might be: “Before accepting the next request, ask which existing priority should move.” The person can picture when to use it. They can also predict a possible response and prepare for it. The advice is easier to test because it is attached to a situation.
Smaller doesn’t have to mean trivial. It means the step is defined well enough to attempt and learn from. A consultant testing a new offer with three relevant buyers may gain more useful information than spending a month redesigning every public asset.
Ask the recipient to describe the first action in their own words. If they can’t, your explanation may still be too abstract. If they can but won’t, investigate the remaining concern. Don’t assume that understanding a plan creates an obligation to adopt it.
You gave the advice last week. They didn’t use it. You bring it up again, this time with more urgency. Soon the conversation is about whether they respect you enough to comply.
At that point, your concern may have become tangled with your need to be validated. The recommendation can still be good. Your stake in being obeyed can still make the interaction worse. Separate the two before continuing.
You can ask what happened without conducting a trial. “Did you decide against the idea, or did something get in the way?” Perhaps the person changed priorities. Perhaps the plan failed immediately. Perhaps they never agreed to it in the first place, and their polite response sounded more enthusiastic than it was.
If their behavior affects a shared commitment, address that commitment directly. A manager shouldn’t disguise a required performance standard as optional advice and then resent the employee for treating it as optional. Explain what is required, why it matters, and what discretion remains. Clarity about authority is fairer than a friendly tone wrapped around an unstated demand.
This possibility deserves its own space. We can become so interested in the psychology of resistance that we forget to inspect the recommendation. The person may be declining because they know something we don’t, or because our reasoning is weak.
Ask what evidence would make you withdraw the advice. If you can’t answer, you’ve made the recommendation difficult to evaluate. You should be able to distinguish between a sound idea poorly implemented, an unsuitable idea, and an idea that simply didn’t work under the circumstances.
Watch for advice built from your preferences rather than their objectives. You might love public speaking while they want a business that doesn’t require travel. You might value maximum growth while they value predictable family time. Your preferred life is an unreliable template for someone else’s decision.
A useful advisor can say, “Given that constraint, I wouldn’t recommend the original plan.” That sentence doesn’t undermine your value. It demonstrates that your judgment can respond to information. People have more reason to consider your next recommendation when you’ve shown a willingness to revise the last one.
Receiving advice requires judgment as well. You don’t have to accept every suggestion to prove you’re coachable. You do need a fair way to evaluate what you hear. Ask what problem the recommendation addresses, what assumptions it relies on, and what a small test would reveal. Rejecting an idea because the delivery irritated you can be as limiting as accepting it because the advisor impressed you.
If you decline, a clear explanation can improve the relationship. “I understand the suggestion, but I’m prioritizing predictable delivery this quarter” gives the advisor useful context. You aren’t asking permission to keep your own priorities. You’re making the decision legible so the next conversation can begin with better information.
Once you’ve clarified the objective and constraints, work on an option together. “What would a version of this look like that you could try without disrupting the existing commitments?” That question invites ownership and reveals feasibility at the same time.
Agree on what the experiment is supposed to teach. If the consultant tests a narrower offer, the result might be whether relevant buyers understand it and consider the problem worth solving. It doesn’t have to prove the entire business model in a week.
When the person mainly wants to be heard, practice listening without turning every conversation into advice. When they want help deciding, offer your reasoning and its limits. When you hold legitimate decision authority, be clear about the requirement rather than hoping your advice will be treated as an order.
The next time good advice seems to bounce off someone, get curious before getting louder. Inspect the problem, the transition cost, the relationship, and the size of the proposed step. Then inspect the advice itself. A recommendation becomes useful when it fits a real person making a real decision.