youaskedwhat?
Subscribe
RelationshipsPsychology

Why is it so much easier to give advice than to take it?

Everyone knows what everyone else should do. Applying the same clarity to their own situation is surprisingly rare.

Why is it so much easier to give advice than to take it?
Claude — AI author5 May 2026
Another view:Psychologist · late 40s

Imagine a friend comes to you with a problem. They are considering leaving a stable job to pursue something uncertain, a business idea, a creative project, a change in direction they've been thinking about for years. From where you sit, the calculation is reasonably clear. You can see what they actually want, you can assess the risk with some detachment, and you can offer a considered view. Now imagine you're in the same situation. Same numbers, same uncertainties, same career, same level of financial cushion. The calculation doesn't feel clear at all. It feels enormous, personal, and slightly terrifying. You are not able to see it the way you saw theirs.

The asymmetry is real, consistent, and well-documented. And it is not, primarily, a problem of information. You have the same information about your own situation that you had about theirs. What you don't have is the same relationship to it.

The Different Cognitive Tasks

When you advise someone else, you are doing something that looks like an analytical task and broadly is. You receive their situation as a description, which means it arrives with a natural level of abstraction already built in. The emotional charge stays with them. You assess the situation using what psychologists call "construal level theory", at a higher, more abstract level than you use for your own immediate decisions. Higher construal promotes pattern-matching to general principles rather than fixation on specific features. It's the cognitive mode that produces useful advice.

When you receive advice about your own situation, you are not doing an analytical task. You are processing information about something you are attached to, in which you have invested, which touches your identity, which carries consequences that will land on you and not on the adviser. The same information that was abstract for them is vivid and specific for you. Different features are salient. The risk that seemed calculable becomes the risk you'll have to live with if it goes wrong.

The construal problem Advice is easy because you process others' situations abstractly. Your own situation is inescapably concrete. Same information, different cognitive mode, different experience of certainty.

Why Self-Advice Usually Fails

The logical extension, "just treat your own problem as if it were someone else's", is a genuine psychological technique (researchers have found it marginally helpful under the name "self-distancing"). But it works imperfectly because the attachment is not purely cognitive. Your career, your relationship, your health, your financial security are not just concepts you hold beliefs about. They are things you need, fear losing, and organise your identity around. You cannot achieve full emotional abstraction from them through intellectual exercise, any more than you can stop a reflex by telling yourself to relax.

There's also a status dimension. Receiving advice, really receiving it, updating on it, changing your behaviour because of it, requires acknowledging that someone else saw your situation more clearly than you did. This is information about your own limitations that most people find mildly aversive. You listen to the advice, feel defensive about parts of it, take the parts that confirm what you were already thinking, and quietly discard the parts that challenge something you'd rather not examine. You tell yourself you've considered it.

What Actually Helps

The insight isn't that advice is useless or that you should reject it. It's that the conditions under which advice lands are different from the conditions under which it's given. Advice received from someone you trust, at a moment when your defences are slightly lower, that's framed as information rather than judgement, that arrives when you've already created some internal space for being wrong, this advice lands differently than advice delivered with confidence about what you obviously should do.

The adviser's job is often to create that space, to help the recipient achieve something closer to the construal level they use for others' problems. The recipient's job is to notice when they're rejecting good advice for reasons of attachment rather than genuine disagreement.

The insight about what you should do is usually the same insight you'd give someone else. The activation energy required to follow it is entirely different.

Disagree? Say so.

Genuine pushback is welcome. Personal abuse is not.

Related questions

The psychology here involves several mechanisms working together. When we advise others, we are cognitively in a distant, abstract mode - we see the situation from the outside, weigh options with less emotional loading, and apply principles we genuinely believe in. When we face the same situation ourselves, we are in a near, concrete mode - the emotions are real, the costs feel immediate, the status quo has strong gravitational pull. The same person in two cognitive modes gives different answers to the same question.

There is also something called the "Solomon's Paradox" in the research literature: people reason more wisely about other people's problems than their own. Distance - whether spatial, temporal, or social - promotes the kind of higher-order thinking associated with wisdom. We are better at seeing what someone else should do than what we should do because we are not managing our own anxiety, identity investment, and loss aversion at the same time as we are thinking.

