|
|
|
|
|
|
by function_seven
1593 days ago
|
|
|
Right. We both know you're going to ask a question. So fire away. I don't mind a "Hi." followed by some [user is typing] followed by the actual question. It's the naked "hi" with nothing else. The "hi" that's just dropped there awaiting me to confirm that I'm now a part of a conversation I know nothing about. Emails have subject lines and require the sender to write out what they want. Phone calls leave me the option to pick up or let go to VM if I'm not available. But DMs are the worst of those two: text like an email, realtime like a phone call. For some reason those seem to correlate with users who want me to do their work for them, or are about to drop a request that I have no time for—and don't even have the time to explain why it's not my domain or a good fit for my schedule. These are requests I'd love to get via email so I can respond on my own time. Or as a voicemail. Or even as a written out DM. But not as another message in "a conversation we're having now." |
|
|
Was it a nuisance when work from home started more and more people switched over to this pattern.
Nowadays I am just fed up with it.
But it might be because after 23 months we (the company I am working for) still haven't been able to learn how to replace most meetings with forms that don't take up that much synchronous time.
Most meetings I am in could be at least cut short when prepared up front by a document that enables commenting. Then one could discuss ideas and not need to generate them on the fly.
And then there are the few cases where the need is to brainstorm. These can be fun. And I like them. But they are for cases when the map/way/ideas are yet unknown.
When the path is more clear things imho should be more asynchronously organized.