31–40 of 60 posts
I’ve seen colleagues share this or link to it in their Slack status. It feels a bit… odd to me. Yeah it’s maybe a bit annoying when people do this, but does it really need a whole campaign website? Not everyone is going to communicate in exactly the way you like.
I’ve seen colleagues share this or link to it in their Slack status. It feels a bit… odd to me. Yeah it’s maybe a bit annoying when people do this, but does it really need a whole campaign website? Not everyone is going to communicate in exactly the way you like.
I disagree. I start text chats with "hello" all the time. It basically relates to channel choice. For some kinds of messages a near-real-time text chat is the right channel but async email-like flow would be entirely the wrong channel. So I start a convo with "hello" to probe if the other party is available for near-real-time text chat, because away-status indicators are frequently unreliable. There are also special…
What's an example? I encounter maybe one situation per month where I'd consider asynchronous communication "wrong", despite having multiple synchronous meetings per day.
In the situations where it is wrong, no one (IME) pings anyone with "hello......", They schedule time on a calendar (asynchronously).
Earlier quoted context omitted.
...I really don't think there's "emotional cost" on the part of the recipient in entertaining a "hello", at least not in peer-to-peer scenarios. Now, if you're someone's boss and hitting up a subordinate with whom there is known "bad blood" then I get the point about the "emotional cost" of a scenario where you write, close to the end of the business day, "hello", then your subordinate doesn't respond for 10 minutes.…
I think there is an emotional cost in receiving a work-related message that only says "hello". My data point: it enrages everyone I know. And they lose respect for the person who said "hello" and wasted their time.
Probably that’s the thing to solve for, not “hello”, “query” vs “hello, query”.
For now, I just settled on being more patient and stoic about the "Hello" kind of people and to lead by example and not do it myself.
I’ve seen colleagues share this or link to it in their Slack status. It feels a bit… odd to me. Yeah it’s maybe a bit annoying when people do this, but does it really need a whole campaign website? Not everyone is going to communicate in exactly the way you like.
Sure, but do you put these differences down to individuality, or to culture?
If someone messages "hello", is this just social, is it that the person is blocked and cannot do anything, or is it a request for help where the person will probably be able to solve the problem (but would be quicker with help)?
Mismatches in cultural expectations lead to friction/conflict. I think it's generally going to be better to be aware of what the different expectations are.
Earlier quoted context omitted.
> If instead, I just open the convo with a drawn-out description of the issue i need help with, I'm kind of stuck after firing off a message to the first person. Succinctly, your whole strategy is wrong. Instead of round-robin'ing your way around the people, you should be broadcasting your message to an appropriate channel set to the group of people that can respond to your query.
Group chats have a problem with "diffusion of responsibility" [1], and sometimes you have reasons for not wanting to broadcast whatever it is you're about to say (e.g. you're in a toxic culture where your bosses will use the fact that you need help from others against you). I wouldn't round-robin my way through 10 people, but with 3 people it kind of seems fine to me. [1] https://en.wikipedia.org/wiki/Diffusion_of_re…
- You are going to get your answer faster
- Your query is only going to people you trusted to ask for help anyway
- The parties that were not able to help at first don't need to come back to you after to see if you still need help, and you don't need to respond with "never mind, someone else helped me".
- It's just more transparent to your colleagues about what you need.
- IT STILL AVOIDS THE NO-HELLO ISSUE
Earlier quoted context omitted.
...this is some rando posting something on github. Advice that's binding on the recipient is not advice, it's a command. And I don't take commands from randos on github. I also don't understand how this thread got so ad-hominem so quickly, with you acting like you know me well enough to put me in a category of people "who often ask for help", and then imply that those people are less entitled to autonomous choices on…
> this is some rando posting something on github Sure, but it's a post which strongly resonates with many people.
...the fact that there's resonance here is something I'm only beginning to become aware of right now, as I see how people are reacting right here to what I wrote above.
I say this with 6 years of work for fully-remote companies under my belt. In those 6 years no one has ever complained about a "hello", none of those companies had this in their "netiquette" guides, and I've been on the receiving end of "hello" many times.
It has just always seemed like the most innocuous and normal thing in the world to me. So it's really weird to see people reacting so strongly right here.