Scan barcode
A review by synoptic_view
A World Without Email by Cal Newport
I skimmed this a few months ago, realized my fundamental issue is not email, and set it aside. I returned to it recently, because my issue is excessive task switching induced by working on too many projects and over-commitment to advising/seminars/random stuff. Ultimately, Cal is arguing that task switching is the productivity killer. He focuses on the switching induced by email. For me, email coming in and disrupting my work is part, but only a small part, of the problem. I wanted to see if the overall lessons about avoiding task switching could be valuable.
The book has lots of concrete and potentially helpful advice. Unfortunately, I am already implementing a lot of it. I use a trello board system very similar to one that Cal endorses. The book helped me rethink some of the specifics of how I use that board, like breaking teaching/advising into its own separate project space away from my research cards. I am also using the cards more aggressively as project note spaces and full project cycle trackers rather than just to do lists. That way I can just look at my trello board when I get to work rather than referring to an email or slack conversation. It also helps me close browser tabs--a source of personal distraction and side tracking similar to email.
Ultimately, the book reinforced something I already knew. If I am doing a lot to avoid task switching and to systematize my work yet am still feeling overwhelmed, then I need to either simply work on fewer things or hire more labor.
I do really want to implement the intensive programming work arrangement Cal describes. Two programmers work as a team for 6 hours a day on a problem. Their manager monitors their email, responding on their behalf and debriefing the programmers quickly at the end of the day. I love working intensively as part of a small team. I just need someone to be my manager. Who wants the job?
The book has lots of concrete and potentially helpful advice. Unfortunately, I am already implementing a lot of it. I use a trello board system very similar to one that Cal endorses. The book helped me rethink some of the specifics of how I use that board, like breaking teaching/advising into its own separate project space away from my research cards. I am also using the cards more aggressively as project note spaces and full project cycle trackers rather than just to do lists. That way I can just look at my trello board when I get to work rather than referring to an email or slack conversation. It also helps me close browser tabs--a source of personal distraction and side tracking similar to email.
Ultimately, the book reinforced something I already knew. If I am doing a lot to avoid task switching and to systematize my work yet am still feeling overwhelmed, then I need to either simply work on fewer things or hire more labor.
I do really want to implement the intensive programming work arrangement Cal describes. Two programmers work as a team for 6 hours a day on a problem. Their manager monitors their email, responding on their behalf and debriefing the programmers quickly at the end of the day. I love working intensively as part of a small team. I just need someone to be my manager. Who wants the job?