Slow Productivity: The Lost Art of Accomplishment Without Burnout

Synopsis

       Cal Newport puts forward his ideology of slow productivity to help knowledge workers escape the frantic busyness of the modern workplace and embrace a more effective, slower method.

Slow Productivity: A philosophy for organizing knowledge work efforts in a sustainable and meaningful manner based on the following three principles
Do Fewer Things: Strive to reduce your obligations to the point where you can easily imagine accomplishing them with time to spare. Leverage this reduced load to more fully embrace and advance the small number of projects that matter most (53)
Work at a Natural Pace: Don’t rush your most important work. Allow it instead to unfold along a sustainable timeline, with variations in intensity in settings conducive to brilliance. (116)
Obsess Over Quality: Obsess over the quality of what you produce, even if this means missing opportunities in the short term. Leverage the values of these results to gain more and more freedom in your efforts over the long term. (173)

Outline

       The first half of the book introduces the opposing ideas of Pseudo-Productivity and Slow Productivity. The second half of the book has lengthy chapters that introduce each of the three pillars of Slow Productivity, give propositions for how to implement them into your work schedule, and outlines specific strategies to help give more concrete advice.

Introduction

Part 1 | Foundations

       When human labor was primarily dedicated to agriculture, productivity was measured in the amount of goods that a field could produce. Given conditions x, field y yielded z crops. Any change to x or y that increased z would mean an increase in productivity.

       In the industrial age, human labor could be measured in the amount of goods produced. A factory worker who turned more widgets than another or who was organized in a more efficient manner was more productive.

       In the current age, with the growth of “knowledge work” where the output comes primarily from an act of cognition, there is no good metric to measure the productivity of knowledge workers. Take the following scenario:

       Given two researchers, A and B
       Researcher A can produce double the amount of academic research
       Researcher B’s research is three times more valuable to the academic community
       Which one is more productive? How could we keep track of which researcher is more valuable?

       This lack of a viable metric to measure productivity, Cal Newport argues, has led to the rise of Pseudo-Productivity, a method of measuring productivity through outward signs of busyness. If someone responds to emails within 10 minutes, has their day booked with meetings, and has an always open Slack tab on their second monitor they must be a productive member of the company, right?

       In opposition to this, Cal Newport puts forward Slow Productivity to help knowledge workers break free from the demands of Pseudo-Productivity and produce quality, meaningful work.

Part 2 | Principles

Do Fewer Things

       Not to be confused with “accomplish fewer things” (60) This pillar seeks to limit the number of projects in a given period of time in order to spend longer, higher quality time on accomplishing those projects.

       Given 10 projects [a, b, c,... j], each requiring 8 hours to complete
       Scenario 1
       Spend 1 hour per day on 8 of the projects for one week
       At the end of the week (assuming an 8 hour work day) 8 projects will be 62.5% complete 3 will be 0% complete
       Scenario 2
       Spend 8 hours per day on 1 project
       At the end of the week 5 projects will be completed and 5 remain at 0%
       These scenarios is vastly simplified to show two points.
  1. The same amount of hours of labor is done
  2. In scenario two, although fewer projects have been started half of the projects are finished whereas nothing was finished in scenario 1

       Further, Cal Newport posits that switching from one project to another will decrease the overall productivity because you are shifting from one context to another and cannot accomplish as high-quality work. Conversely, if you are working on one project and that is your sole focus you will get more of that project done relative to the person who is continuously distracted by other contexts pushing their way into the brain.

Proposition: Limit the Big

       The goal is to “implement a systemic plan for limiting significant commitments in your professional life” (60). There are three main areas that require limits to be placed on them: missions, projects, & daily goals.

       Missions are overarching goals that direct your career. In limiting missions the less the better, two to three is minimal and manageable. Cal Newport uses the example of his own career just after graduation he had, “two missions: academic research and writing” (69.) Five or more seems unmanageable.

       Projects are tasks that require more than one sitting to finish. In order to limit projects you must be realistic and specific with your rime. Schedule protected time to work on projects like you would a meeting. If somebody attempts to pawn another project onto you, respond respectfully with the amount of time it will take before the project can be started, your current workload, etc. As long as you make this a regular practice and are known as a steady and faithful worker (hopefully) people will reconsider overworking you.

       In order to accomplish the most amount of high-quality work on a project, it is recommended that you work on at most one project per day. Not that this is the only thing you will do in a day, everyone has smaller tasks that can be accomplished in one sitting, but that this is the only project that you will work on for the day.

