News for hackers. Stuff that matters.
Re:A guide to difficult conversations by tyingq on Tuesday March 26, 2019 @10:37AM (#19492217)
"how you recognize when you are being patronizing"

That's a good point. I'm fairly adept at recognizing when someone is trying to negotiate with me based on some kind of taught methodology. Because most of what's taught is counter to how you would do it naturally...thus it stands out.

Once you recognize it, the natural reaction is to feel like you're being manipulated with some technique.

Re:A guide to difficult conversations by waylandsmithers on Tuesday March 26, 2019 @11:16AM (#19492608)
I think part of it is that the observation needs to be genuinely objective rather than veiled evaluation.

For example, when I did tech support I would occasionally get chat messages from my supervisor along the lines of:

"Hey, I see that you closed out Ticket #XYZ without any resolution or response sent to the requester."

(waits for response)

(waits for response)

(waits for response)

...and it would make me furious, regardless of whatever the situation was.

Re:A guide to difficult conversations by ben509 on Tuesday March 26, 2019 @12:27PM (#19493288)
Is it even possible that that could not be an evaluation? I've been on both sides of that exchange, and it never even occurred to me that pointing out a ticket wasn't properly filled out was an evaluation. The ticket itself is often the only proof you actually did your job, after all.

Personally, if I'm on the receiving end of that, I'd rather the boss say, "please update this ticket with X and Y" rather than making an "observation." It can't be condescending nor manipulative since that person is plainly exercising their authority. And you can generally resolve problems with an instruction by pointing out that it won't work, or it conflicts with others, etc., which avoids it getting personal.

(This may be why I rarely had these issues in the military, and noticed that many veterans report a great deal of confusion when they get into civilian life because "nobody knows their lane.")

Re:A guide to difficult conversations by cimmanom on Tuesday March 26, 2019 @01:18PM (#19493900)
If I did that, there would be an implicit "I'd like to know why" on the end of it, with the understanding that there might be a very good reason. But now that you point it out, I could see how that could come across as a criticism, too.
Re:A guide to difficult conversations by logfromblammo on Tuesday March 26, 2019 @12:26PM (#19493279)
"Is there something you want me to do?" is a slightly less hostile way of saying "Get to the point."

"The petitioner did not make a request upon which relief can be granted." might set off a snark detector, and "The ticketing system already automatically notifies the requester that their ticket has been closed." might inadvertently imply that the supervisor does not know how to do their job.

Re:A guide to difficult conversations by dodobirdlord on Tuesday March 26, 2019 @11:46PM (#19498024)
My habitual response to these sorts of messages has been to just affirm the statement.

> "Hey, I see that you closed out Ticket #XYZ without any resolution or response sent to the requester."

> "yes" / "yup" / "indeed" / "true"

It's an effective way to sidestep having to pay attention until the person comes up with an actual question or request.

Re:A guide to difficult conversations by logfromblammo on Wednesday March 27, 2019 @10:28AM (#19501077)
"That is a true statement." is one that is frequently used around here. It sounds very engineer-y, and has no inflectional or emotional connotations whatsoever. It's about as sterile as a SYN-ACK packet. I heard what you just said, and evaluated it for correctness. Current computation completed, and ready for additional input.
Re:A guide to difficult conversations by Noumenon72 on Wednesday March 27, 2019 @12:43AM (#19498225)
That wouldn't bug me at all. People who totally respect me would ask me that. "Why didn't you put a resolution on Ticket XYZ?" blames me. "There is no resolution on Ticket XYZ" states a fact and lets me offer an explanation of why I do that kind of thing. Or, like as not, investigate how I closed the ticket by accident or assigned it to someone else who closed it. There are usually lots of good explanations and if you can't even raise the subject without getting mad, you miss those opportunities to not screw up. Maybe I thought no one cared about the resolution and this teaches me someone does look. It's a positive thing to do IMO.
Re:A guide to difficult conversations by skolsuper on Tuesday March 26, 2019 @09:13PM (#19497409)
At the same time, if it comes from a place of genuine concern, even unnatural communication can be empathetic. I once asked for help on an online forum, and one person responded with something along the lines of "I don't know how you feel, but if that happened to me I'd feel terrible". In the moment, it felt very carefully crafted, but the care with which the words were chosen really amplified their impact to me.
Re:A guide to difficult conversations by jacobwilliamroy on Wednesday March 27, 2019 @02:07AM (#19498497)
I've been in that scenario and NVC still worked. In that case the person I was talking to felt anxious when I practiced NVC in our conversations because they needed freedom: to think their own thoughts and make decisions etc.

I asked if there was some way I could speak to them that would help them meet their need for freedom. Then we both laughed and the situation defused.