Slow Productivity by Cal Newport: Good Reminder, Not As Good as Deep Work

Category: Book Review
August 25, 2026

Cal Newport has earned a permanent spot on my reading list. His book Deep Work: Rules for Focused Success in a Distracted World is one of my favorites. It changed how I think about organizing my work, and I still recommend it constantly.

So when Slow Productivity: The Lost Art of Accomplishment Without Burnout came out, I was excited. In Slow Productivity Newport says that our current definition of productivity is broken. Busyness has become a proxy for actual effort, but history’s most creative and impactful people worked very differently. I buy into this premise completely. Newport is one of the clearest thinkers writing about work and attention right now, and I always appreciate his thoughts. Here’s a review about what I found valuable and perhaps not as valuable about the new book.

Slow Productivity’s Main Ideas

Newport’s thesis is built around three principles, which I’ll reproduce here directly from the book:

Do fewer things. Reduce your obligations to the point where you can accomplish them with time to spare. Use that reduced load to more fully advance the small number of projects that actually matter.

Work at a natural pace. Don’t rush your most important work. Allow it to unfold along a sustainable timeline, with variations in intensity, in settings that are conducive to good thinking.

Obsess over quality. Focus on producing work of real value, even if it means missing opportunities in the short term. Let the quality of your output earn you more and more freedom over the long term.

Slow Productivity’s Best Advice: Only Work On One Project A Day

Newport writes three long chapters that go over not just these principles, but how to accomplish them. What he tends to do really well in all of his books is give very concrete, actionable examples. Slow Productivity does not disappoint on this front.

For example, his advice for doing fewer things is spot on. Newport gives us a framework for thinking through both the large and small obligations in our lives and determining which to keep and which to jettison. He says, limit your missions (your big, professional focuses) to 2-3 maximum at any one time, then limit the projects you take on within those missions and only work on one project a day. That’s right, just work on one project a day. Between your meetings and other obligations, you really only have time to do deep work on one thing a day anyway, so why not focus fully on that project and then move on to other projects later in the week? A day is a natural break point and allows you to really give each project the time it needs.

He also suggests limiting your meetings to half the day, maximum. If you put a meeting on your calendar, add some equivalent time to your calendar just for you, to focus.

Slow Productivity is full of tips like these, that bring some distinct clarity to how much we should be taking on and I appreciated that aspect of the book.

Historical Examples & Stories

Another strength of Slow Productivity are Newport’s historical profiles of people who did their greatest work by not working the way most of us work today.

Jane Austen was rumored to have finished her major novels writing bits and scraps in secret between visitors. Newport says if you research her life further you find that the reality is that she only found the time and space to fully finish and polish her writing after she moved to Chawton and shed most of her other responsibilities. The conditions for great work require protecting your attention, and attention requires space that busyness destroys.

Lin-Manuel Miranda took eight years between his first draft of In the Heights and its Broadway debut, not grinding every day, but returning to the work, gathering talented collaborators, stepping away, and returning again at a sustainable pace.

Mary Oliver wandered the woods and jotted notes as they came to her, working poetically rather than productively in the modern sense.

Newport’s argument, illustrated through these examples and others including Newton, Galileo, Georgia O’Keeffe, and Benjamin Franklin, is that the ebb and flow of intense work and rest isn’t a bug in how great things get made, it’s the reason great things get made. The pseudo-productivity that defines most modern knowledge work (the visible busyness, the Slack messages, the email chains, the packed calendars) is not just exhausting, it actively crowds out the conditions under which good work happens.

I find this argument maps onto what I’ve observed in my own career and in the careers of people I’ve coached. We have confused being busy with being effective for so long that many people have lost the ability to tell the difference.

Where It Falls Flat: Some Advice Doesn’t Land

For as much as I love Cal Newport’s work, several of his specific suggestions in Slow Productivity feel rehashed or even privileged. Only available to traditional knowledge workers with plenty of autonomy and partners holding things together at home.

For example, his advice to “write when the kids go to bed” assumes that you have a partner that isn’t vying for your time, that you have energy left after your kids are in bed, and that you don’t have a million other household tasks to do. Ask any working mom whether that’s a viable option and most would say, “hell no”. Do some women do it? Of course! But when I was working and writing a book, I found it far easier to find creative ways to reduce my meetings and use time during the day to get my pages written.

Newport basically also suggests that “quiet quitting” is a good idea. His recommendation to periodically reduce your visible output without telling your employer, is great if you have a decent level of autonomy and organizational trust in your work. If you’ve been killing it for a couple of years, you can do this. If you’re just starting out at a job, you need to get through that period of kicking butt before you can even consider this suggestion.

