For software developers (engineering+product) these days, most of the deep communication happens over document review comments (say, in google docs, UX design t

For software developers (engineering+product) these days, most of the deep communication happens over document review comments (say, in google docs, UX design tools) or code review comments (in your fav code review tool). Usually, a meeting is called via a calendar invite which may come via e-mail (but you never have to actually see the invite email as the invite shows up automatically in the calendar along with invite message/note - very important). The meeting itself can be in person or on remote video call. In between these two, for any casual business (of status update, coordinating meeting etc) or casual seeking/providing help we have chat in your fav 1-1 or group messaging app (slack, hangout etc). I think e-mail is a poor replacement rich authoring and reviewing environments made for any specific type of document (PRD, Design document, code, UX design etc) needed in the SDLC workflows. But nevertheless, writing good e-mail is an important skill – whenever you have to engage with someone outside of your team or immediately neighboring team, you cannot just cold call or message them (too intrusive) you will have to write a formal intro mail and set the context etc. and then bridge into your more richer workflows.