[chuckcode]

Please write a collaborative doc instead of an email if you have that much detail. Having an effective discussion over email is actively painful and worse yet no one can refer back to your detailed documentation later.

Good on you for communicating. Personally I've found that details are great, but being able to distill that core message down to a quick code really helps. Call it an elevator pitch, sound bite or whatever but it is really transformative. So much communication seems to be just passing along a historically linear repeat of facts rather than helping reader by distilling down.

[sjg007]

Email is the worst but a close contender are Slack messages and threads .... Confluence is somewhat better but comments are not handled well with respect to the source document. Add in Smart sheet and the rest as kludges and I have 10 different things to check for a single project with dependencies.. it's nuts. I am not sure if anyone has really figured the information based workflow out yet. There needs to be some auto association and project based aggregation (maybe tags?) .. that and a personal workspace of things you need to do in each system.. right now everything is asynchronously propagated by slack or email.

I am interested in trying out Asana and Facebook Workplace to see if they have solved this in a more natural way.