Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Marriage has taught me to go even further than that. I now ask "are you telling me to get it off your chest, or you want help solving it?". If the former, I don't offer any solutions whatsoever, in any kind of format.


Thank you for bringing this up. This was a life lesson that unfortunately had to be spelled out for me in a very embarrassing way.

My ultimate takeaway is to now default to listening without advice. The result are on average better as people who want to vent are more put-off by advice givers than advice seeks who receive a good listener. It's also made me quite a bit more appreciative of times when I need to vent and someone is there to simply listen.


What do you do though? Just stand there quietly nodding? When I try to do this I end up basically saying "that sucks", "hmm hmm", "yeah", etc which is very frustrating to me as I'd hate someone doing that to me. Or worse, sometimes I get the feeling that those "that need a listener" actually want mindless agreement with whatever the situation was or I feel like I'll be reinforcing insecurities.

Let's say someone is telling you they are fearful for their job, they think they will get fired soon, even though they have nothing specific to point to. As a listener, are you agreeing with this or are you neutral nodding your head? Because my default would be to reply that they should do the best they can and if it comes to that they will surely find better pastures, but then I'm giving advice already.

I hear this advice but I have little clue how to put it into practice, moreover because of what I mentioned above, if I'm telling someone something, I definitely want them to think about it and try and help me with advice, otherwise I feel like they don't even care and would not share again with the same person.


There’s a big difference between agreeing with someone, and acknowledging their emotional state.

In these situations people just want to hear you acknowledge that you understand they are in pain, no necessary agree with their cause of action.

If you’re not sure what to ask, then your best course of action is to enquire about why they think they feel a certain way. Why does they job makes them stressful, why does talking with a certain person make them anxious. You’re not rendering judgement on their emotions or feels, you simply acknowledge they are what they are, and that’s normal.

For some specifics the following might be useful:

“Why do you think X makes you anxious”

Once they answer

“Yes, I understand now why that might make you anxious”

Or

“It’s perfectly normal to feel anxious”

If there behaviour is causing issues:

“It’s perfectly normal to feel anxious, that’s ok, but the way you’re dealing with it is causing issues for X. Perhaps we can find a better way for you to cope?”

For more, it’s worth looking at Mental Health First Aid. It can provide a number of very practical tips of dealing with someone in crisis, which are also excellent for helping those that just need to vent to someone.


> There’s a big difference between agreeing with someone, and acknowledging their emotional state.

This has been a key takeaway for me too, also in the context of intimate partner communication.

However, I would say that there can for sure be pitfalls with it— it's easy to believe that you are communicating only acknowledgment of emotional state, but have the listener receive it as signing on to their interpretation of the facts, the overall premise, their assessment of the other players' actions and motivations in the story, and so on.

