Sometimes people are asking to be heard, not repaired
Someone says, “I had the worst day,” and before they finish you are already explaining what they should do tomorrow.
The advice may be sensible. It can still land badly if the person wanted understanding rather than a solution.
Listen for the need behind the words
Before responding, ask yourself: are they asking for advice, reassurance, a place to vent, or simply company?
You can even ask directly: “Do you want me to listen, or do you want help figuring out what to do?” That one question removes a lot of guesswork.
Validation is not the same as agreement
Saying “That sounds exhausting” does not mean you agree with every interpretation of the situation. It simply acknowledges that the person’s experience makes sense from where they are standing.
Validation can lower defensiveness because the person no longer has to spend the conversation proving that their feelings are legitimate.
Try reflections before solutions
Instead of immediately saying, “You should talk to your manager,” try: “It sounds like you felt ignored after you put so much work into it.”
If your understanding is wrong, they can correct you. If it is right, they often continue naturally and reveal what they actually need.
When advice is appropriate
Advice is useful when it is wanted, specific and realistic. Ask permission before switching modes: “I have an idea if you want to hear it.”
That keeps the other person in control and makes your advice easier to receive.
What to avoid
Do not compete with their story, immediately compare it with your own experience, minimise the problem or force positivity. “At least…” often closes a conversation faster than it helps.
You also do not have to solve everything. Sometimes being present is the useful action.
A simple listening sequence
Listen → reflect → validate → ask what they need → offer advice only if wanted.
Good listening is not passive. It is active attention without taking control of the conversation.