Proposition: Contain the Small

       Schedule regular time to finish recurring tasks. If you have to review a budget report every month, block off the required time it would take every month instead of waiting until the last minute.

       When dealing with a team, instead of firing off a quick email, or scheduling a meeting, institute office hours. Office hours are regular 30-60 minute time periods where you are totally available to any and all requests. It is also incumbent upon you to broadcast this message to people. If one of your co-workers sends an ambiguous email, instead of engaging in a lengthy asynchronous back-and-forth, just offer that they stop by your next open office hours so you can discuss it quickly in person.

       This advice can also be followed for teams in “docket-clearing meetings” which are weekly meetings where your team runs through tasks that require clarification or collaboration.

       Spread the workload. If someone has a request of you it can be useful to a minimal amount of effort from them for you to be successful. The example used was an office manager who processed travel reimbursements. Instead of doing all of those tasks herself, she has two mail sorters, one for unsigned forms and one for signed forms. It is the team members responsibility to print the forms and fill out the requisite fields. Once a week (say, Thursday mornings) the manager signs the forms and transfers them to the signed forms pile. From there it is the teammate's duty to scan and submit the forms. This process requires minimal amounts of extra work from the team but saves a large amount of time on the office manager's account.

Proposition: Pull Instead of Push

       Task management can be viewed in one of two ways: push or pull. Ordinarily, when work is finished at one stage it is then pushed onward toward the next stage. In knowledge work, it is often the case that more work is pushed onto a worker than can feasibly be completed in an expected amount of time. Instead of having work pushed onto a worker, a pull based system is exactly the opposite. When a worker has finished a project, he will pull in a new project to work on. Unless your organization is reformed to accept a pull-based system, you will not be able to do this as an individual, but Cal Newport has a three-part system to simulate the pull.

  1. Create two lists
    1. Holding Tank: list of unbounded size that holds all projects to be completed
    2. Active List: list of at most three projects that are currently being worked on
  2. When accepting a new project send an acknowledgement that you will complete the project, then
    1. Request additional details before the project begins
    2. Count existing number of projects
    3. Estimate when you expect to finish the project
  3. Once a week clean out your list
    1. Pull in new work
    2. Update any deadlines
    3. Send updates to stakeholders about any delay
    4. Cancel if absolutely necessary
    5. Look for projects that have been made irrelevant or redundant

Work at a Natural Pace

       Humans have spent a much longer time working seasonally than they have working year-round in air-conditioned factories or offices. We are designed to work seasonally, and we work better when we do so.

Proposition: Take Longer

       We are not well equipped to properly estimate the amount of hours it will take to accomplish a cognitive-based task. As a result, one easy way to work more naturally is to double project deadlines. You also ought to simplify your workday. Cut back on the amount of meetings and daily tasks you plan to accomplish.

Proposition: Embrace Seasonality

       It is not strange to work on a seasonal basis. Historically, working eight hours a day, every day is a strange idea. As is possible, attempt to schedule major projects such that they all wrap up around the slower seasons of work and plan to start new ones when the slow seasons end. In the interim have smaller, less cognitively demanding projects during the slow seasons. Just because it is more natural to work seasonally does not mean you are not getting paid to work year-round.

       Small seasonality is a way to shake up your work year by embracing smaller segments of your day, week, or month and slowing down. The examples Cal Newport uses are

  • Do not schedule meetings on mondays
  • Take an afternoon off once a month and go to the zoo or movies
  • Schedule restful projects that you will enjoy doing
  • Work in six to eight week cycles