This can lead to major misunderstandings down the road, when the person presents concrete actions that they are expecting will be taken. They may not be anticipating any pushback on this because previous validation-of-emotional-state conversations led them to believe you were both on the same page, when in fact you have significant concerns (whether it was that they misjudged the situation, escalated it unnecessarily, viewed someone else's actions unfairly, failed to accept a compromise or take possible corrective actions, whatever it is).

At that point, it's probably the type of conflict best taken to a professional to sort out, but I think of these situations when I see relationship coaches on TikTok talking up this kind of emotional validation as being a silver bullet for resolving all conflicts and achieving lasting harmony.


I can really empathize with this struggle.

>As a listener, are you agreeing with this or are you neutral nodding your head?

The "trick" I do is to try to set aside whatever train of thoughts I might have had before the person spoke to me, and try to imagine that the thing they talk about is happening to me. And then, voice my reaction to that. So if someone told me that "I'm fearful for my job. I think I might be fired soon", the first that comes to mind is "Oh my god, that's horrible! Why do you think that happens? Have they hinted about this before?"

Now, this maybe works a handful of times in the conversation. A second thing that you can do is trying to imagine the relations of the thing that just got told to you. By relations, I mean relating to anything, how it connects to anything: the speaker's environment, life circumstances, your shared universe, anything. Continuing the example above: "The timing is such a shame, given what's going on in your life, I would have liked it that at least the job is stable".

Third thing, you could discuss the persons possible actions and reactions to the event, and how others in their life have, or will have taken it. Continuing: "Do you have anything else lined up, just in case?" "Could your side gig support you until you find another job?" "How did your spouse take the news?"

And the fourth thing, it's always worth thinking about WHY the other person told you the thing they did. What are you to this other person? A friend? Colleague? Are you their superior? Spouse? Do you relate, in a way, to the thing that they told you? Are you maybe a recruiter, and that's why they tell you that they are fearful for their job? The answers to these questions can bring you closer to your natural response to the situation.


At least personal type conversations, “that sucks” is very very often exactly the right thing to say. Even in work situations it can be a reasonable first response, at least with people not too much further up the org chart than you: “The load balancer latencies have just spiked” “That sucks”. (I’d suggest against using it if CTO comes in yelling about the entire network being cryptolockered though. Unless it’s “That sucks, but I told you so. I quit.”)


You could try to associate this with the rubber duck trick where you just tell your problem to anyone, just to articulate the problem may very well solve it. You don't need input.

In my experience this is also a women-men difference in brain wiring. Men often looks for help when he fails to solve a problem, women always looking for emotional support before solving a problem.

If you give a solution for someone looking for an emotional support or vica-versa you've expreienced one of the main source of frustration in relationships :)


Also a lot of emotional problems don’t need to be solved, you just need to process the feelings and move forward.


There's a term that's useful here: active listening. If they are fearful for their job, express concern and ask them to tell the story:

"Oh no, that's terrible! Why are you fearful, are you all right?"

and you remain active by asking follow-up questions. For example to plug gaps in the story:

"Wow! Did your manager say that to your face? Or was it hearsay through that one co-worker?"

and so on. Expressing emotions is also perfectly fine:

"I feel bad. Wish I could do something for you."

I'd only interject long enough to get them talking again. If they need your help they'll have asked it by now :)


There’s a fantastic book and tv series by a research psychologist Brene Brown where she talks a lot about how to be on the listening end of these kinds of conversations. Often in these situations the other party just wants to have their emotions validated by someone they trust. Just being there to acknowledge their feelings and see their pain is enough (and trying to do more can sometimes make things worse). I highly recommend checking Brown out, she is quite incredible.


I agree and would like to emphasize the word "validation".

It is less about "solving a problem" and more about "figuring out how to feel about the problem".

Validation can help reduce emotional turmoil, distill it into a calmer set of feelings.

The feelings may still be strong. The situation may still suck.

But at least you can be sure of how much it sucks - because someone else you respect, see's it as valid too.


> When I try to do this I end up basically saying "that sucks", "hmm hmm", "yeah", etc which is very frustrating to me as I'd hate someone doing that to me.

Something my sister does, which I hate, is follow up "hello" with a falling-pitch "how are you". This really bothers me every time she does it to me, which is pretty often.

But I have a lot of problems responding to (strangers) asking me how I am, and I've tried her approach of mostly ignoring the question and reflecting back a falling-pitch "how are you", and it seems to work very well. No one ever complains that I ignored their question, and the focus goes back on them, where I want it, instead of me.

If I were to judge this strategy by how I personally feel about it, it would be one of the most grossly offensive things you could say. And it still makes me uncomfortable to use it. But the lesson here appears to be that I shouldn't use myself as a reference for how to interact with other people.


It sounds to me like you want some way to engage with what the other person is sharing. I find that I get a lot of mileage out of asking <i>really dumb questions.</i>

So with your example, I would first accept their feelings - we've all been insecure about jobs from time to time - and then try to probe into them.

"Has your boss been talking about money being tight? Did one of your big customers just drop?"

"Has your boss been talking about your performance? Do you see others on your team being dismissive of your role?"

Questions like this let the counterparty know that a) they matter to you and b) you're hearing what they're saying. I think that's what you're saying you want to convey. I could be way off base here.


It's very cool that you are sensitive to how frustrating saying "that sucks" is for you. Many people are looking for just that, though. It might be informative to try out "that sucks" enough times to see what response it gets from the person you're interacting with. You might be surprised. (I was.)


This is hard for me too. If it's a big complicated thing, I try to recapitulate what they said which then leads to them feeling more listened to. That way, I stay busy and feel like I am engaged without trying to solution for them. If it's a simpler thing, this advice doesn't work and can feel condescending. Ymmv.