Similarly, his advice to “bet on yourself” by reducing your hours or salary only works for the right kind of person. For the rest of us, needing to make money from our hobbies and side projects comes with crushing stress. You need to know whether this will motivate you or kill your joy and happiness. Taking a short break to test this theory is likely a better place to start.

The practical frameworks buried in the book like the pull-based system for managing projects borrowed from Kanban thinking are actually quite good. But nothing here is groundbreaking and the frameworks get buried underneath the so-so advice.

Newport’s Core Insight Is Still Worth Reading About

Even when the specific advice falls flat, the core reminder is valuable enough, I feel, that the book is worth your time.

We are working too hard, for too long, without adequate breaks. Most of us know this and do nothing about it because we’ve internalized a definition of productivity that equates visible busyness with actual value. Newport gives you historical permission to question that definition. He makes a case, grounded in the lives of unarguably accomplished people, that the sustainable path to meaningful work runs through fewer things done more slowly and more carefully, not through more things done faster.

That message is worth repeating, even if this particular iteration of it isn’t Newport’s most elegant or his most practical.

If you want the version of this argument that comes with a rigorous framework and immediately applicable rules, read Deep Work first. If you’ve already read Deep Work and want the philosophical companion piece then Slow Productivity delivers that, even if it meanders getting there.

My Takeaways

From my own reading notes, here’s what I’m actually applying:

The holding tank and active list approach to project management is useful. I already use a Trello-based Kanban board to keep track of my to do list. This is basically Kanban applied to your own life, and it works. If you’ve never heard of Kanban, ask Claude about it or pick-up my easy-to-read book about how software is built. Chapter 6 is all about Kanban.

Double your timelines. This one is simple and almost certainly correct. However long you think something will take, estimate longer. The fear that you’ll accomplish less this way is usually wrong, you’ll accomplish the same amount with less suffering and more quality.

Schedule slow seasons. After a hard project, deliberately plan a lighter period. This is something I’m actively trying to build into my own retirement rhythm, and Newport’s framing gave me better language for why it matters.

Work poetically by finding your spot and your rituals that allow you to do your best work, then protect them. I write at specific times in specific places for a reason. I’m having a very productive morning at our local coffee shop today.

The Verdict

Slow Productivity is a good book about an important idea, written by someone who has written better books about adjacent ideas. Read it for the historical examples, the permission it gives you to work differently, and the handful of frameworks that are useful. But if you’re new to Cal Newport, start with Deep Work. It’s sharper, more practical, and in my view still his best work.


I also recommend Alex Soojung-Kim Pang’s book, Rest. Slow Productivity and Rest make excellent companions.

Search the Blog

Subscribe to Blog via Email

Enter your email address to subscribe to this blog. We will never share your email.

About Amber Field

Amber has over 20 years of experience working in the software industry with agile software teams and specializes in creating efficient, happy teams & clients while helping them scale, execute, and work / live intentionally.
Get to know Amber →

Check Amber Out On:

Browse Posts by Category

Recent Posts

Why I Keep Starting New Things in Retirement (And Why You Should Too)

Why I Keep Starting New Things in Retirement (And Why You Should Too)

The truth about retirement is, I’m still figuring out which challenges belong in my days and which problems I really want to solve. I’m still learning what it means to do hard things by choice rather than by obligation and how to find the right balance between the ebb of rest and the flow of something hard that I think matters. Here’s what I’ve figured out so far.

read more
The Best Part of Our Viking Rhine Trip Was After the Boat: Switzerland, Lake Como & Milan

The Best Part of Our Viking Rhine Trip Was After the Boat: Switzerland, Lake Como & Milan

Our extension, which went from Basel through the Swiss Alps by the scenic Bernina Express train, two nights in St. Moritz, another scenic train into Italy, a stop at Lake Como, and two nights in Milan, was fantastic. It had everything the river cruise sometimes lacked: free time, fitness centers, beautiful hotels, and the feeling that the pace was ours to explore. Let me tell you how our post-extension to Switzerland and Italy went.

read more
Viking Rhine River Cruise: The Good and The Bad

Viking Rhine River Cruise: The Good and The Bad

We went on a Viking River Cruise down the Rhine River this July. The trip was wonderful in many ways, but it was not quite what I expected in a few important ones. The Rhine River was low so we ended up switching boats partway through the cruise. This is my account of both the day-by-day itinerary, what we actually did, and my verdict on whether a Viking River Cruise was right for us (and whether it may be right for you).

read more