6 ms·
Hard disagree back. Email has multiple contexts when I would say that short form is ideal and should be the default but at times a thoroughly long form email is
by conductr 27d ago
Hard disagree back. Email has multiple contexts when I would say that short form is ideal and should be the default but at times a thoroughly long form email is needed. Or, honestly, you just need to create a document at this point. It could be a slide deck or word/markdown/excel/etc (depends on context) and this should be in the email. But email is key.
My experience is that people search subject lines, conversations, dates, and generally traverse historical conversations much better in email than in chat or a fully external application. They won’t search Slack, or try but can’t find the conversation. They won’t remember it’s on a wiki, you’ll constantly be redirecting them to the url. If the file is attached to an email, sometimes they’ll resurface it from a year+ ago. I find that’s way more common than someone referring to a chat from even a month ago. Chats are semi ephemeral. I’ve used both Teams and Slack and feel neither has really changed the game in terms of how the entire user base of an org use the system, enabling the historical reference points and moving it out of a ephemeral state, so email remains a stalwart for archival purposes and helps provide maximum context after the fact (people tend to elaborate on their choices more when writing an email).
- deleted 27d ago[deleted]
- prepend 27d agoI’ve found that a two-prong approach works best. Detail in the email, expect people to read it or fail. And include a reference to a wiki or some more detailed version that can be collaborated on and extended. So the email isn’t the primary source, the wiki is (really some markdown in git). But the email is the thing that people organize and find over time.
- conductr 27d agoThis probably differs a bit by your exact profession and circumstances. I could see devs and technical people (most of HN readers) to prefer and have success with this when operating with like minded peers. It doesn’t scale much outside that. If you work with people outside of tech/dev minded people, those who are not used to RTFM type info seeking, it’s going to be an uphill battle.
- prepend 27d agoI think you may be right. Fortunately, I work with like 10k collaborators who are all science/tech oriented and it works quite well. I wouldn’t want to work in an org where people can’t read email and want to talk to everyone instead.
- conductr 26d agoI'm envious, although I think my experience is the rule and your's more of an exception. It might be more common on HN given the demo, but IRL, people mostly want to talk. Or even if they read email, they can't be bothered to search for things themselves. Makes me think of another long standing habit I have, I just ignore people. If they ask me something that has been answered and I know it's in an email somewhere, I ignore the question. If it's something they really need, they will go find it. Obviously this is very YMMV and I was able to start doing this after I reached a higher position/role, I've been a CFO for some time now and I still have certain people and audiences I will promptly answer any question even if I know it's been answered/documented.