> Let's say someone is telling you they are fearful for their job, they think they will get fired soon, even though they have nothing specific to point to. As a listener, are you agreeing with this or are you neutral nodding your head?

As a listener, I'm my goal is to create an environment for them to talk about what bothers them in the most vibrant, and exploratory way possible. I realize that's not exactly the most helpful explanation so allow me to go into more detail. There's a few conversational techniques that I pull from heavily when I'm trying to actively listen: conversational orienteering, and open ended questions, non-Sorcratic questioning.

For lack of a better term[1], conversational orienteering is actively being aware of the topic of conversation and its local topology. Given a topic, one should be able to generate several other topics: one that is more abstract, one more specific, and several adjacent. Over time, a listener gets a sense of where a conversation wants to go and uses the conversational topology to orient towards that goal. It took me a bit of practice to be good at picking topics not too far and not too close to the one at hand - too far can make conversations feel disconnected and random, and too close can make someone feel like they are being misunderstood.

Secondly, I don't think open-ended questions needs much explanation, but when someone is venting or needs support, hows, whys, and whens give the speaker much more room to express themselves than 'Do you...'s.

Thirdly, it's important to be non-Socratic in questions and responses. Leading the speaker is much much worse than telling them advice and should be avoided at all cost.

If you've ever worked a problem out verbally, you should be able to recognize that these principles work to cultivate a good verbal environment for the speaker. I don't see them as not helping, so much as creating an environment where they have the best shot at verbally processing their issue. I think it's important to recognize that emotions can get in the way of people being able to take action and that speaking can help diffuse strong emotions so that someone is ready to take a concrete step toward fixing their problem. I've seen that happen a lot. Even just feeling understood can help people feel better about making a real decision.

It's probably also important to point out that there are some people for which verbal processing works really well and some who can complain endlessly. It's important to recognize the difference. For the later, value your time. Maybe give them 15mins of listening and then decide to change the subject, for them verbal processing is not going to help. They probably need to work on issues in a clinical or therapeutic environment you cannot provide.

Hope this gives some insight, and even if it doesn't, feel free to tell me too.

1. If this actually has a term, please let me know. I'm coining one just to be able to talk about it.


> My ultimate takeaway is to now default to listening without advice.

Eve when it’s not listening to someone who’s venting, that can be really powerful anyway.

The best sys admin I’ve ever work with used to keep a teddy bear on the end of her desk. When people came to her with a question or problem she’d say “talk to the bear”. It’s astounding how often explaining the problem to an inanimate object results in the solution becoming obvious to the person ding the explaining.

(Note, she was really good at not saying in a rude or dismissive way, but she was somewhat on the spectrum and we ran a lot of cover to ensure the CEO didn’t get told to talk to the bear…)


https://en.wikipedia.org/wiki/Rubber_duck_debugging

(At first I thought “talk to the bear” was some sort of folksy Eastern European way of telling the asker to go to hell)


This is why "rubber duck debugging" works.

I've had good luck explaining any thorny technical problem to any inanimate object on my desk. Often times, the mere act of doing this makes me really pay attention to my assumptions and the information I have gathered.


Another useful thing to say, “oh no that sounds terrible, what are you going to do?” It can help reframe from complaining to strategizing, and that can make people more receptive to outside ideas.


Depends on the person as to whether I'd say that. With an employee who's constantly moaning about everything - I'd absolutely say that.

With my wife? Noooo, it would sound like I'm saying "I'm not interested in your problems unless you have solutions". As her partner, she wants me to share the burden of her problems, even those for which she has no solution.


I wouldn’t recommend this. First of all, you shouldn’t provide personal opinions such as “terrible”. Then, asking what they are going to do forces them to confront the problem which they may not be ready to do yet, or may not want to articulate to you.


Usually in the sort of situation where you'd say this, you're just reflecting the speaker's very-clearly-expressed emotional state back at them to demonstrate that you're actively engaged in listening and considering their statements.

It's not something you'd say in response to a text complaint, where there's not enough "bandwidth" to clearly communicate the complainant's emotional state; but it's something CSRs are trained to say on phone calls all the time.

It's also the reason that therapists vastly prefer speaking in person, to video calls, to phone calls; and almost never even consider doing "therapy via text chat." There's not enough bandwidth in text chat to enable a therapist to properly engage with and respond to the emotional content of a client's communication; but with each additional level (voice, video, in-person meeting), that's more possible.

