3 ms·
Some good items in there but I disagree 100% with Guideline 25: > Write at the right time. Sharing something at 5pm may keep someone at work longer. You may ha
by andsoitis 3y ago
Some good items in there but I disagree 100% with Guideline 25:
> Write at the right time. Sharing something at 5pm may keep someone at work longer. You may have some spare time on a Sunday afternoon to write something, but putting it out there on Sunday may pull people back into work on the weekends. Early Monday morning communication may be buried by other things. There may not be a perfect time, but there’s certainly a wrong time. Keep that in mind when you hit send.
Guideline 15 states:
> Communication shouldn’t require schedule synchronization. Calendars have nothing to do with communication. Writing, rather than speaking or meeting, is independent of schedule and far more direct.
Guideline 9 states:
>"Never expect or require someone to get back to you immediately unless it’s a true emergency. The expectation of immediate response is toxic."
When you embrace asynchronous communication and you expect people to manage their own time, you should be empowered to send a note at any time because recipients should have the maturity to manage when they read. If something is truly urgent, the sender will find a way to reach you (e.g. phone), but those cases are very rare indeed so not worth having a process for.
- margalabargala 3y agoI think this depends on the relationship between sender and recipient. If they are peers, then yes, send whenever. If the sender is in a hierarchy above the recipient, then the mere fact that they are communicating with them inherently includes that hierarchy and places pressure upon the recipient. You can trust the recipient to be mature and manage when they read, as much as they can trust you to be mature and not fire them for failing to reply.
- andsoitis 3y agoThat's a good example where power dynamics can infuse expectations. What I have found is that power dynamics also come from other dimensions that are not encoded in official company hierarchy but more about social hierarchy. They can also be implicit amongst peers, such as someone with more tenure than someone with less. Or personal traits such as being outgoing vs. more shy. I'm sure there are many that are informed through one's culture, background, etc. If you have a geographically distributed company, then picking the "perfect time" can get very awkward. Maybe the solution out of this is that they can collapse the set of guidelines into fewer principles that are centered around themes, such as: "audience", "clarity", "modes", etc. and focusing on desirable outcomes, rather than prescriptive implementation details.
- Sammi 3y agoYou're applying non-contextual black and white thinking. The article leaves room for context and nuance.
- mdekkers 3y agoNot really, and they (op) are rather specific, pointing out the issues specifically and directly
- andsoitis 3y ago> You're applying non-contextual black and white thinking. The article leaves room for context and nuance. Maybe. On the other hand, I would rewrite these 30 guidelines into a more condensed set of themes that describe desired outcomes rather than implementation details. That would leave much more breathing room for not only context and nuance, but also future cases that were not specifically envisioned in the original set.