Scan barcode
synoptic_view's review
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?
aneesasona's review against another edition
2.0
It’s not that I think Cal Newport is wrong.
I just think he’s self-important, out of touch, and at least five years late with the content of this book.
How was this published in 2021 with a long-winded explanation of task boards and somehow zero mention of the pandemic and remote work?
I just think he’s self-important, out of touch, and at least five years late with the content of this book.
How was this published in 2021 with a long-winded explanation of task boards and somehow zero mention of the pandemic and remote work?
romcm's review against another edition
1.0
I had to give up on this one. It just made me want to cry and quit my job. Stand up meetings, increased productivity, depersonalization of email addresses... Without relationships, what’s the point of living? We’re just cogs in a machine on a dying planet.
benrogerswpg's review against another edition
3.0
This was a really good book.
Move aside Jordan Peterson's use of "benevolent"! ...
This book had the words "Hyperactive Hive Mind" used a shocking 142 times in the book.
I found the book a little jumbled and scattered at times. It went all over the place. It wasn't organized too well (to my liking).
Not entirely just about emails and solutions neither. Emails definitely was a majority of the book, but in no way was it entirely the contents. Honestly, it was about 52% of the book.
All in all, this was a good business book.
Some really great strategies and goals for companies to use.
I got a lot out of this book, and took a lot of notes.
3.5/5
Move aside Jordan Peterson's use of "benevolent"! ...
This book had the words "Hyperactive Hive Mind" used a shocking 142 times in the book.
I found the book a little jumbled and scattered at times. It went all over the place. It wasn't organized too well (to my liking).
Not entirely just about emails and solutions neither. Emails definitely was a majority of the book, but in no way was it entirely the contents. Honestly, it was about 52% of the book.
All in all, this was a good business book.
Some really great strategies and goals for companies to use.
I got a lot out of this book, and took a lot of notes.
3.5/5
eososray's review against another edition
3.0
This book identifies a definite issue, there is no doubt that email sucks up a lot of work time. Though the ideas to solve this are some variations on doing meetings or picking up the phone or using some kind of organizational software. Which depending on your organization, could work. The smaller the place the easier to make it work in my experience. Though a lot of this seemed to rely on the management team to identify this issue and resolve it, and I would say that would be the most difficult part in the process.
Still interesting, but maybe not the most practical solutions.
Still interesting, but maybe not the most practical solutions.
caszriel's review against another edition
4.0
This was a really enjoyable read, a lot for me to digest. Considering how much Deep Work added to my life after I read it I was certainly excited to read this one as well; gotta pick up Digital Minimalism next!
simazhi's review
4.0
Cal's books have had quite a profound impact on my professional life. Equally, this one will have an impact too, but it won't be as revolutionary as his Digital minimalism, Deep work or . Many of the take-aways from the book are things that have become more mainstream in the past few years, like using kanban-style boards for project management. I've implemented some of them with Notion based on a youtube recommendation, like a year ago; and I was late to the party.
So, yes, read it, take notes and apply, but read the other books first.
So, yes, read it, take notes and apply, but read the other books first.
juliana_aldous's review
3.0
Deep Work was so good and so I was disappointed with this one. Deep Work had a central theme and I feel this one suffers from too many ideas. This is exactly the kind of mishmash I hate in many tech-focused business books talking about this or that technology or process. It reminds me a bit of Timothy Ferris.
That could be me. I've read too many productivity books over the years and I think I'm a bit jaded at this point. I had a hard time focusing on the book.
That could be me. I've read too many productivity books over the years and I think I'm a bit jaded at this point. I had a hard time focusing on the book.