(Interesting consideration, given that: suicide/crisis hotlines should probably consider offering video calls as an option, as the increased bandwidth for emotional content will allow the operator to engage with + potentially help the caller on a deeper level.)


I’m sort of inclined to think that people calling suicide hotlines are probably not that enthusiastic to hop on a video call.

Just reaching out is hard, and you want to be as anonymous as possible.


> Marriage has taught me to go even further than that. I now ask "are you telling me to get it off your chest, or you want help solving it?"

I may be much slower to adapt. My wife of (almost) 30 years usually starts with explicit “I am telling you this to just get it off my chest”.


Thank you for the reminder -- it does feel like people can be in (at least) two different modes -- with a desire to vent and be heard, or inquiring about a solution. Yet it is not obvious which since the two can sound so similar.

If someone is grieving it's probably time to just listen, but when someone is stuck with a social problem they may be rubber ducking with you rather than considering you to be a good approximation of an oracle ;)


"Rubber ducking." As in speaking to your rubber duck with no expectation of a response? First time seeing this usage. Thanks.


I think they’re probably referring to https://en.m.wikipedia.org/wiki/Rubber_duck_debugging


Moreso than that, imagine a rubber duck floating in the water: silently looking at you, nodding in understanding.


A way to deal with really perplexing bugs is to just carefully explain the code to an actual rubber duck.

"This code is obviously correct, right duck? Look here, this line first does x, then y happens and here... Wait a minute, that doesn't do z at all!"


Congratulations, you are one of today's Lucky Ten Thousand! https://xkcd.com/1053/


The only problem is that you often hear the same variation of the problem multiple times with no action taken to resolve it in between.

That frustrates me.


I'm guessing it frustrates you because you like solving problems? You hear someone stuck in a rut and you want to help them out of it?

Totally with you on this. I'm a solutions architect by day, and my entire skillset is helping people solve problems.

Do a role-play: someone comes to me complaining about how it's really frustrating having to type all this crap into Excel, so I suggest using OCR, or taking a course on getting quicker with the numpad. Unfortunately, I missed their real problem: they hate their job. Me telling them "here's how you could be better at a job you hate" doesn't really help them, it simply looks uncaring and assumes they haven't already thought of those things.

So I could just nod and say "oh that's sound terrible" every time they mention it. You're right, it might look crass and robotic.

Even better here would be saying "Wow, typing all that crap into Excel, you mentioned it last week as well. Sounds like you really don't enjoy doing that?" and encourage them to expand a bit. Is it the typing? What makes it so frustrating? Do they think it's their job in the first place?

