Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

This is a valid approach, but it does have a problem: it can lead to long back and forth messaging/email exchanges, including lengthy messages.

I don't, generally, have time to write long messages, nor (often) to read them, so as soon as I see this happening I've started to point out the behaviour and set up a short meeting to resolve whatever the issues are.



Maybe those short meetings loose some of the nuance of the longer written discussion and lead to worse decisions.

I'm reminded of Amazon's supposed culture of well-written memos ahead of meetings.


There is no guarantee that a short meeting will resolve something that has already been the subject of a long discussion, though I will grant that long discussions are often the result of at least one party not paying attention to what the other is saying, and only the intervention of a third party can break that deadlock.

Having one party who only reads the subject line before replying will sabotage any attempt at resolving an issue through email.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: