Welcome to How I Work, a show about the tactics used by the world's most successful people to get so much out of their day.
I'm your host, doctor Amantha Imba.
I'm an organizational psychologist, the founder of behavioral science consultancy Inventium, and I'm obsessed with finding ways to optimize my work day.
Today's show is a best of.
Show because I'm taking a few weeks off How I Work to recharge over summer, and so I've been going through the last two and a half years of doing How I.
Work and picking out some of my.
Favorite episodes to share. So on Today's show is one of my favorite interviews that I've done over the last couple of years, and that is with Cal Newport. Cal is a computer science professor at Georgetown University. He is the author of six books, including most recently the New York Times bestseller Digital Minimalism, Choosing a focused Life in
a Noisy World. Cal's work has been published in over twenty languages and has been featured in The New York Times, The Wall Street Journal, The New York Of, the Washington Post, and The Economist. And his book Deep Work Deeply Impacted How I Have chosen to change the way I work over the last three years.
So look, it was probably.
An understatement to say I was excited for this chat when I did it because I am a complete and utter fangirl of Cals and his work has just had such an enormous impact on how I work, and we cover a bunch of different aspects of the way Cal now approaches his.
Work in this interview.
Before I throw to Cal, just a shout out to everyone that's been leaving reviews for how I work in Apple podcasts and other places. It's so deeply appreciated. I'm so grateful for everyone that has done that. And you know, if you're enjoying how I work and maybe haven't had the time to leave a review or think that it will go unnoticed, trust me, it won't. I'm so, so so grateful and it's a great way of helping other pe will find the show. So on that note, let's
head to Cal to hear about how he works. Cal, Welcome to the show.
It's my pleasure.
I want to start.
By talking about deep work because I've heard you talk about the benefits of creating a deep work ritual, and I was wondering if you could describe what your deep work riteal currently looks like in your own life.
Well, so I differentiate between the types of deep work, which is actually an innovation that came after my original book came out. This is sort of an evolution of some of the ideas from the book because I realized there's different types of deep activities that benefit from different types of rituals. So, for example, when I'm writing, I have a ritual built around writing that's quite specific. I
actually have in my house. I had a custom library table built that was reminiscent of the tables at the university library where I used to work as an undergraduate, with sort of brass library lamps next to the dark wood bookcases. And I have a ritual for writing where I clear off that whole desk and I just have those bright lights shining right down on the custom desk.
It's just me and my computer. But that's very different, for example, than when I'm trying to solve a theoretical computer science proof, where the rituals I use almost always involve various walking routes around my town. And so I really differentiate now what the ritual is the best match the character of the cognitive effort.
That's that's fascinating. How and I love the sound.
Of this custom made library table as well.
That's really cool.
How How did you like how did your deep work routine evolve to that? In terms of getting to the insight that you need different rituals for different types of deep work.
I think what was bothering me at some point is that I realized that the rituals I had built were centered on only one type of deep work, and then when I was getting to other types, I was feeling either I wasn't really counting it as deep work, or
I was feeling frustrated. And so my memory was I really had my deep work rituals built around solving proofs because that was at the core of my job as a professor, and so a lot of what I needed to do, for example, for writing, like reading hard things or taking notes or actually sitting down and writing chapters wasn't being captured by the same rituals I would use
to solve proofs. And I was just getting really frustrated and I would say, Wow, you know, I didn't do any deep work this week, And I said, wait a second, actually I did.
No.
I just was too narrow in my definition, and so I think it was just reacting to that frustration in my own life that I realized, oh, I have to be more broad when thinking about what deep work means. Yeah.
Yeah, And how do you know if you're actually doing deep work, like if the activity that you are working on constitutes deep work? Like I've heard you have conversations I think on other podcasts where you discuss the difference between being in flow versus doing deep work, which has had Is that something you're able to elaborate on.
Well, it's an important distinction. I think the right way to think about it is under the category of different types of deep work. Some of what's under that category might induce a flow state, some of it might not, so they're not the same thing, but they're also not completely different. So the type of deep work that creates a flow state tends to be where you're applying a
well honed skill to something cognically demanding. But you really might get into a flow of you know, I'm writing and I'm in a flow, or I'm sort of making I'm thinking through a proof and I'm starting to make
progress on it. I just feel completely engaged. But another type of important deep work is when you're trying to learn something new or improve a skill, which requires a deliberate practice where you're stretching yourself paste you're comfortable because you're constraining really hardless stay to try to learn a new idea that you've never known before, to learn a new tool. That is by definition actually kind of the opposite of a flow state, when you're in a state
of deliberate practice. The Anders ericson, who really helped innovate the research and deliberate practice, is very clear that it's unpleasant. You don't lose track of time when you're trying to learn something new. You actually are quite aware of every minute because it's hard. But that's also deep work, and so it's just a broad umbrella. Some deep work you feel great, you lose track of time. Some you're white
knuckling it because it's really hard. But the fulfillment you're going to get is afterwards, when you're knowing that you did something, you did something difficult.
I wanted to ask when I read deep Work a couple of years ago, I remember being struck by the insight that I had somehow let shallow work take over my life. And I simply tried to fit in bits of deep work in amongst it. I'm sure I'm not alone in reaching that insight, and I've since completely transformed the way I work and get so much more out of my days. And I want to know for you, have you always been a naturally deep worker or was this something you had to build or create into the way you work.
I had always been a natural deep worker, in part because of the field in which I worked, and so training as a theoretical computer scientist, my world was a world in which concentration was just openly considered to be the most important skill. This is what you were judged on, this is what you were rewarded for. No one could care less about busyness. Busyness was actually probably a sign
that you weren't a very good theoretician. People had pride in the number of hours they could spend staring at a whiteboard, and so in this sort of esoteric field I was in, deep work was at the core of it,
and so I really understood it. The insight that really surprised me, however, is when I discovered that deep work is just as important in almost every other knowledge field as well, and So for me, the process of coming to write that book Deep Work Work was sparked by the process of saying, Okay, well, for me, concentration is
really important, but what's important in other fields? And keep coming up with the same answer, the sort of discovery that this thing that I thought was pretty narrow that applied to only a small number of rarefied jobs, turned out to be core to almost everything in the knowledge economy.
I'm curious about the idea that's interesting for you that you have always been a deep worker, and I would imagine that a lot of people that have read Deep Work probably we're probably stuck in a similar work routine to where I was, where the majority of my day was shallow work, even though I am a knowledge worker.
What have you seen to be the most effective.
Ways for people to break the shallow work cabit.
Well, the first step is just a vocabulary. So if you don't differentiate between what is deep work and what is shallow work, it's very very easy to just get into a world of busyness. Right. If you don't differentiate between these two activities, then the only metric you have
is am I working harder? Am I not? And this is the trap that a lot of people fell into in the last ten or fifteen year in this age of sort of very low friction communication and internet accessibility, is that it just work is work, and either you're working a lot or not. It was very easy to be very busy and think that that was good. But once you have the terminology of deep work and shallow work and realize that in most jobs, at most levels, deep work is what moves the needle right. Deep work
is what gets you promoted. Deep work is what gets you more revenue as a company. Deep work is what actually produces value in the knowledge context, and shallow work just supports them. Once you make that distinction, then suddenly you become incredibly uncomfortable if you notice that you're doing almost no deep work, because in knowledge work, the main manufacturing process is mine's concentrating to produce information with more value.
If you are not doing that, there's something probably problematic. You're not producing value. You just talked about producing value, doing logistics about producing value. You're planning about producing value.
So step one is getting the vocabulary right. Once you have the vocabulary right, people get a hunger for well, I want to do the deep work and so something as simple as just well, let me keep track of how much I'm doing can be incredibly powerful because if deep work is the main activity that actually creates new value in almost any position, at almost any level, and you see that you're doing two hours of a week, then suddenly, instead of thinking, Wow, aren't I great, I'm
really hustling, you look at this and say, what in the world is going on? This is sort of a degenerate setup I've ended up in. I'm spending almost no time actually trying to produce things that are valuable and that can give you the big spark you need to make big changes because it's not easy. It's not easy to push back against the cold the business. So you need something like that to really help break you up.
Have you found that just that inside alone is enough to spark behavior change.
Well, it sparks the hunger I've then at that point it's helpful. It's helpful to have some meals to serve to associate that hunger. And let me mention two things real quick that in the aftermath of deep work coming out, readers have reported to be very important for you know, are at least very useful in practice for satiating a new hunger for deep work. One is scheduling deep work in advance on your calendar, treating it and protecting it
like any other meeting or appointment. So once it's on there, that time is taken up you have to plan around it. If someone tries to schedule something during that time, you say, already have a thing. People are used to the social conventions, run meetings, and appointments. If someone tries to get in touch with you during one of these blocks and they're upset because hey, why don't you get back to me, you can say, well, I had a thing from twelve
to two, like you really do. Treat it like you're going to the dentist or in a meeting right where you can't be reached. That's really helpful. So then in advance people can start putting this time and locking it in and then forcing themselves to work around the anchor time to try to fit in the other shallow work.
That's useful. The other thing that's useful I've been hearing from readers is having a conversation with your supervisor, or if you work for yourself, sort of have this conversation with yourself where you say this is what deep work is. This is what shallow work is. Both are important for the organization. What's the ratio I should be shooting for in a typical forty hour work week? How many of
those hours should be deep work for shallow work? And the answer will be different for different jobs, right, But you get an answer, and then you work backwards and say, Okay, what changes might we have to make so that we can accomplish this goal that we decided together was going
to optimize the value I produce for the company. So it's a way of approaching deep work with the people you work with that is positive, saying how can we use this idea and agree on how to do it together to make more value, as opposed to what most people do, which is negative, which is stop bothering me, I don't want to answer an email. Stop scheduling me in meetings, right, which just tends to make people defensive.
So those two things scheduling deep work like meetings and appointments, and two agreeing on a deep to shallow work ratio are things I've been hearing from readers to be really effective for getting more of this into your life.
That's great. I love that question. To ask your boss.
And I must say I personally have had great success with just blocking out deep work in the diary. Generally, almost every morning in my diary just has a do not book sign over it, which I've personally found very effective and funnily enough, the thing that I found hardest to apply from deep work was you write a bit about having a ritual to end your day and shut down your work day, and I've never been able to
make that stick. But I'm wondering if you could describe how your workday ends, because I've found that quite fascinating and I'm not sure if it's changed since writing the book.
No, it's more or less still the same. So the idea of a work shutdown ritual is that when you're done with work, you want to go through the potential open loops, right, So make sure that anything that is on your mind but not actually in a system where it's going to be dealt with and scheduled, gets into a system where it's going to be dealt with scheduled.
Get everything out of your mind. I used to, depending on what's going on in the week, I'll often at this point check my calendar, check my task, check my plan. Make sure that Okay, I'm on track. I've got a plan for the week. I know what I'm doing. I'm on track to get things done. I'm not missing anything. So that there's no open loops, no concern. Make your last look at the inbox. There's nothing lurking there that's an emergency, right, and then you shut it down. So
you and I recommend having at first a phrase. You say whatever you want it to be. The idea being that once you've done the shutdown and you've said whatever the phrase is, if later in the evening your mind starts to bother you right and say, you know, like maybe we're missing something. Maybe we should go back and think some more about this, you can say, you know what I said the phrase. I wouldn't have said the phrase if I hadn't checked on everything and made sure
that I trusted our plan. So there must be a plan. I trust. I don't have to think about it anymore. And what people experience is when they do this shutdown routine, and that kind of pushback on the ruminations. After a couple of weeks that urge to ruminate and think about work after work is over starts to really diminish which allow to have a much more sort of present and relaxed evening.
It's so true, It's so true. It's funny.
In my own life, I just I can't seem to crack that. I always am struggling to resist the temptation to hop back onto my computer after my daughter's in bed. And I wanted to ask, like, did becoming a parent, which obviously happened for you quite a few years ago, did that change the way that you approach your work in particularly deep work habits.
Well, in some sense, my deep work habits made it easier to make the transition to being a parent because the way I used to work, you know, I trained myself that I have work hours, and I want to get the most of those work hours, and I'm going to structure the day. It's going to be intense, depth, really organized, shallow, have a shutdown when it comes time to be the shutdown period. For whatever reason that that was really appealing to me. I used to plan as
a grad student. I'd planned my day around my wife's work schedule, so I was like, I want to use every minute that she's at work to get as much done. But then I don't want to be one of the grad students who sort of was lazy during the day and then has to be on campus all night. I want to be home with her and doing other sort of things. So I have this tight schedule. When I'm working, work really hard. When I'm done, be done. So then once we had kids, that kind of worked really well.
So I was like, Okay, when I'm at the office, I'll work really hard. But then I was already used to the idea that when I'm done, I can shut down completely. And now shutting down completely wasn't just well, it's just kind of relaxing when I'm home doing what I want to do. Of course, now it's kind of, you know, it keeps things off my mind when I'm home running around doing childcare. But it fits really well.
And so this notion if I want to work deeply, really intensely, keep the shallow work incredibly organized and contained, and when I'm done, when I'm done, incredibly compatible with being a parent.
It all sounds very logical. Work when you work and don't work when you're not at work. Something I want to shift on to, which you write about in digital minimalism, is the value of solitude and bottom, I guess which
you know? Again, like when I was reflecting, when I was reading the book and reflecting on my own life, it's quite scary to think about how infrequently I was feeling bored and how infrequently I would imagine a lot of people experience boredom because there's just constant inputs, and I'm.
Curious to know how.
And you write a bit about this in the book. How do you experience solitude and boredom? How do you create those states in your own world?
Well, so, just to provide a little bit of background, some context on the shift from Deep Work to digital minimalism before getting to the specific question. Basically, Deep Work was this book that was about focus in the workplace and how technologies had unintentionally made that more difficult. And so one of the big reactions I got the Deep Work was, Okay, maybe this is true, Like what you're saying about tech and what it's doing in the workplace, Well,
what about tech in our life outside of work? Because people in the last couple of years particular, were really beginning to feel that their life outside of work was being taken over by screens in a way that was making them uneasy. Right, And it wasn't that, Okay, I hate what I'm doing when I look at the screen. It was the fact that they were looking at the
screen so much. It was almost like they were losing their autonomy, that their whole life was getting eaten up by just glance after glance after glance at the screens was making them anxious, making them unhappy. I was keeping away from friends and family, and so digital minimalism was about, Okay, what's going on with this unease in our personal relationship with tech, so outside of work, outside of things like email and slack, and what can we do about it?
And so getting back to your question. So that's one of the ideas I talked about in digital minimalism is that when you kill every moment that you could potentially be alone with your thoughts by looking at a screen. So every time you're in line, every time you're waiting for the subway, when you know someone gets up at dinner and goes to your bathroom and you're waiting for
them to come back. If at every single moment like that you look at a screen, what you do is you put yourself into a state calls solitude deprivation, where you're never alone with your own thoughts. And we know that this is actually really unhealthy and it's probably going to make you anxious. It's also probably going to retard your ability to have sort of self development or professional
insights or breakthroughs. We really do need regular time spent alone with our thoughts, which is why I recommend that you get that in your life. And so what's the easiest way to do that is my suggestion is most days, do at least one or two things without your phone. And that simple thing I go on one errand and I do whatever one thing around the house each day
where there's no earbuds and no phone. Something as simple as that can have a major impact on your cognitive health, anxiety levels, and happiness.
What does that look like in your life in terms of incorporating, you know, moments of solitude and space to be bored.
Well, I reject this idea, which is actually quite recent, that you need to have a phone with you all the time. You know, this notion that the phone's always there, you're always looking at it. We're used to it, but it's quite arbitrary, it's quite contrived, and it's quite recent, And so I spend large parts of my day without
a phone handy, so I do locks exercise. When I'm at home, I typically my phone will be in my bag somewhere, So I don't accept this premise that I'm like in an emergency room doctor that needs to be accessible at all times on a communication device. And so once you change your mindset to one where it's I use my phone to do various things, but it's not something I always have with me, you just naturally get
lots of solitude. So throughout my day there's just lots of times with just me alone with my thoughts because I don't have easy distraction nearby. And so something as simple as that, I think if the phone as a tool you occasionally use, not a constant companion, can really make a big difference in terms of getting more solitude.
It's such an interesting idea leaving your phone at home or in the glove books. And I must say, like during the month of match my husband and I, but it's right digital minimalism before the month started, and we use that month as digital declutter month, And something that
we both consume a lot of is podcasts. And I really became aware of this habit where in any moment where I could have been experiencing solitude, Like I generally spend the hours of six to seven am either walking or at the gym or exercising or moving in some way. Podcasts and my AirPods would be glued in my ears. But one of the changes I made in the last month is actually going, well, what if I just spent that hour in silence and it just made things completely different.
I found that some of my best ideas were coming to me at that point where I was previously just consuming stimulus.
How do you delineate.
Between these moments where there's no input going in other than your own thoughts versus feeling like it's okay to have some stimulus going in, Like I'm not sure if you're a podcast list or I know that you're a big reader, But how do you kind of delineate that time?
Yes, I mean it's a good question, because I do like podcasts. I am a big reader. I try to get rid of the idea that it's a default activity. It's something I guess I think of as I look forward to our schedule, right, So instead of being a default activity, I guess I'm more active about putting aside when am I going to get input? What input is it going to be? So if I know, for example, I have a lot of yard work to do, you know, maybe I'll say, great, I'm going to listen to this
particular podcast and it's gonna be good. On the other hand, I say, oh, I have a walk coming up, and say, you know, I'm walking my kid to school and I'm going to walk home alone. I usually won't listen to a podcast. Then I've just become used to. I really like that solitude. And so it's not that there's a hard and fast rule, but I plan when I'm going to do stimuli, and you know, I have to think about it right and say do I want to listen
to something or not? Do I want the silence or is there something I think this might be a good chance to listen to something. Same thing with my commutes when I come to campus. Probably about half the time I think, the other half the time I listen. And you know, I don't have a precise heuristic that says this is when I do this and this is when I do the other. But I just keep in mind that both are possibilities and that it's worth thinking about in any given moment, which one I want to do.
Yeah, that's nice being delivered about it.
I feel like for so many people it's just a habit to put in earphones and just start listening when there's no other stimulus that could be coming their way.
And on the topic of habits, I think this was a blog maybe that you wrote a few months ago around habits versus workflows, which I found really interesting because I think in the productivity space there's such an emphasis on different hacks and quick fixes, whereas you write about the importance of actually reviewing your workflow, and I was wondering if you could like expand a bit on what you meant by that concept and maybe gives some examples
of what are the different workflows that you have in your own working life.
I think this is a key distinction and to understand some of the issues we have in workplace productivity and how we might eventually solve them. So to me, a habit is something you put in place for how you
interact with your work. So maybe when you check your email, or your methods you use for organizing your email, or maybe your personal planning like how you plan out your day or keep track of what you need to get done, whereas workflow is the underlying either explicit or implicit system that specifies how work gets done, so how obligations are assigned, executed and tracked. A lot of times we think about habits, but it's actually the underlying workflow that's causing the problem.
So the key place, I think, the key example where this distinction comes up is when it comes to email overload. So to me, the big problem with email is this underlying workflow that says the way that we work in our organization is that we maintain this sort of ad hoc, ongoing unstructure conversation using email inboxes, and it's very flexible, it's very convenient if we all just kind of keep hey, you get that what's going on over here, and that
this is how we're going to work. Is how we're going to pass tasks off to each other, how we're going to follow up on things. It's how we're going to communicate with people. It's just we're going to have this ongoing, unstructured conversation. Now, you can have a lot of habits on top of that workflow to try to tainment,
So maybe you don't check email all the time. And maybe you have some nice folder system for organizing emails moving to a to do list, But until you change that underlying workflow, there's nothing just going to solve the need in such an environment to check email a lot, spend a lot of time doing email. And so, like when I'm out there talking about the problem of email overload,
people really want to just focus on the habits. They think, well, we could just change some norms about how often we check email, or you know, batch it, or let people know that we're not going to respond right away, that we can we can solve all the problems we're having. But often the underline issue is that there's this workflow that depends on ongoing email communication you get anything done, and so if you want really systemic change, you have
to replace that with something better. And so I think organizations have to think about this, and I think individuals can think about this in their own life as well. To what extent are you rearranging the deck chairs on the sinking Titanic when you're building more complicated systems for an underlying workflow that's just inevitably going to keep you overwhelmed or not doing what's important And so I like
that distinction. There's the underlying decisions about how tasks and obligations are identified as sign tracked, and executed, and then there's what you do on top of that to help sort of interact with those workflows. And those are two different things.
And what are some workflows that are true for your own working life.
Yeah, it's an interesting question because often when I'm talking about workflows and habits, it's relevant primarily at the level of organizations, right, And so this is the difference between two software development teams, one that just people are on slack all day and the other where they use an agile methodology like scrum. It's really explicit about here's who's working on what. We put it on this board, we can see its status. We have synchronous meetings. We do
them twice a day. This is how you know, we assign things. They have a really structured workflow. Because of that structured workflow, they don't need to be on slack all day. But without that structured workflow, they need to be on slack because how else are tasked going to get passed around or things checked on? In terms of like in your individual life, I mean, one way to think about it, I suppose is in terms of processes or systems that you use for identifying tasks and making
sure they get done or assigning them. And so sometimes these can be pretty subtle, but a concrete example is like on my book tour which I'm on now for digital minimalism, there's a lot of bookings that have to happen, and so I thought about the underlying workflow of well, what's the what's the right way to actually sort of get things identified and scheduled and information to me? And we built a system with the publicity team where I could identify time when I'm available. They then had access
to those parts of my calendar. They could then book things directly on the calendar with all the information I need I could if I book something else, that time would get blocked off. And we rebuilt the workflow that minimized back and forth communication required to accomplish the goal of getting the proper things like this interview scheduled, for example.
And so that might be an example of working on the underlying workflow as opposed to just the upper level habits of like how often do I check my emails about when things are being scheduled?
And do you have I guess on top of your workflows, what are some of the most useful habits or productivity systems or weekly rituals that you do to keep your weak organized and flowing.
Well.
Well, I'm a big believer in both weekly and daily planning. I think you need to spend time to understand the contours of your week. What's happening on each day, what day is really crowded, what days have open space, so that you can start moving things around at that scale and recognize, hey, Monday is pretty open, that's probably gonna be a good time to make a lot of progress on this hard thing, even though that hard thing's not
due till Friday. But you're seeing on the calendar that Wednesday and Thursday have a lot of meetings, right, And so looking at the whole week and trying to plan out what's going to happen when I think that's important. Believer in time blocking on a particular day. Give your time a job. Here's the hours I have available. What am I doing with this hour? What am I doing with this thirty minutes? What am I doing with this
three hour block? Give your time a job, as opposed to just approaching your day with a generic to do list, You're much more effective at getting things out of your day if again, you look at the free hours of the day and reconfigure them, move them around, and figure out how can I get the most out of this? And then I often am a believer in ad hoc systems and rituals that match what's going on at the time. And so if you have, let's say, a big event coming up, do you have to do a lot of
planning for you might just say here's I'm doing. It's thirty minutes after launch every single day, thirty minutes every single day just checking in, moving things, seeing what's going on or whatever. Right, But this idea of having temporary systems that you put into place to help you make a lot of progress on important, non permanent things in a way that doesn't have you just completely an ad
hoc looking at a tasklic type mode. So if you do weekly planning, daily time blocking, build temporary systems and rituals as needed for temporary but large obligations, that usually combines to help you get a pretty effective use of the time available.
And can I ask with time blocking because it's something I've experimented with myself, and I feel like the cognitive biases that either cause you to overestimate or underestimate how long something takes, I've found can be my downfall with time blocking. Where let's just say I've completely overestimated how long something will take, but I've set aside three hours. I finished it in an hour and a half, and then like, what, like, how does that work.
In your world?
Right?
Well, I mean, I should say at the bigger point is that one of the nice things about time blocking is that it's practiced to make you better at estimating how long things take because there is some pain to when you get it wrong. It requires some extra effort, and so you have to try to get it right, and you get a lot of feedback. So you see, consistently not giving myself enough time for this type of activity, you get that feedback or I'm always giving myself too
much time, So that gets better. But then what do you do in the moment? Well, if you don't give yourself enough time, then you know if you keep going till you finish what needs to get done, and then you just adjust your schedule for the rest of the day, which is fine. And one of the ways that people get time blocking wrong is they think that it's a game where you win the gold medal if you never
have to change your schedule. But there's actually no prize you get for getting your schedule exactly right and never having to change it. You probably might have to change it three, four or five times. The goal is not to have a perfect schedule. It's to always have some intention about what you're doing with the time that remains of the day. Same thing if you underschedule, so you
have a couple options here. You could add something new, or you could take advantage of that time just to relax, or to do something that's going to dogative rest like
that's actually kind of a nice scenario. But the point I always make about time blocking is that, regardless of what you do, having a good understanding of how long things take is crucial because if you don't, regardless you're time blocking or not, you're just going to keep getting yourself in the trouble and you're going to keep having colliding deadlines, You're going to keep having late nights, you're going to keep having these sort of stressful moments when
you realize, ah, a lot still needs to get done and I'm not there, And time blocking trains you to better appreciate how long things take and then otherwise just be comfortable with the fact that you might have to change your schedule several times throughout the day and that that's not negative, that's actually how the system works.
Yeah, I like the idea of actually taking a break. And I've heard you talk about the concept of deep breaks, because I feel like people don't really think that much about what constitutes a break, what they do in a break, how long a break goes for. So can you describe this concept of deep breaks and what they involve.
So, if you're doing a deep work and you're taking a break and you're going to return the deep work, you should be careful about the break. And so you want to avoid, for example, in a break, exposing yourself to other but similar type of work, because now you're going to contact shift and so you want to be really careful. If you're writing an article, you don't want to during a break maybe read or think about a
related article. It's just too close and now you're kind of context shifting to that other article and it's going to be hard to come back. You also want to avoid open loops, exposing yourself the loops that you can't close during the break. And so this is what's dangerous about looking at email. For example, in a fifteen minute break, you're going to see a lot of things that you can't get to, a lot of emails you can't quite answer. Open loops really eat at our attention and reduce our
cognitive capacity going forward. So a deep break, you want to void looking at similar type of work or open loops. And so you can look at stuff, for example, that's completely unrelated to work. You know, you can read an article about your local sports team is probably not gonna be a big deal. You can go for a walk, you can read a book, a chapter from a book, or a magazine article that's completely unrelated to your work. These type of things are fine. You can talk to
people you know, non work related conversations. All that's fine. Those would be deep breaks, But you don't want to do something similar. You don't want to expose yourself to open loops.
I find that really helpful because I feel like email is the thing that often fills spare time because it can take as long or as little as you want. And how what does email look like in your life, like how how frequently do you check it?
How long do you spend in there?
What would like your I guess your email system look like in a typical way.
Well, there's two elements to it. So one is controlling what comes in. And so if you look at, for example, my author website and you go to the contact page, I don't give people a general purpose email address. I don't just say hey, i'd love to hear from you. Here's my email address. Instead, there's very specific addresses for very particular purposes, and then I give expectations around them, like okay, if you're interested in speaking, well, you can
you can talk to my speaking age. And thus the address publicity, here's like a publicist you can talk to. If you want to send me links or articles which I really like, you can send them to this address. But I don't answer. A look at it, but I don't answer, and I don't give an option, for example, for and if you just have like questions for me, or want to talk to me or ask me to get involved in a business or whatever, there's just no
option for that. Now you would worry that that might make readers upset because you're sort of cutting off accessibility, but I found that didn't happen. People are okay with clarity. They don't really need accessibility as long as it's clear.
So if they know for a fact, like, okay, there's no way for me to really reach you about this, and they're okay with it, that's better than them just having a generic email address and sending their business pitch to you with some expect that you might answer, and then being upset that you don't. And so I try to cut down on what comes in or expectations on reply.
And then in terms of dealing with the email that I do get, you know, I schedule when I look at it, and how often that is just depends on what's going on, and so it's not maybe I go a day or so without having to without being able to look at it, and over time people get mad at me a lot. But people have learned that I don't use email like an ongoing, constant communication or chat service.
It's just not something you can use to grab my attention real quickly, even if it's really convenient for you. That's just not the way I use email. It might be a day or two till I see it, and so I always tell my students that when we begin class, my colleagues have learned it, my family has sort of learned about it, and people adjust. And so for me, some days I don't look at it, other days I do, and when I do, I try to take care of it in basically one session.
I do like the idea of just being clear and setting expectations, and ironically that will lead to less disappointment.
I want to come back.
To emails toward the end of about chat in a few minutes, but first I did want to ask you something that my company, Inventium is working on at the moment with the University of New South Wales, is actually looking at strategies like introducing deep work into an organization along with other different strategies for working better and trying
to assess the impact on productivity and other variables. And so I guess a couple of questions there, because I've heard you talk about it's actually quite hard to land on a definition of productivity, like if an organization introduces a workflow that is more around prioritizing deep work when we're talking about knowledge workers over shallow work, like how do we actually measure the impact of that on productivity, and then what are the other variables that we would
expect it to change, like you know, ranging from job satisfaction to health and well being and stress levels. But I guess, in the context of this study, how would you be measuring productivity when it comes to the impact that deep work would have.
So I would go back to the economic metric of productivity actual value produced per hour that you're paying salary, which I sometimes call true productivity in the book because what we've done in knowledge work because knowledge work is a little bit more ambiguous we don't have widgets to count coming off of an assembly line, is that we began to use busyness as a proxy for productivity. So are you there early in the morning, are you around
a lot? Are you answering emails very quickly? Just in general, if you're doing something, at least we know you're not being lazy or taking advantage. And that's the sort of metric we put into place. But what really matters is is the activity producing concrete value for the organization, such as dollars coming in in a for profit organization. And it's there that I think that we're finding that we
should be a little bit concerned. Like if you look at the US, for example, our labor department tracks this productivity right, revenue per sort of employment hour, and they break it out for the non industrial sector, so particularly for they call it non industrial productivity metrics, so not counting manufacturing, but mainly just knowledge work. That metric has been stagnant for a long time. I mean throughout this last decade period where we invested billions to make communication
as fast and flexible and easy as possible. It's never been easier for you to get information or to contact someone and get a quick response ever before in the history of work. It doesn't show up at all in the economic metrics, and I think that's something they should have us really worried, right, And I think in large part of it is because it turns out that all this communication information gathering has an impact on our brains functioning. It makes it hard for the brain to do the
actual job of thinking and producing value. And so if I was measuring productivity, you know, from a study perspective, I want to know about how much dollars are we paying in salary, what are we getting back in terms of revenue coming in, Like sort of these these baseline numbers.
And just as an aside, there's this really interesting study from the nine We're an economist from Georgia Tech was watching personal computers enter the desk like the workforce, like the front office workforce in fortune five hundred companies in the US. Right, So what happened when you got these productivity enhancing computers on everyone's desk? And he measured the numbers very carefully in the way I'm talking about. His
name was Peter G. Sassone, and what he found. I think this is really interesting is that the organization said, hey, look, this is great. These computers make certain things that we used to have dedicated support staff do, like typing and sending letters or whatever. Right, it makes some of these things easy enough that we no longer have to hire
dedicated people just to do these administrative tasks. Is the higher level they called the managers in this study, but sort of the higher trained employees can now do it themselves. And so we're going to save all this money by firing all the typists, and we don't need everyone to have secretaries anymore because you can send emails and do word processing. What ended up happening, however, is that that
he calls us the diminishment of intellectual specialization. Now you take the people who were actually producing the things to brought value into the organizations, and all this administrative work fell onto their plate. It then took more of those people to produce the same amount of work, but their salaries are much higher than the support staff that they fired.
And what with sasone crunched all the numbers, he figured out that you were actually about twenty percent less effective in the sense that you could cut your payroll by twenty percent to produce the same amount of work by bringing back support staff and allowing people just to focus at the higher level on just their work, and you wouldn't need as many of these expensive high level employees.
That's the type of study I think we need to have in mind who are thinking about productivity when you get to the dollars and cents bottom line, I think a lot of what we're doing with this constant communication, hyper convenient business is having a huge economic impact. So that's a long answer to a short question, but it's something that I feel really strongly about, and I'm glad that the University of South Wales is thinking about some studies along these lines.
That is absolutely fascinating what you described.
I'm also curious, like, what are the variables outside of productivity would you expect, like actually dedicating more time to deep work to have Like, for example, in my own life, I just get so much more fulfillment from my work because I'm creating more meaningful output into the world. So I'm curious what other variables you would expect a deep work routine to impact.
Well. You should expect more psychological satisfaction and more satisfaction with work, especially if you pair increased focus on deep work with decreased communication responsibilities. So it's true that deep work itself is very fulfilling. We like the focus on one thing and produce something valuable that's very fulfilling, and so that makes us happier. The flip side of that
is also really negative. So if you're constantly trying to deal with tons of communication, each of which is someone who needs something from you, and you can't keep up with it because you have hundreds of messages and it's always piling up and you're always behind. That collides with the sort of ancient paleolithic social wiring in our brain in a very unnatural way. That makes us very unhappy
and very stressed and very anxious. It's really just in the way that eating junk food hits our paleolithic you know, food processing system in a bad way. It makes us
really overweight. Our body isn't meant for it. Our paleolithic social brain is not meant for an inbox that's always failing and we can't keep up with because it doesn't know the difference between that email is not that important and what it was evolved for, which is, if someone around the tribal fire is trying to get your attention, you better listen to them because there's a lot at stake if you snub them, right, I mean, social dynamics
is something we're incredibly cue to, and things like email completely mess around with these finely tuned social dynamics, which is why we just feel compulsively like we have to check it. We feel if a text message comes in and we're driving, we still check it, even though I put in our kids' lives in danger, because to us, it's the same as like if someone's tapping your shoulder at the tribal fire and you ignore them, like you might get a spear in the back, right like, we
take that really, really seriously. And so the more time you spend trying to keep up with never ending communication, the more unhappy you get. The more time you spend focusing deeply to try to produce valuable things, the happier we get. So if you can increase the ladder and decrease the former, people are going to have a much more healthy relationship with their work. Your employees are going to be much more protected against burnout, and the positions are going to be much more sustainable.
Yeah, that's great, And look in the kind of just about out of time, but just in maybe one or two minutes, I would just love to I guess you know, that's a nice segue into the topic of your next book, which I believe is about email free organizations.
Is that correct?
Yeah, the new book, which should say very much in the early stages, but as of now it's vely titled A World Without Email. It gets into a lot of these ideas. I mean, I basically argue that we don't have a good theory right now about how to get a lot of value sustainably out of human brains, and the way we're working is a really terrible way to work. And we've told ourselves this story that there's no other way to work in a modern world than to just
send messages all the time. I can make the case so that's actually quite arbitrary, and that there's this growing movement of organizations who are much more careful about thinking. We have these brains, we want these brains to produce value. We don't want these brains to burn out. We're getting incredibly innovative in answering the question of what's the right way to work in a digital world.
I cannot wait to read that.
And my final final question, if people want to consume more of your work, you're thinking, you're writing cal what's the best way for people to do that?
So, from a book perspective, if you're interested in sort of technology and work and the problems, Deep Work is a good book. If you're interested in the impact of technology in your personal life, you're looking at your phone too much, you feel uneasy, feel like a loss of autonomy. Digital minimalism is good for you. Online. I don't use social media. I'm not easy to reach, but I do have a blog at calneport dot com that I've been
blogging at for over a decade. And so that's a pretty quick way to sort of dive in and see in more detail some of my ideas.
Awesome, Cal, it has been an absolute joy talking to you.
Thank you so much for your time.
Oh it's my pleasure. Thank you.
That is it for today's show.
If you enjoyed this chat with Cal and know someone else that you think would also find it interesting or useful, why not share the episode with them. All you need to do is click on the little icon that's like a little box with an arrow pointing out of it. That is what the share icon looks like mostly, and to share it with them, and hopefully whoever you share it, we will enjoy it too. So that is good for today's show, and I will see you next time.