Eventually, they admit to you (maybe they hadn't realised themselves) that they hate this bit of their job, and need to discuss with their manager not doing it any more. (Or maybe they hate the company they work for, and need to find a new job. Or it's actually the keyboard they're using they hate. Or whatever, you need to listen to find out.)

This is how you help them out of their rut. They feel that you're interested in their problem, and when they do find a solution, they'll own it because they found it.


My challenge is that to be able to usefully respond to people’s rants, I need to empathize with them and expend at least some mental effort to understand their problem.

If they go on a rant about something, that dumps emotional and mental load onto me.

If they don’t resolve, or attempt to resolve it, that means they’ll continue to dump it onto me - and even worse, it will be a boring, already heard it problem with no new information!

If they continue to do that, and I continue to listen, I’m essentially their emotional garbage dump and enabling their lack of dealing with their actual problem and frustrations.

Even worse, it is often hard for me to get my mind off an unresolved problem. So then it bugs me.

I like solving problems because then I have a lot fewer things bugging me. They almost always result in progress in other ways too, and accomplishing things, which is nice.

Even worse still if it’s the kind of problem they are making for themselves, or are intentionally not trying to solve. Of which there are many.

Eventually, I just don’t want to be around them, or get progressively more blunt with changing the subject because it makes it exhausting and unpleasant for me being around them.

Some people seem to be able to just ignore the emotional affect or load, and get whatever they want from the convo, and I can do so if I exert effort to do so.

But life is too short for this kind of BS on the regular.


Even better is when there's a agreed upon action and then they just abandon that plan, leading to the same discussion and plan,, only for it to be abandoned again...


I'm sorry that it frustrates you, that must be difficult.


I'd prefer we live in a world where idle complaints are not entertained. If you want advice, complain. If you do not, keep silent.


You should probably not say this sort of thing in public as it may cause people to view you as an emotional or intellectual cripple.


Then shouldn't you, by your own principles, have kept silent instead of posting that complaining?


I don't think my post is a complaint, more an expression of desire. It has also spawned an interesting discussion, which seems to be the idea here.


That's exactly a complaint.


This is a bit pedantic. I did qualify the word complaint with the word "idle". A broad enough definition encompasses any desire for change in the world. There must be a distinction between statements which invite meaningful conversation and those which do not[1].

1. https://www.youtube.com/watch?v=XIJYO4u5iug


Venting is a pretty normal and healthy way of dealing with emotions.


Are we sure that it's healthy?

I mean within reason I'm sure it's fine.

But we probably all know people who complain about the same things incessantly, with no desire to change them. And at some point it's reasonable to decide if those are people who you really want to continue to invest time into.


And responding to venting with advice/criticism is also (clearly) perfectly normal right?


Sure, nobody's saying "you're a bad person for offering advice".

In some contexts, though, offering advice can feel like you want to close the person down rather than listen to them, that you think their problems aren't serious enough because you'd solve them easily. I'm guessing you've had at least one occasion where you have a work issue, and your manager is casually dropping solutions that didn't work, and you were frustrated with them as a result.

As such, the consequence of offering solutions is that it can damage your relationships with people, or at least not use an opportunity to strengthen them.


To recenter the conversation - in a personal context idle complaints (ie. venting) are considered rude, and are often accompanied by an apology, for a reason. You're basically monopolizing a person's time, and expressing explicit disinterest in their perspective. Using complaint as a coping mechanism is a fundamentally selfish thing to do[1]. Therefore I don't think we should tolerate it idly. If you want to talk and only be listened to, talk at an inanimate object. If you want to be an equal party in a conversation, speak to a human being.

In a work context, it should (always) be about most efficiently solving the problem at hand. When I have a work issue, I preface my request for support with the steps I have taken to attempt to solve the problem. Anything else wastes the time of everyone involved. When this is done correctly, the first thing to come to the mind of the people I'm asking is often exactly what I'm looking for.

> your manager is casually dropping solutions that didn't work

Casual, useless, unsolicited advice is also a waste of time and energy (see "seagull management"). If my manager did this I would promptly tell them to either dig into the problem properly with me, figure it out themselves, or leave me to it.

1. https://www.youtube.com/watch?v=XIJYO4u5iug


> You're basically monopolizing a person's time, and expressing explicit disinterest in their perspective. Using complaint as a coping mechanism is a fundamentally selfish thing to do[1]

Yep, and allowing other person to do all this to you is definitely spoiling. At the same time, a possibility and ability to spoil someone you love - is one of the biggest pleasures in life.

(I’ve shown the video to my wife. She said: “See, you could have done much worse”)


> If you want advice, complain. If you do not, keep silent. reply

I couldn't agree more, I would amend the above with "unless you are sure you are loved by your listener, and are willing to impose on them" =)


> that you think their problems aren't serious enough because you'd solve them easily

That would be a rather strange reaction. A single brain gets easily stuck on a problem, so if involving the second brain helps that does not mean that the problem was easy. Or that the first brain was defective. (Frankly, I think it was evolutionary “cheaper” to implement the rule “if stuck - consult” than to implement an unstuckable brain).


Curious, does this apply to romantic partners too? Personally, I'd be sad if my wife didn't share things troubling her that she didn't need my help solving. I like knowing how she's feeling about things.

But at work, I understand this mindset. Though personally, I still actually don't mind hearing people complain. And since I'm a manager, complaints are a very useful signal for me: even if I'm just in listening-mode, they give me more clarity on precisely what's going on in my team.


Of course I don't callously dismiss my romantic partner when she complains. We both also recognize that complaining is fundamentally indulgent, pointless, and selfish, and strive to develop better coping mechanisms. Even when suffering greatly, I am loathe to complain. When I do complain, I am sure to apologize.

As a leader, actionable complaints (read: criticisms) are indeed a very useful signal, and I try my best to pay attention to them.


Do you always feel a need to apologize when indulging in something that makes you feel better? Why is it that you feel you're not entitled to do something selfish that makes you feel better and doesn't hurt anyone else?


> doesn't hurt anyone else

If this is actually true then clearly there's no need to apologize. However if I've selfishly imposed a one-sided conversation on someone else in order to soothe myself, of course it's correct to apologize. Who enjoys participating in a one-sided conversation? Most people tolerate them out of sheer politeness.

The whole idea of good manners is to avoid imposing on other people, be that physically, emotionally, or conversationally.


> Most people tolerate them out of sheer politeness

You are projecting. Some people are flattered to be a trusted confidante or emotional support, and glad to be able to help someone they care about. This is situational and dependent on factors (if someone's emotionally leaning on me every second of every day, it's going to get tiring pretty quickly), but even if the experience of the conversation _itself_ isn't exactly pleasant it might still be considered a worthwhile discomfort to go through for the emotional closeness generated (as a parallel - physically exercising isn't (often) pleasant, but the sensation afterwards and the physical well-being generated are considered worthwhile, so the activity is net-desirable even if it's unpleasant in-the-moment). In fact, apologizing for the act might insult the listener, implying that your relationship isn't strong enough to warrant such sharing. Further, the listener might care about the speaker's mood and state of mind so much that, even if the experience is net-negative _for them_, they're still glad to be able to provide that support to someone they love.

This is all subjective - you and your partner might so dislike being vented to, or feel such negligible positive effects from it, that the calculus ends up negative and an apology _is_ genuinely warranted. But it's not necessarily true for all (or even, I'd guess, most) people. You're right that avoiding imposition is good manners, but it is not necessarily the case that sharing feelings with someone is an imposition on them.