Proposition: Work Poetically

       Embrace rituals as a way to get into particular mindsets to accomplish work.

Obsess Over Quality

       When it comes time to advance in your field only a few key activities matter. “When professors go up for promotion, for example, most of what occupies our day falls away from consideration. The decision comes down to exhaustive confidential letters, solicited from prominent scholars, that discuss and debate the importance and impact of our research on our field. In the end, great research papers are what matter for us. If we haven’t notably advanced our academic speciality, no amount of to-do list martyrdom can save us.” (175) It is vital that we cast off the demands of Pseudo-Productivity in order to invest our time in high-quality skills that will improve our careers.

Proposition: Improve Your Taste

       Developing a skill not in your field can increase your appreciation of the skills that are in your field. Most of the advice and strategies put forward are interesting but seem to mainly apply to those whose careers are entirely creative (artists, authors, the like) who could feasibly become a cinephile and as a result, apply the lessons they learn to further their writing career. Another strategy was to start your own version of The Inklings, a writing club that included the likes of J.R.R. Tolkien, C.S. Lewis, Owen Barfield, and Nevill Coghill. The Inklings met to read and offer advice to the authors within its group.

Interpretation

       This book is written for knowledge workers with a high level of autonomy in their workplace. The author’s concern is how to increase productivity. The modern office space has failed to create a useful metric for defining what a productive knowledge worker is. As a result, productivity has been replaced by pseudo-productivity, “The use of visible activity as the primary means of approaching actual productive effort.” (22) Instead of focusing on being productive we pride ourselves on responding to emails within 10 minutes, filling our day with meetings, keeping an open Slack tab. To combat this Cal Newport posits a break from pseudo-productivity and an embrace of his philosophy, Slow Productivity.

Application

       The difficulty in applying a book like Slow Productivity is that all applications will be worker and workplace specific. An author will have a different way to “Contain the Small” than a Software Developer or a Professor. The level of autonomy will also change individual application. If your office is more easy-going then taking an afternoon off to the zoo (148) will be easier than for others. On a personal note, I went through and came up with applications for my job for as many strategies as I could think of that are unique to my job and my office. Some were easy, my office has a built-in “shorter work year” (142). However, there were others that I did not have applications for (how am I supposed to attract an investor (209.))

Conclusion

       Every portion of this book is interspersed with examples and stories to help ground the author’s ideas in reality. For example, when introducing the proposition to switch to a pull-based method (page 100), the author begins by telling a story of how he first found out about how the Broad Institute implemented a pull-based method. This story is useful in that it shows that this method was developed by a team to solve a problem that knowledge workers often have, an overflow of projects currently under development. However, if you do not care about the story, then you are better off skipping to the implementation of the idea (beginning on page 105.)

       Personally, I do not care about the stories and feel that they get in the way of the rest of the book. Some of them are interesting (such as the one about Benjamin Franklin and his habit of journaling virtues he would like to develop), but my interest in a particular story is incidental to the information conveyed. If Cal Newport omitted the tale of Benjamin Franklin I would still have all of the information within the “Proposition: Contain the Small” (76) and I would have saved 4 pages of reading. Cal Newport says that he enjoys “collecting these stories of glamorous defenses against distraction.” (81) Unlike the author, I do not find them aspirational.

       You could interpret all of the stories as padding in a book that could be rewritten as an article. I do not find this to be a fair interpretation. I think the author genuinely enjoys collecting and sharing these stories and they can be a useful way to show the audience Slow Productivity in action.

       If you are an avid fan of Cal Newport (you read his books, listen to his Podcast, subscribe to his YouTube Channel, have signed up for his weekly Newsletter, bookmarked his website, or his other website, and read his articles in the New Yorker) then you will find little in this book that you have not already heard. Does this mean that you can happily skip this book? I would say no. It is useful to have Cal Newport’s thoughts on Slow Productivity all collected in a compact, well-edited format that can be easily referenced and engaged with. Also, there is greater value in deeply reading a book than in listening to various podcasts on the topic.