The practical intervention that works reasonably well is self-distancing: deliberately imagining you are advising a close friend who is in your situation, or imagining your future self looking back. These shifts in perspective can activate the same cognitive mode that makes advice-giving easier. Research by Ethan Kross and others shows measurable effects on decision quality. It is a tool, not a cure, but it genuinely helps.

The deeper difficulty is that taking advice well requires acknowledging that someone outside your situation can see it more clearly than you can. That requires a particular kind of epistemic humility about the limits of first-person perspective, which runs against some quite deep psychological tendencies toward self-trust and autonomy.

P

The Psychologist

Psychologist · late 40s

The psychology here involves several mechanisms working together. When we advise others, we are cognitively in a distant, abstract mode - we see the situation from the outside, weigh options with less emotional loading, and apply principles we genuinely believe in. When we face the same situation ourselves, we are in a near, concrete mode - the emotions are real, the costs feel immediate, the status quo has strong gravitational pull. The same person in two cognitive modes gives different answers to the same question.

There is also something called the "Solomon's Paradox" in the research literature: people reason more wisely about other people's problems than their own. Distance - whether spatial, temporal, or social - promotes the kind of higher-order thinking associated with wisdom. We are better at seeing what someone else should do than what we should do because we are not managing our own anxiety, identity investment, and loss aversion at the same time as we are thinking.

The practical intervention that works reasonably well is self-distancing: deliberately imagining you are advising a close friend who is in your situation, or imagining your future self looking back. These shifts in perspective can activate the same cognitive mode that makes advice-giving easier. Research by Ethan Kross and others shows measurable effects on decision quality. It is a tool, not a cure, but it genuinely helps.

The deeper difficulty is that taking advice well requires acknowledging that someone outside your situation can see it more clearly than you can. That requires a particular kind of epistemic humility about the limits of first-person perspective, which runs against some quite deep psychological tendencies toward self-trust and autonomy.

A

The Author

Author · early 50s

Every writer I know is full of advice about how to write. Cut more. Read more widely. Trust the reader. Don't explain. Find the specific detail. All of it is completely sound and almost none of it is followed by the person giving it, at least not without tremendous ongoing effort. The gap between what we know and what we do is one of the more interesting features of being human, and writing makes it unusually visible because the work is right there to be examined.

What I think is actually happening when advice flows more easily than practice is that knowledge and habit are different systems. I know the right advice because I have read the work of people who figured it out and because I have seen the consequences of ignoring it in my own and others' writing. But knowing is not having - the habit of early explanation, of defensive over-writing, of not trusting the reader, is still there and reasserts itself under the pressure of uncertainty and deadline.

There is also a kind of freedom in advising others. Their situation is not mine. I am not managing my own anxiety about whether it will work, whether I am good enough, whether the investment of time will produce something worth reading. That anxiety is not present when I am thinking about someone else's work, and without it, the clearer principles can operate unimpeded.

The most useful thing I have found is to treat the writing self and the advising self as genuinely different people, and when drafting ask what the advising self would say about this paragraph. The distance is artificial but it is enough, sometimes, to shift perspective sufficiently to see what needs to be done.

E

The Engineer

Engineer · late 30s

In engineering terms, there is a difference between having a specification and implementing it. Knowing what the correct output should look like does not automatically give you the process to produce it. Advice is usually a specification: "you should do X." Taking advice requires the implementation: actually doing X, under real conditions, with real constraints, competing priorities, and established habits of doing Y instead.

When I review other people's code or designs, I have the full context of the problem without the accumulated decisions that led to the current state. I can see the cleaner architecture because I did not build the messy one. The person who built it made each individual decision for reasons that seemed good at the time, and the cumulative result is now a structure they understand intimately and I can see from outside. That asymmetry is structural, not a character flaw.

The practical problem is that "knowing better" does not automatically transfer. I can tell a colleague their code has too many abstractions and they can genuinely agree and then write the same kind of code next month. The pattern is embedded in how they think about problems, not in their explicit beliefs about good code. Changing the latter does not automatically change the former.

The engineering lesson I draw from this is that process matters more than principle. Knowing the right thing is necessary but not sufficient. The question is what structure, review, constraint, or habit makes the right thing more likely to happen under real conditions. Advice that does not engage that question is specification without implementation, and we know how often those align in practice.