Leaning on someone for emotional support unprompted is an imposition, just like relying on someone for financial support. Yes in some cases the imposition is welcome, and fosters closeness and interdependence, but in most cases it is better to be self-sufficient (emotionally and financially).

You'd surely apologize when asking even the closest friend for financial support, why not when asking (or worse, demanding) emotional support?


+1 to this advice. I've heard it as "do you want comfort, or solutions?"


This sounds really patronizing. I would be careful with that phrasing. People who don’t want their problem solved often know the solutions and don’t like the tradeoffs or change they entail. It is often not a knowledge problem.


It also implicitly discounts one of the most valuable processes: verbal processing. Some people, myself included, find themselves verbalizing a problem and the tensions in every choice and monitoring the logic and emotional response present in saying it out loud.

In this way, listening and solving aren't too dissimilar. Simply listening can give the speaker an appropriate environment in which to solve their problem. A listener can play a part in helping to solve the problem, but helping foster the environment in which the problem can be solved. Don't mistake this as a silver bullet, but simply recognize that being a listener is an underappreciated role and listener vs solver isn't as dichotomous as it sounds.


> It also implicitly discounts one of the most valuable processes: verbal processing.

Not really. The question, more generally, is: what should my role be in this conversation? Should I be an active participant in solving the problem? Or should I support you as you work through it?


I think the implication is that by listening passively you can be an active participant. That is to say, speaking the problem out loud causes it to run through alternate pathways in the brain which helps the person sharing their issue resolve their own problem.

As with so many things in life, the hard part is working out if your actions should be motivated by actually helping or feeling like you helped.


> This sounds really patronizing.

I think generally the person you’d say this to is already aware how the conversation will go if you don’t clarify beforehand.


Or, the way I do it: "do you want me to just listen, or do you want me to offer advice?"


This is soooo important ! (And not just in marriage...)


Exactly. Being on the receiving end of unsolicited advice is truly annoying, which most posters here seem to be ignoring. Unsolicited advice is annoying, no matter what insincere bullsh*t you wrap it in


What is the point of discussing a problem if you don't want advice? Implicitly whining about something is like giving advice to the listener what to not do or what does not work properly etc.


1. To seek comfort from a fellow human being. 2. To vocalize it in hopes of coming up with your own solution. 3. To vent emotion; “get it off your chest.” 4. To share an aspect of your life with someone you like, love, or respect.


A very useful and practical question at the right time is "Is there a request in there?"


I learned to announce my point when complaining as in saying "I'm just kvetching, I'm not looking for a answer" or similar phrase.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: