3 ms·
I’m creating an account just to reply to this, and for some context: I’m a big Cal Newport fan. He isn’t arguing against the use of email, but the non intentio
by onetimename 5y ago
I’m creating an account just to reply to this, and for some context: I’m a big Cal Newport fan.
He isn’t arguing against the use of email, but the non intentional default to emailing instead of work. Yes, your ideal scenario- communication between employees will get work done. But in Cal’s scenarios, that one person is having multiple conversations like that through email, and is waiting for the other person to reply. And instead of producing deliverables, they are having these slow conversations.
You mention just get to the email later, but rarely does the application or notification go away after the info is gathered. So your plan of checking email 1-3 times a day is right inline with Cal’s thinking.
Some of his solutions he hand waives away complexities with “we’ll rock and roll” but the idea is email won’t be a springboard for work. It sends pdf’s and reports and minutes great, but planning a project is better done elsewhere.
- rdiddly 5y agoHmm maybe I agree with him more than I think I do then. And yeah I've enjoyed at least one of his books and "feel like" I've read another just because of how often it gets quoted to me, haha. Definitely there are at least two ways of screwing up, and they're both about using the wrong tool for the job. One is to use urgent methods for stuff that's not urgent (which bothers people). And the other, which it sounds like you're alluding to, is using a non-urgent method (email) for things that truly are urgent. Or that are, to use a metaphor, "bandwidth-intensive." You can usually get a heck of a lot more communication done faster in person than you can by email. Although much of it will be lost into the ether, too... unless someone's taking notes. Everybody just use the right tool for the job okay? Great, that's settled!