The Jordan Harbinger Show - 503: Cal Newport | Reimagining Work in a World without Email
Episode Date: May 4, 2021Cal Newport researches cutting-edge technology and writes about the impact of these innovations on society. He is the New York Times bestselling author of Deep Work, So Good They Can’t Ign...ore You, Digital Minimalism, and his latest, A World without Email: Reimagining Work in an Age of Communication Overload. What We Discuss with Cal Newport: What is the hyperactive hive mind, and how did the collaborative nature of email communication give rise to it? Why checking our email an average of every six minutes is, as Cal puts it, "a terrible way to extract value from human neurons." How so-called multitasking takes its toll not only on our individual capacity to focus, but on the prosperity of society as a whole. Why debuzzing the hyperactive hive mind can't be done from the inbox, but by replacing the rules for how we collaborate. How we can set the rules, guidelines, and systems by which we agree to communicate without succumbing to the collective pull of the hyperactive hive mind. And much more... Full show notes and resources can be found here: jordanharbinger.com/503 Sign up for Six-Minute Networking -- our free networking and relationship development mini course -- at jordanharbinger.com/course! Like this show? Please leave us a review here -- even one sentence helps! Consider including your Twitter handle so we can thank you personally!See Privacy Policy at https://art19.com/privacy and California Privacy Notice at https://art19.com/privacy#do-not-sell-my-info.
Transcript
Discussion (0)
Coming up next on the Jordan Harbinger Show.
This ancient social mind, it just doesn't want to be missing communication.
It doesn't care about the context.
There's someone in my tribe right now tapping me on the shoulder.
I'm ignoring them.
When there's a famine, they're not going to share their food, and I'm going to die, right?
That part of the brain is powerful.
And those type of instincts don't go away easily.
Welcome to the show.
I'm Jordan Harbinger.
On the Jordan Harbinger show, we decode the stories, secrets, and skills of the world's most fascinating people.
We have in-depth conversations with people at the top of their game.
Spies and psychologists, astronauts and entrepreneurs, even the occasional arms dealer,
mafia, enforcer, or neuroscientist.
Each episode turns our guest's wisdom into practical advice you can use to build a deeper
understanding of how the world works and become a better critical thinker.
If you're new to the show or you're looking for a handy way to tell your friends about it,
we assemble these episode starter packs.
You can go to Jordan Harbinger.com slash start.
It's all organized by popular topic.
You can get a taste of everything we do here on the show.
Whoever you're referring can get a taste of everything we do here on the show.
I love it when you help other people find us,
and that is the easiest way to get a little sampler platter.
Back by popular demand today, Cal Newport,
author of many amazing books, including So Good They Can't Ignore You,
Digital Minimalism and Deep Work,
all of which kind of rock the world of productivity and focus and all that,
if there is a world of productivity.
Cal's books are the kind of books that I see CEOs and founders
passing around to their key team members and each other.
I've known Cal for a really long time.
The guy is super switched on.
I'm not sure anyone spends more time thinking about
and studying productivity and focus than Cal Newport does.
Today, a world without email.
Maybe not entirely without.
I'm not sure we could survive there.
But the future of human work is cognitive.
I don't think anyone is going to argue that.
We need to maximize that as opposed to the hyperactive hive mind,
as he calls it, that mindless email productivity.
We don't want more things.
faster. We want focus on more important things, and that is what Cal and I are going to discuss today.
So if you're looking to become more focused and productive at work, so you can do the important
stuff, then this episode is for you. And if you're wondering how I managed to book all these
superstars on the show, these authors, thinkers, and creators, it's because of my network.
I'm teaching you how to build your network for business, personal, career, otherwise over at
Jordan Harbinger.com slash course. The course is free. Dig the well before you get thirsty.
most of the guests here on the show, they subscribe to the course and support the course.
So come join us. You'll be in smart company where you belong. Now, here's Cal Newport.
I love the idea of a world without email. I don't hate email though, you know, and I think that's
kind of where a lot of people are going to take, is it Umbrage with the book and possibly the titles
are going to go, hey, look, I don't feel like emails suffocating me or crushing me. Why do we need a world
without email? And I know that's an involved question, but let's start there. Because frankly, it sounds
a little bit like a, I'm not a Luddite, right? I get it. I can ignore my phone, but I don't have to,
like, I don't have to discard all the benefits of having email and internet. You know, I have to go back to
95. Well, that question gets to the heart of it, so it's a good place to start. We have complicated
feelings towards email, and it's worth untangling these, because otherwise we're never going to get a
solution to these complicated feelings. Here is the quick story. Email spread in the office environment
in the 1990s.
You can basically track it from around 1990 to 1995.
That's when it makes its big move.
And it spread for a really good reason, which is why we enjoy email.
It was replacing fax machines.
It was replacing voicemail.
It was replacing inner office memos.
It was unambiguously better than those existing modes of communication.
This is why we're happy that email exists because the fax machine was a pain.
And plunging in those numbers in the phone is a pain or getting those little yellow pink pads from a
secretary or, you know, who did you miss?
So it was solving a real problem.
And it solved it really well.
It was faster.
It was cheaper.
It had more features.
The issue is what followed behind email spread.
So as email spread, behind it came a new style of collaboration, which I call the hyperactive
hive mind.
Now, this style of collaboration is one in which you say, look, now that we have this
low friction digital communication tool, why don't we just work out most collaboration with
ad hoc unscheduled messages?
Just go back and forth, figure things out.
Hey, do you hear about this client?
Can we jump on a, could get into a meeting?
What's going on over here?
What should we do about this?
it's actually that hyperactive hive mind workflow, that's what's causing the problem.
That got out of control.
And by the time we get to the early 2000s, the amount of checking of inboxes you had to do
just to keep up with all this back and forth unscheduled ad hoc messaging began to really
take away from people's ability to get other work done.
So really the title of this book should have been a world without the hyperactive hive mind
workflow, but that doesn't exactly roll off the tongue.
So I'm glad we could make that distinction right up front.
Yeah, that makes sense. And the hyperactive hive mind is something you talk about a lot in the book. The phrase shows up a lot in the book. And you're right, it's not just email, right? It's, I look at my morning. Let me see what I did this morning or on any casual morning. I look at my calendar, which is a shared calendar. That's pretty useful. Keeps me in line. I'm checking my texts. I check my YouTube comment inbox to make sure there's not a bunch of spam in there. I mean, or a VA does it, right? I like to answer some fan mail. I check my Instagram DMs because there's fan stuff in there. I check my LinkedIn DMs. There's fan stuff in there. I check my Twitter.
DMs, there's fan stuff in there. I check my email. There's fan stuff in there. There's also work
stuff in there. Come downstairs, play with my kid who's finally awake, play with him for 30 minutes,
make some breakfast. Look, there's a bunch more email because everybody else who got up later
and realized that they needed to send me. So, and this is kind of a constant cycle. And then sometimes,
like right now we're recording a podcast. This is what real work is for me. Real, like the real fun,
productive part of my day is. After this, though, it's sort of like back to the inbox, back to another
spreadsheets back to making sure that other inboxes aren't full. I'm not going to have to check all
the social media stuff because I've got that systemized and it's never urgent. But there's always
kind of a pull and there's probably some calls, right? So it's, and this is, I'm my own boss in theory,
right? I work with very few other people. I live with my wife, who's my chief collaborator and
runs, kind of shields me from a lot of this. So if I'm this busy, I can't really imagine how busy
a school administrator is or a person who runs a freaking daycare or somebody who owns a drugstore.
I mean, they have to be much busier than me because they don't even control their workflow necessarily
or their time. They can't say, hey, I'm not, I'm in communicato today with my head down. They're like,
what are you talking about? You work for me. You're not doing that, right? We can quantify,
by the way. We can quantify how busy there are. There's this great data set I talked about in the book
from Rescue Time. So they have tens of thousands of people who have this software in their computer,
that monitors everything they're doing.
They hired some data scientists to say, well, let's actually crunch some numbers on
this data since we all have it in the cloud.
And what they found among their users is that they were checking inboxes once every six
minutes on average.
So that's how we quantify how busy the hyperactive hive mind makes us.
Every six minutes, as far as I'm concerned, means that you have to just effectively
speaking constantly be tending inboxes.
So it just becomes a parallel track.
Whatever else you're doing as a pharmacist or as an administrator, as a marketing executive,
it's whatever, you have to, in parallel, be constantly.
monitoring those inboxes. Our brain can't handle that. It's a terrible way to try to actually
extract value from human neurons. You mentioned this in some of your previous books as well, but the
constant task switching is terrible for focus. And I guess this is just called switching costs.
And I know that a lot of people have probably heard this, but this first came to me when I was in law
school because people had instant messenger open. And eventually I went, you know, when this is open,
I always lose the professor in class. I never can follow the lecture. There's no way this is good for me.
And then when I was studying, I'd get sucked into it. And I'd be three hours and I'd go,
how am I on page 10 of this? And that's sort of where this concept started to illustrate. But now it's
even more insidious because you go, well, I'm working. Look, it's an email inbox. It's our company
slack, it still does the same amount of damage to our focus, only now we think we're actually
working, but we're not doing anything. Well, I mean, switching cost is the most underestimated,
overlooked, crucial scientific principle affecting our ability to work today. And the fact that we're
not talking about this constantly, I think is a real crime. Now, back in my book Deep Work, I hinted at this
and said, you know, I think the switching cost thing is a big deal. There's this notion called
attention residue. Maybe that's why we don't get as much done when we are not doing deep work. Well,
for the new book. I said, well, I'd go talk to all of these researchers, right? So I went and
actually talked to the neuroscientist and the psychologist. I talked to Sophie Leroy, who wrote
the original attention residue paper. I talked to Gloria Mark, who really studied the impact
of technology, what's happening in the workplace. I talked to a really well-known neuroscientist
who really walked me through exactly how the brain works. And the conclusion is this worse than I
thought. For the human brain to change its attention from one thing to another is a messy process,
especially if it's a very different context you're changing your attention to. It can take a while.
take up the 15 minutes for you to really inhibit the old networks that were fired up and
amplify the new networks. The problem with glancing at an inbox is that you're seeing
wildly different contexts. You're seeing information from different people about different things.
It's from other people. So our mind treats it is very urgent. As soon as we look at that inbox or
that Slack channel, we initiate a sort of drastic context shift in our head. Here's the thing,
though, we're only looking at this temporarily because it's the hyperactive high vine. And really what
we're doing is just seeing, you know, we're waiting to hear back from, you know, we're trying to
schedule a meeting and just say, hey, did I get that message back? That's why we're checking so often.
So after a minute, we try to then abort that context shift and go back to the original thing.
And now we're trying to slam the brakes on that and come back to where we were before.
And the whole thing creates a cognitive pile up that is exhausting.
It's why we feel so fatigued.
It's why you only get through 10 pages, you know, instead of 30 when you're trying to study.
Yeah.
It makes us anxious.
And we can't think clearly.
So it's literally one of the worst things you could do for your brain if your job is to actually
use your brain to think clearly and produce value. And so this is why I'm so down on the hyperactive
hive mind is it is an insane way to organize cognitive work. What if I'm one of those people,
and I'm not, but what if I'm one of those people who says, oh, Cal, that's cute, but I'm
great at multitasking. I'm so good at it. Look how much of it I do, right? There's a lot of people
who think that way, and I know you studied this. And is that just a big delusion?
Yeah, unless you're a cyborg. If you're a cyborg and you're running off a computer chip,
Sure.
Like, computer processors are great at this, which, by the way, I think it is, it's no coincidence
that this mode of hyperactive high mind working was really influenced originally in Silicon Valley
because in Silicon Valley they're very influenced by tech and how to computer processors
work.
They're entirely agnostic to what they're executing, right?
You give it a command and executes it.
It's just a circuit that it has an oscillator that gives it a pace, like a clock speed,
right?
So just execute, execute, execute, everything takes the same amount of time.
So if you're a tech guy and you're thinking about a computer processor, you're like,
We just want to make sure there's as much stuff in the queue as possible.
So the processor always has a command to execute.
The thing we want to avoid is like having downtime.
And so then they started to think about the human brain that way.
Low friction is good.
More information is better.
More things to look at better.
More things to do better because we're keeping the processor queue.
They call it a pipeline and processor design.
We're keeping the pipeline full so that we're always executing.
But the human brain's not a processor.
It is not agnostic.
If you want to change from working on a marketing essay to giving an answer to your boss about an upcoming event,
you need 10 or 15 minutes.
So no, you can't multitask.
And you can't context switch really quickly.
I mean, people delude themselves into thinking they're single-tasking because they don't have
the inbox open.
But if you're quick checking every six minutes, it's the same damage, right?
You're never given your mind time to actually fully adopt the cognitive context of what
you're working on.
So no one can do it.
I mean, you can do a lot of stuff back and forth, but you're doing it poorly.
It's just like people say, look, I'm good at drunk driving because I do it all the time.
Like, look, if I was going to test you, I'm sure you're hitting a lot more cones than you
think you are because the brain doesn't function as well when it has a lot of alcohol. Well, you can't
think it's clearly when you contact shift every six minutes. Right. We just think that we're good at it because
we're doing so much of it. And that really does make sense. There's a lot of things, even in this job,
look, I read books and I talk to smart people. That's the crux of the job. But, you know, there's also,
hey, this advertiser sent some pretty bad copy. Can you go over this and make sure that it sounds like you
and you're not going to be embarrassed when you say it? Yeah, okay, I really don't want to do this. I've got to
rewrite this copy. It's two paragraphs, right? This is a 60 second.
this is short. I will screw around and avoid doing it by doing quote unquote other work. And this isn't
simple procrastination. Maybe it is simple procrastination, but I can make myself feel like it's work and I can
quote unquote get other things done. But I can also make a 30 second, 90 second task take 30 to 90 minutes
by shoveling email and other things in there. And it's not like I'm getting to inbox zero. I'm
literally just looking at different screens. And I find myself doing this when I am anxious
about something else, I'll go, oh, gosh, I don't want to look at this balance thing or this
conversion thing, or this isn't working. I wonder if I got an email. Okay, and then I go, wait a minute,
not only am I using anxiety or sort of burying anxiety in my email or in other tasks, but these other
tasks are creating the anxiety that I have in the first place. And it's this gross, icky cycle where I go,
okay, I'm anxious. I need to answer some of my email because I can feel it piling up. I have like this
invisible sixth sense, right, that my inbox is filling up while I'm not looking at it. And it makes me
edgy. So then I plow through all of it. And then I go, crap, I haven't done any real work today.
All I've done is email. And then I get more anxious. And I find that this is a, not only a self-fulfilling
prophecy, but there's nothing I can really do to get rid of it. Unfortunately, I can mitigate it
somewhat by answering a bunch of email, but I know that that's not the answer because it's basically
like taking another hit off the old Gmail crack pipe. And then I'm trying to,
to get back to life and I can't do it because I'm just waiting for the next, I'm just waiting
to get that thirst again, right?
Well, I mean, this is what's happening is that, okay, you start checking email because
you have to as the hyperactive hive mind.
That's where stuff is happening.
This reduces your ability to think clearly.
It gives you mental fatigue and it gives you anxiety.
Well, once you get fatigued and anxious, you don't have the cognitive reserves anymore
to do the hard thing.
Right.
So they're like, well, I guess I'll just go do the easier thing, which is email, which
makes it worse, which is we get into the, and then you end up at three or four in the
afternoon, just like half-heartedly emailing.
And then what do you start interleaving?
Well, like some social media.
I got to check in on the trade rumors for the baseball, right?
Because now you're just completely toast.
It's a terrible way to work.
But imagine what the impact here is on the economy.
If we have an economy that now is at least half of the workforce is doing cognitive work, office work,
where the hyperactive hive mind could be relevant.
If we have most of those workers who are basically in those type of cycles,
and that means we are getting a fraction of the potential productive output out of a major portion of our workforce, right?
Like this is more than just like individuals like, ah, it tires me out or I'm annoyed by how much I have to check email.
We have like a real problem here because we have a giant section of our workforce that is working in a way that makes it impossible for them to get anywhere near the amount of actual value production they could do.
A lot of people think that if you're overwhelmed by communication, it's because you need to batch things and turn off notifications.
And this is what I've done largely.
But that doesn't really address the problem, right?
Yeah, we can't solve this problem in the inbox.
And I think that's why it's so important to identify the hive mind as the issue.
So if the underlying way that you collaborate is through unscheduled ad hoc messages,
that means you actually have to be checking these inboxes because that's actually how decisions are being made.
It's how information is moving.
It's how progress is being made on projects.
So if the hive mind is your underlying workflow, the more time you're not checking, the more problems you're creating.
That's why it doesn't work to say, we'll solve this with individuals tweaking their habits, right?
Which is a standard sort of techno-instrumentalist type response.
Well, all tools are neutral.
We have our work, and then we have email and just use email smarter.
It doesn't work that way, man.
If your organization needs you to be moving back and forth real quick in email, which most
organizations do, you can't just do the Tim Ferriss auto responder and say, yeah, I'll check it,
you know, at three.
Because between now and three, you have put a lot of grit in the gears of your organization.
So once you realize that, you realize, oh, we're not going to solve this with my habits.
We're going to solve it by actually taking that underlying workflow and saying, let's replace that.
let's find other ways to work together and collaborate that doesn't involve just hit me up with a
message and I'll bounce it back to you, right? We got to fix the problem under the inbox. We're never
going to fix it in the inbox. Yeah, this is this sort of velocity of communication speeds up.
And then you end up with tools like Slack where they say, hey, look, no more CC, BCC, just have channels
for everything. And you go, great, that does maybe cut down on the number of emails, but it has all of
the same underlying problems, right? Well, Slack's important. So when they were acquired, when they
acquisition was announced when Salesforce was going to acquire Slack for a lot of money, and this was
announced in the fall. The New Yorker asked me to write a piece about it, right? And what I ended up
titling that piece is Slack built the right tool for the wrong way to work. And I think that's
the right way to understand Slack. Basically what they said is, oh, I see, we're using the hyperactive
hive mind as our main way of collaborating. So ad hoc unscheduled back and forth messages. Well,
email is not the best tool for the hyperactive hive mind. We can build a better tool for the hive mind, right?
Like, don't you CCs, let's be on a channel, and we need the archive to be searchable,
so you don't have to go back through your inbox.
And so, yes, if you're implementing the hive mind, Slack is a better tool than the inbox.
So we love Slack because it's better than email for that way we work, but we hate Slack because
we hate the way we work.
Right.
And I think that's how we understand our confused relationship with Slack is they didn't solve
the underlying problem of the hive mind.
They said, if that's what we're doing, we got a slicker tool for you.
Right.
So basically, it is, as you said, the right tool for the wrong way of working.
And so, all right, we know our brains don't parallel process information like processors, like computer processors, so we can't multitask attention residue. Is that the concept of not being able to switch quickly because we're still sort of secondarily focused on the thing we were doing before?
Yeah, it's a term from the psychology literature about when you've switched over to something that have come back, the leftover attention from that thing slowing down your ability to think. And then you can dive into the neuroscience literature and see what's actually happening here. It has to do with networks being inhibited or amplified. But from the psychology perspective, which is a layer above the neurons, they don't care about what's actually happening in the brain. They just want to measure it. The term is attention residue. So you can measure like the more this thing is still on your mind, the worst you do at the thing in front of you. And then being overly responsive.
degrades our ability to do the heavy lift, the deep work, and then not just our habits,
not just batching emails, because that can cause more stress and more unhappiness, because now
we're basically throwing problems onto other people or messing up the whole organization.
And then I assume that it's just kind of like, we're just pushing the problem off until a
later time, but we're not actually creating a better workflow by doing that.
Or maybe you're in a nice position like Tim Ferriss or you or I could maybe get away with this,
but then everyone else in our organization is like, well, it really sucks because now I'm stuck
waiting for him to check his effing email.
And then, of course, you have the emergencies where your team can just call you.
So now your phone's ringing all the time instead of you being able to at least look at a slack or an email.
And it just kind of causes a problem unless you're comfortable with everyone moving slower because
of you, which is not great for business.
Yeah, and I heard a story like this recently.
It was a podcast was talking about the book.
And I think it was a software developer.
He was talking about his company was fine.
Like, we're going to send you to like a resort.
so you can be left alone and just work on this and get this system done.
And he said he was there for about two hours, like 1030 the first morning, before they started calling him and saying, hey, I need you to check your email.
Because I sent you something I need you to respond to.
And he's like, that first hour and a half was the only actual work actually got done in that weekend.
So yeah, this is the whole problem.
We have to replace our rules for how we actually collaborate.
And I think this is really important because it explains why we've had so much trouble with this issue.
We've known that email overload is a problem since roughly 2003, 2004.
That's when you really first start to pick up the threads of people saying, whoa, wait a second.
This is getting a little out of control.
That's when we shifted from Meg Ryan and Tom Hanks and you got mail where it was like,
a message.
And like everyone's excited to David Allen.
And, you know, all I do is handle inputs.
That was between 1998 and 2004, right?
So by 2004, it became a problem, right?
So we've known it's a problem.
But our issue is the way we try to solve it is we just tell people we'll have better
habits and it's never going to work. So we we try things like email free Fridays. Remember those,
right? No email on Fridays. Why does that never last? Because email is how you get your work done in your
organization. So if you say no email Fridays, you're really just saying Friday is a day off, right? And,
okay, turns out that doesn't work that well. Or we say let's have better response time norms or
expectations. Why doesn't that work? Because if back and forth email is how we make decisions and we have
to make this decision today, you got to respond right away. Because we have to do six and seven back and
fourth to solve this thing. We have to solve it by EOB or COB or whatever. So no, none of that stuff
works. It becomes back-to-back meeting Friday because everyone's got to sit in the same room if we're not
using email. Yeah, which might be better. I mean, I look at, let's look at like car manufacturing
as a useful analogy, right? Like how we got from the way we used to build cars in the early 1900s
to the assembly line, which was 10x more effective, right? We went from 12 hours to 90 minutes or
something like this, right, man hours per car, the Model T plant at Highland Park.
The way we used to build cars was very flexible and convenient and easy. It was called a craft
method. It was what you would expect. Let's put a chassis on some sawhorses, have a group of craftsmen,
and they sit around and they build a car. Now imagine, like, oh, we want to do this faster.
And our only idea was like, let's run faster when we go back and forth to get the tools.
Like, let's give the craftsmen better shoes so they can move faster without falling. Let's, like,
maybe move the tools a little bit closer to them so they can grab what they need a little bit
faster. That makes it a little bit faster, but what made Ford the largest company in the world
and Henry Ford, the richest person in the world at the time is they said, no, no, we have to
completely change from scratch how we build the cars. And it shouldn't just be on a chassis.
We're going to have the chassis move on an assembly line. It was a huge leap, completely different
way of thinking about the work. Right now, we're doing the craft method and knowledge work.
It's easy. It's convenient. We just rock and roll an email. Everyone knows how it works. There's no hard
edges. We just kind of figure it out. And then we try to make ourselves more efficient by basically
doing the digital equivalent of putting on faster running shoes or moving the tools slightly
closer. Like, let's get rid of the friction in our email client so we can auto-complete our text
or let's have the interface be really slick so we can move more messages back and forth or AI
filters to move our messages around faster, never realizing the big leap is going to come when we
say, let's get this chassis off the saw horse in the first place and change completely how we
coordinate. It's funny that the pull of email is almost, it seems like it's almost based in,
there's an evolutionary reason why I can't just ignore my email. It's like,
I'm ignoring my tribe. And I'd never thought about this. I thought, wow, I really programmed myself to
have anxiety around email. What a weird dysfunction I have. But it turns out that at least you're
hypothesizing that there is a pull that is built into our DNA, right? This is our like ape monkey brain
saying, hey, you can't just ignore communication from other people, even if it's a freaking forward
with an attachment that is irrelevant to your life. Yeah, I mean, we take social interaction very
seriously as a species for obvious reasons. It was key to our survival for hundreds of thousands of
years. So the idea of there's communication piling up that I'm not responding to right now makes us
anxious. Now, we might answer like, yeah, but it's not important communication and we have
response time norms. But here's the thing about those ancient instincts. They're not very susceptible
to reasoning, right? Like think about our instinct for hunger. Hunger feels really bad. It's very
distressing to feel hungry, right? You can explain to yourself, we have lunch reservations in 90
minutes. We are not going to starve. We are for sure going to eat. There's no reason for you to be
for us to have this bad feeling because we know we eat lunch every day. It's not a problem.
It doesn't make the hunger go away, right? Same thing with the social anxiety. You can tell yourself,
this is not a tribe member that we're ignoring at the fire. It's a four word probably. It's okay.
No one expects me. We have a rule we wrote down about don't expect a response within four hours.
That deeper part of your brain that prioritizes social interaction doesn't care. People want us.
We're ignoring them. And so it gives us this background hum of anxiety, which it
Again, we kind of just treat this stuff as normal, but then when you find teams or companies like I profile who have moved away from the hive mind, the terminology they use is it's always relief, happiness, joy. And it's because they're switching to a cognitive environment that is just so much more peaceful and less stressful and less anxiety. They didn't realize how tense they were with the way they were used to working until they actually move into a way where there's not an inbox filling all the time. And they don't have to check something every six minutes. Until they move to that, they don't realize.
how bad they were feeling with the status quo.
What about those people that never answer anyone?
Did you study those people at all?
You know, those folks, like, I've got a few of them in my life,
and they've got, like, 72 unread text messages,
and I'm just like, how are you able?
I'm both disgusted by it and jealous of it, right?
Like, if there were 72 unread texts on my phone,
I wouldn't be able to go to bed until I read them.
And there are people that get texts all day,
and they're like, eh, or they get so much email,
and they're like, eh, I'm just going to mark his unread or delete it.
and whatever, I don't want to deal with it. Are those people wired differently, or have we broken them with our email culture and they've just given up? What do you think? You know, I don't know. They're probably the better adapted ones of us, right? They're the next step of evolution. They've moved past that human need to have to do these responses. Though I would actually, I should admit, I'm kind of one of these people because I do time block planning. When I'm working on one thing during a certain time of my day, that's what I'm working on is my phone is not there. And often I get to my phone later in the day and there's all these different text messages on. It's like, I don't know how to go.
through all these. And so people have just learned, I probably won't answer because I'll probably have missed it.
So I am one of these people and I'm still around. But really the model, the people we should look to is not the people that just give up, but the people that replace. They say, here's the communication that I need to do in my life and in my business. I'm going to actually think through how I want to do it. And here's how it works. And they come up with these processes, these workflows that don't require unsolicited, unscheduled messages. So when we when we shift our attention to the solutions, they all feel like the same type of thing.
You put in place alternatives to the hive mind.
So they're like, here are my rules or guidelines or systems for doing X.
Here's my rules and guidelines and systems for doing Y.
And the things that these rules, guidelines, and systems are consistently trying to optimize for is less
unscheduled communication.
That is the killer.
If this requires like a message to arrive at some point, I don't know when, but when it
does, it needs me to respond.
Think of that like productivity poison.
And be willing to do a lot more work up front.
Be willing to miss some things and it's a problem.
Be willing for something to be more complicated if it's significant.
cuts down the number of unscheduled messages that might arrive that you are going to have to respond to.
You're listening to the Jordan Harbinger show with our guest, Cal Newport. We'll be right back.
Now back to Cal Newport on the Jordan Harbinger show. What about those of us that are in an executive
type role where we're making loads of decisions all day? Are those people the exception to this?
Why or why not? Because, you know, you hear about Jack Dorsey and it's like, all right, what about this?
Cool. Fire off this text. Fire off this Slack message.
or email, whatever they use to communicate. And we kind of hear about how CEOs are uniquely
positioned in companies to execute and make decisions all day. They're usually not sitting around
and making an investor report. That's this assistance job. They should just look at it and go,
this looks right. You know, there's a lot of, there's a lot of that in corporate America. And I think
a lot of us feel like those people are the exception, or we feel like we are one of those people,
therefore, we're the exception. How much of that is even accurate? Well, so in this book,
I break down types of knowledge jobs in the three categories.
There's the makers, the people who need to give sustained concentration to things for a long
amount of time.
Then there's the managers, which is what you're talking about, people who manage teams, executives,
et cetera.
And then the minders, which is my team for administrative support, right?
So you're an assistant, for example, or an IT professional.
Like, you're in a support role.
My argument is in all of these cases, you want to avoid unscheduled messaging as the
main way that you interact with the world, that our mind works best when it's sequential.
One thing until you're done, then the next thing.
Now, if you're a manager, these things might.
might not take six hours, whereas if you're a writer, my one thing is I'm going to write all day.
If you're a manager, it's like, no, no, I'm Jack Dorsey. I'm going to make 10 decisions today,
but you're going to be much better off if those decisions are sequential. And each one gets your
full attention until you're done, and then you move on to the next. As opposed to, I'm trying
to decide on this, but I have to also have a incoming, unpredictable flow of messages I also have
to respond to. And I give some examples about this in the book. First of all, I cite research that
shows if you look at managers, as their email count goes up, their behavior shifts away from
leadership activities and towards what they call productivity activities. You shift away from
actually making big decisions, getting people what they need, moving your team forward, the type of
stuff you need to get ahead. And you shift into just, I'm just trying to keep up with messages. So it makes
you worse at what you do. And then as a counterpoint, I tell the story of George Marshall, the first five-star
general in the history of the U.S. military, who basically ran the U.S. Armed Forces during World War II.
So a very busy, complicated job. He came in and said, okay, I'm not going to be responsive all day.
So he quickly restructured the whole war department.
So instead of there being something like 200 people who could directly report to him,
it got cut down to a couple dozen, and then put in place some pretty strict processes.
Here's how it works.
We have these meetings that are set up to maximize my decision-making potential.
You have to do all the work in advance.
You come in.
Don't salute that waste time.
You sit down.
You hit me.
You get right to like, here's the crux of it.
If you're not prepared, I'm going to yell at you and you're out of there.
I think for a second, I give you my best decision.
We move on.
I'm huge about delegation.
these people handle these things. So he was running World War II and would finish work at 530 every day.
Because he had a heart condition. He thought it was healthy. He didn't want to work. So he won World War II without working path 530, right?
Yeah, and we're running podcasts and can't finish work by 530.
It can.
And Jack Dorsey, by the way, is an interesting example because, you know, I used them in my book
deep work as an example of, like, what you were saying.
Like, well, maybe executives have to be more responsive and it's a different type of job.
But then I heard after that book came out from one of his early stage investors that said,
oh, that's not a valid way to think about what Jack is doing here.
It's actually very sequential and very deep.
We actually set up his day because, you know, he has to go between Stripe and Twitter.
We actually set up his day really rigorously.
Like, you're going to come here and.
you're going to meet with these people, make a decision. We're going to move you here,
talk to these people, make the decision. And so what he does is cognitively very exhausting. He's
not on his phone answering emails. He's being moved from place to place team to team like George
Marshall. Give me what I need to know. All right, think here's my decision. All right, let's move us
on to the next. So the key thing I want to emphasize here is sequentiality. Concentra on this thing,
completely finish it, move on to the next thing. If we can set up our work to do that,
whether we're in a VA or a CEO or a computer programmer, that's going to be the best way to
work, even of how long these things are vastly different. Sequentiality is key. Having to tend to
unscheduled messages at the same time is going to hurt your ability to perform no matter what type of work
you're doing. Email additionally, I took this from the book here, reduces friction, this is a
paraphrase, email reduces friction for us to delegate work to others or have it delegated to us,
which actually decreases efficiency because of switching costs and overwhelm. And this is counterintuitive,
actually, because it seems like it would be more efficient for me or for anyone to be able to
delegate things faster. But at the end of the day, when I look at this, I'm kind of just pouring sand
into somebody else's underwear instead of my own, right? I'm going, oh, I don't want to deal with this.
Jen, fire this off. Oh, this thing's, all right, fire this off into somebody else. So I'm actually just,
instead of being an umbrella for my team to do their work and sort of protecting them from this,
all I'm doing is funneling disturbances to specific people myself. Who just bounced around?
I call it obligation hot potatoes. So once you get overwhelmed, but there's so much stuff coming to my inbox,
and I can't keep up with it.
Now it's just everything I see here is every obligation on my plate is a source of pain.
If I can take it off my plate, even if temporarily, I get a little bit of relief.
So then what do we do?
We send the nonsense email.
We know that, you know, thoughts, question mark, or, hey, did you see this?
We're like, they're just going to send this right back.
But you know what?
In the moment, it's off our plate.
And you get that little bit of relief, right?
And then they get the email that's like, I don't know, what do you think about this?
I'm like, I don't want to deal with this.
And they're like, let me just forward it, you know.
Yeah, yeah.
Bob, didn't you look at this before? Send, you know, hot potato right?
He's going to throw it back to you. So then we take each of these things and we bounce them around
and we generate dozens of back and forth interruptions and emails. There's this story I tell in the book
that was really interesting about a guy who hated how much his boss bothered him with email,
urgent email task during this period every week where he had to set up a lab. It was an R&D company.
And it was, he get interrupted and would take him a long time to finish because he kept having to
go respond to these questions that his boss would bother him with.
Then this researcher named Gloria Mark and her team from UC Irvine came and said,
we're going to run this experiment at your company where we're going to take some people,
we're going to take them off email for a week.
And we're not going to plan for it.
We're just going to do it and see what happens, right?
So this guy who was sent up the lab was one of the people they took off email.
His boss stopped bothering him during that week.
And Gloria was telling me about this.
It's not in the paper.
She was just telling me about it, you know, after the fact.
She said what was really eye-catching about this is that his boss's office was two doors down.
So the friction, increasing the friction from pressing send to walking 10 feet and
opening the door and saying, hey, can you do this, drastically reduce the amount of things that
the boss put on this guy's plate, which shows that this notion that this is all critical and this all
needs to be done is really inflated. When you take the friction out of the system, we send a lot more
stuff to people. We put a lot more stuff on people's plates. The amount of work we do, the amount
of work we delegate, it all spirals out of control. When you take friction out of systems,
weird things happen. All right. So if I'm telling myself this story here, it's, hey, maybe you don't want
somebody to be able to fire things off to you really quickly because for a lot of these things,
in this guy's case, especially, it never needed to get done. So it wasn't something where it was like,
oh, this is so great. I can hand things to Cal right away. It's, while I'm not allowed to send this
to Cal with two keystrokes, I'd have to get up out of my chair and go tell them about it. It's not
important enough for me to do that. Not that important. So we kind of want to increase friction at least a
little bit. Look, I don't want to have to fax you something that's 58 pages. That's a pain,
especially if you just need to skim it, right?
So we don't want that kind of friction,
but we do want enough friction where I say,
maybe he doesn't need to skim this.
I'm just going to call him, read him the relevant part,
and say, does that sound right to you?
And if it is, then we're done with this whole thing,
no meeting, he doesn't even have to read it.
Right?
We want to have the right kind of friction in place.
An easy example of how to do this
is a notion from Jason Freed's company base camp
is office hours.
They have these subject matter experts there.
People are always bothering them with questions.
They said, well, here's how we're going to do it.
There's office hours.
These are the times each week when these people are available.
It's mainly a remote company, so hit them up on Zoom.
They'll be there.
No appointment needed.
Ask me any question you have.
But if you have a question in between, you have to wait.
Wait till their office hours.
And you know what?
The important questions still get answered, but you have drastically improved the cognitive
environment of those experts, but also the number of questions goes down a lot because
it's a little bit more friction.
Like, yes, you can definitely ask Jordan this question.
He's here to help.
You got to wait until Thursday morning.
And you're like, all right, maybe I won't.
Or maybe I will, but you get to do it all at once and it's not constantly interrupting you.
So yeah, I think friction is great.
I wrote a blog post recently to when we're recording this about this notion of reverse meetings.
What if instead of you being able to gather five or six people together?
So you're taking an hour of all of their time to come together so that you can get their
feedback and make a decision on something.
What if we reverse this and said, no, everyone has office hours.
You have to go to each of their office hours one by one and ask them and get their opinion, right?
So, yeah, you have to spend much more time than the other people.
Well, A, that would cut down on a lot of meetings, but the meetings that do happen, the overall number of man hours cost it would be significantly less because now I'm talking to five people for 10 minutes each, as opposed to having five people that have to sit there for one hour. And you're getting a three to four time reduction there, depending on how many people were involved with, right? So I like adding friction. You don't want to make things prohibitive, but you don't necessarily want to make things easy. Right. But you kind of do want to make certain things prohibitive, right? Like, I don't want it to be easy for people to send, I have a small company.
so this doesn't really apply as much.
But I don't want people to be able to send,
what does everybody want on their pizza for lunch?
It's like there should be enough friction
where that just doesn't ever happen, right?
People should on Mondays or in the beginning
of the freaking year put into a spreadsheet
at some point during the day what they are allergic to
and then everything else is on the table, right,
for the pizza on Friday.
There should not be a circulating email
where people say, ooh, no green peppers this week,
not feeling it.
Like that kind of, and we laugh about these examples
and yet when I worked in corporate America, how many of those exact type of, does everybody like coconut
flakes on their cake for Thames's birthday? Good Lord. Why am I doing this instead of billing a client?
Yeah. Why does this exist? And it's because somebody who had five free minutes literally had to fill those
five free minutes with some sort of anxiety-inducing thing. And then they passed the virus on to the other 300 people in the office.
And I like asymmetry and cost. It's another thing I think is important. You need to make the cost higher in general for the person who is
about to commandeer attention than it is for the people whose attention is commandeered.
These asymmetries are very good in regulating these systems.
So another corporate America example is you have all of these administrative units in
large companies.
And they tend to just think, like, what's going to be easiest for our unit, right?
Like, what's going to make it easiest for us in the HR department to get what we need
the file compliance forms or something, right?
But that could be at odds with what's going to help this company produce the most value,
because now you have the frontline executives having to answer these emails.
So you can imagine, for example, a world where.
No, you cannot directly mass email employees.
You need to fill out this form.
We want to tell you about this new initiative.
Because every single administrative unit is just like, it's convenient for us if we can just send this to everyone because we care about this.
Like imagine a world we're like, no, there's some sort of attention ombudsman, right, for each of these different teams or whatever.
And you've got to work with them.
And they put together a weekly digest, almost like a newspaper of all the announcements, things that people need to do.
Here's what's happening from the administrative units.
You've got to work with them and here's what we need in there.
And it all gets put together.
And once a week, this one thing, as part of a weekly status meeting, this thing gets sent to everyone.
And there's a quick review of like, look at this thing.
There's 15 announcements and three requests in there.
And look at there, there's two things in there you really have to do.
You only see this once a week, right?
Hey, it's more of a pain for the HR department.
But who cares, right?
I mean, your company doesn't grow because the HR department is efficient.
It grows because you produce the things that produce value.
So also this notion of asymmetry and costs, I think, is critical.
If it gets way out of sync, if in five minutes I can commandeer 50 or 100 overall minutes of attention,
that type of asymmetry is where you really begin to get problems.
I think about this with this podcast sometimes as well, not so much in the administrative sense,
but I've trashed episodes before where I go, oh, I just can't release this.
And I'm sure you have done that as well.
And people go, oh, why not?
I mean, you know, you never know.
Some people might like it.
It can't be that bad.
You're just being hard on yourself.
And I think, well, okay, if I waste an hour of my time recording a show and I wasted
four hours of my time or 10 hours of my time preparing that show, that's a long time. Let's say it's a 15
hour or 10 hour long show to prep. But then I send that out to 200,000 people and half of them,
just half, listen, and waste an hour of their time. I've wasted 100,000 man hours of people's
time. Yep. Now, maybe they were working out and running at the same time. But in theory,
I've wasted 100,000 hours of, like, decent cognitive cycles in global humanity.
That's kind of like a, that's a war crime, right?
There's a Geneva Convention Amendment waiting to happen where it says, what the hell were
you thinking?
Don't ever do that again.
You've just burned trust with all these people.
And also, like, we're all dumber for having heard this episode of the Jordan Harbinger show.
How dare you?
Yeah.
So you think about it like that.
But at work, we're more than happy to go, hey, we made this really annoying spreadsheet that's
going to tell everyone whether or not you can eat.
coconut flakes for Jim's birthday cake. And it's like, send that to everyone. Yeah, well, let's do
an extreme case study, right? Let's imagine we're in a company, there's a team of 20. I don't want to
keep being up on HR, but you work in whatever, right, in an administrative unit. And you're like,
you know what's going to make my life easy? I need to get this information from everyone so I can
fill out these federal forms. And you send out this confusing spreadsheet and no one even knows
what half the terms mean. And you're like, you just email it to the 20 people. Hey, everyone,
I need this information. It would make my life easier if you could just fill this out and figure
it out and it would make it easier for me to fill out the form, right? So you have 20 people now that
you're taking up a non-trivial amount of their time and attention. The flip side of this would be like,
that's so expensive. Imagine we did the opposite. Imagine that person who was sitting out the form,
instead went to all these offices and hung out for a day and kind of waited until he saw someone was in
between something. And then came in as like, okay, I see like you're growing to grab some coffee.
Let me just chat with you real quick and kind of figure out, I'll fill this out for you.
Like, let me just talk to you because you don't even know what all these terms mean. Let me just
ask you some questions, I'll fill this out for you. That guy spends all day doing that, right?
Minimal impact on each individual person, he has a really hard day, right? That's probably way,
way better. But we don't think that way. That guy's like, I don't want to spend a really hard day.
Are you kidding me? I have a Google form that if people would just take a couple hours and figure this out,
it makes my life easier. Why do we want your life to be easier? If these 20 people are computer
programmers, I'd rather have them not waste an hour of code production, right? So even if you
push this thing to an extreme, I think especially administrative facing units should think about like
how can we minimize our impact on people's time?
Right.
Even if it takes a lot of effort on our part, there should be a lot more invisible UI, a lot more
like, let me just do this for you, walk you through it, a lot less of these interfaces that
make their job easier.
They should be thinking, how can I sacrifice some more of my time and attention to make
sure whatever the frontline value producer is time and attention that could be more spent
on this?
That's actually what everyone's job probably should be.
But we tend to focus instead on just a personal, like what's easy in the moment for me.
Now, that totally makes sense.
There was a, I remember, again, when I worked on Wall Street, like very corporate environment, obviously.
They would say, you'd get an email from HR that would say, we made it like a video training
for you to figure out how to use our healthcare reimbursement, HSA, whatever, system.
And so every lawyer, bear in mind, an hour of my time as a first year associate was like
$300 or something to a client or $250, let's say.
So all of us, the whole firm, is watching these stupid-ass videos.
And sometimes the video wouldn't play.
you watch the video, you got to pay attention to it, then you have to log into the system,
you're setting this thing up. And I remember, finally, one of the partners came in and knocked on our
doors. And you know, when a partner comes in, you're like, uh-oh. And he goes, don't bother with
this. We're going to find a different way to deal with this. And I'll never forget, because I
remember thinking like, oh, I got to make a note of this. The different way to deal with this was,
we all don't do it. And someone from HR will have to come to the real estate finance department
and go, was there a problem? And then the partner's plan, I think, was to go, can you just do
this for everyone because we're really busy. And that's what happened. Yeah. That's exactly what happened.
Which makes complete economic sense, right?
I mean, it makes completely, why should someone who's billing out at $500 or $600 an hour spend two hours to make the HR department's life, you know?
I don't want to keep saying HR, but I just don't know.
I'm not from corporate America.
Yeah, right.
Yeah, I'm not from corporate America.
So I don't know.
We only know three positions, HR, me and my secretary who did all the real work.
But there's an underlying point here, which is like we should be much more innovative and radical in thinking about our underlying workflows, right?
Like, okay, here's a type of work we do.
Let's start from scratch.
Like, how do we want to do this? And these are the examples I try to give, like, a lot of in the book.
For some things, they might be very automatable, like podcast episode production. Hey, we can
coordinate the entire team getting from the raw video to this posted. Everyone needs to be posted without
anyone ever having to send an email on Slack. If we can get a pipeline of shared folders and a spreadsheet
that controls it all. And maybe we have some, you know, we have some air table zapier magic going on.
I don't know, right? But like, we could get this so that you, right, sometimes it's not automatable,
but it's like, okay, we're going to have these really set, highly structured status meetings.
We're going to use task boards.
Everything's clear.
Who's working on what?
How much should you be working on?
Let's go.
We'll meet back in 48 hours, right?
Like, we should be willing to think radically.
Like, when I was working on, you know, this book tour, I've experimented with different
processes for working with my publicist.
And like, what I landed on for scheduling interviews was I don't want her to email me
about everything because I can't do a hyperactive hive mind.
Like, what about this?
Well, what about these times?
I'll ask them.
I was like, I know publicists do that.
I can't do that.
Right?
And I tried before in a prior launch, just giving my publicist access to my calendar and just scheduling things directly.
I don't like that either because I want to have a say when things are scheduled because otherwise, she doesn't know all the other stuff going on in my life, but you'd have terrible days and it wouldn't make sense.
And so we had a work around.
I'm like, okay, we have a shared document and you update this.
There's sections in and you update it with like, here's pending interviews and here's the link to schedule it or here's the times they can do it.
I check it twice a week.
I come back in and respond to these things.
Then she puts all the final details at another section of the document, right?
a little more overhead, a little bit more pain, sometimes creates an issue when we need to do a
quick turnaround, but she just calls me in those cases. And I don't have to check an inbox all day to schedule
interviews, and I still maintain control over my calendar, right? It's like, we should constantly be thinking,
not what's the easiest way to do this, but how do I actually want to implement this system? How do I
want to implement that system so that I'm not a slave to these attention grabbing unscheduled messages?
Right, because it's hard to fix a broken workflow, especially if it's nobody's job to make sure that
the system is actually working. As knowledge workers, right, we have autonomy, which means we just
have to figure this crap out, generally. That fuels the hyperactive hive mind. And I think in the book,
you call this the autonomy trap, right? Yeah, this is a really, I think this is a really important
argument because I hadn't heard it before. I mean, I sort of feel like I broke this story.
And I also wrote a big New Yorker piece about this called the rise and fall of getting things done,
which is where I sort of debuted this story, but it's also in the book. As far as I can tell,
basically because of one individual, Peter Drucker, the management theorist, who coined the term
knowledge work in the 1950s and really helped the whole sector take shape and he really helped
the managers understand how do we do knowledge work. He had this really clear idea.
Autonomy, autonomy, autonomy. Knowledge work is different than industrial work. You can't break down
knowledge work into steps. You can't run, you know, add copyrighting like an assembly line. You got to
give knowledge workers autonomy to figure out how to do their own work. And so he introduced this
notion of management by objectives, which of course dominates the world of knowledge work right now.
like what's my OKR, what's my wild, hairy, ambitious goal or whatever, right?
Like, here's our clear goals, but you figure out how to execute it, right?
This has caused a side effect, which is, okay, so we'll leave it up to the worker to figure out how
they get their work done.
But if all productivity is personal, where are you going to end up?
You're going to end up in the lowest common denominator.
The thing that's most easy in the moment, most flexible, most convenient, because no one individual
can push a whole organization to a more complex way of working.
And so we end up stuck with the hive mind.
And so that's why I call it the autonomy trap.
I absolutely believe that the execution of knowledge work needs to be left autonomous.
We can't break it down in the steps.
But the organization of knowledge work, right?
How do we actually organize who's working on what, how's it going, and get the information
people need?
Like that we should optimize the hell out of it.
That needs to be an organizational level thing.
We can't ask individuals to figure out how information flows are tasked or assigned because
they don't have any control over that.
So I think this autonomy trap is why we've stayed stuck in this bad way of working
longer than we probably should have.
There's a lot of other interesting psychological concepts in the book that were maybe not super
surprising, but it was cool to see science behind this.
For example, there was a study that you had written about where you took people's phones
away and you said, ignore it, there's nothing critical coming in, just focus on this task.
And then I guess they called the phone and people just like could not focus.
And the idea behind this was, I'm guilty of this as well.
We think I'm focused on something, but we're kind of not because just having your phone screen
light up or be in the same room or having all of these systems that are kind of broken, even if we're just
trying to ignore them, we're still using precious cognitive bandwidth to focus on something because
the distraction still exists, because the system is still broken. Yeah, and we have this modern mind and
the ancient mind. And that was what was interesting about that experiment is that the subjects in that
experiment had put their phone on silent mode. So they knew, like, calls could be coming in and I'm okay
with the fact I'm not answering them because I put it in silent mode.
And what they did in this experiment is they had a confederate coming to be like,
ah, your phone is messing with the equipment.
We got to move it away from the monitor.
They had them hooked up the heart rate monitor, the stuff you need to measure stress,
which is what we'll see in a second one's very clever.
But it's messing up the Bluetooth.
So we got to move it across the room.
They would only do this experiment with people with iPhones because iPhones has to switch
on the outside for silent mode.
As they moved the phone across the room, the assistant would flip it back to non-silent mode.
And then they would text the phone.
known while the person was now across the room and couldn't reach it.
And so even though they were like rationally very okay with the fact that like their mood
was inside, they might be missing stuff when they actually heard something they were missing
while they were hooked up the galvanometers, they were hooked up the heart rate monitors.
They could just measure the stress response that just jumped off the chart, which I saw as
evidence of like this ancient social mind.
It just doesn't want to be missing communication.
It doesn't care about the context.
It doesn't care that it's an experiment.
It doesn't care that, you know, technically speaking, you were in silent mode before so you
could have been missing things. It's just like there's someone in my tribe right now tapping me
on the shoulder. I'm ignoring them. When there's a famine, they're not going to share their food,
and I'm going to die, right? That part of the brain is powerful. And those type of instincts don't go
away easily. This is the Jordan Harbinger show with our guest, Cal Newport. We'll be right back.
Thanks so much for listening to the show. I love conversations like this. I wish I could do them for
free, but I can't. I'm not asking you for money. I get that money from the sponsors, but they only renew
if y'all buy some underwear or mattress or something.
All the discount codes, all those URLs, we put them in one place.
So if you're jogging, lifting weights, whatever, you don't have to write anything down.
Just go to Jordan Harbinger.com slash deals.
Please consider supporting those who support us.
Don't forget, we've got a worksheet for today's episode.
If you want the drills, exercises, and major takeaways talked about during the show,
they're all in one easy place.
That's in the worksheets, and that link is in the show notes at Jordan Harbinger.com
slash podcast. And now for the conclusion of our episode with Cal Newport. I can't focus on a lot of things
if my kid is in the other room, because he's, especially if he's like, Daddy, Daddy, I can't do anything.
So I have to leave the house and go for walks to make calls because I can feel that we've already
debunk the lizard brain on the show, but I'll say it anyway. I can feel my lizard brain just
pulling me in that direction because, you know, my kid's calling me. It's like the highest
possible priority that a human has. Meanwhile, I'm trying to chat with somebody on.
on the phone or I'm texting or I'm recording something. It just doesn't work. And that leads to a
different question here because we talked about attention capital, at least not, maybe not in so many
words, but you've sort of discussed the attention capital here on the show. But asynchronous
communications, it seems like that would be more efficient, right? I can leave a message for you
and you get it later. And then when I'm checking it again, it seems like that's more efficient.
But according to your book here, it's actually less efficient than synchronized communication.
So is it actually better to just meet and do calls? Because that sounds horrible. And yet I know that that's not really what you're saying, right? We're kind of like, we're almost trapped in between these two things from the look of it. Yeah. I mean, here's a tradeoff, right? So synchronous communication has more upfront overhead because we have to be participating at the same time. That's the definition of synchronous. So like you have to be on the other side of the phone or we have to be in the same room. So it's more of a pain to set up. A synchronous communication is much easier to initiate. I can just shoot off the message whenever. But asynchronous communication requires more total.
messages and more complex messages to get to the same decision, right? So in the moment, it's easier
to initiate asynchronous communication, but overall, you might actually cause a higher cost.
And let's just think very simply about like scheduling a meeting or something like this, right?
To go and find you or to get you on the phone, there's a real pain there potentially.
But once we're on the phone together, we can set up a meeting time in about two minutes.
A lot of back and bad. It's not going to work. What about this? Let's do that, right? It's much quicker to
get started, just send you an email. Be like, hey, we should have a meeting. However,
this may require now seven or eight back and forth messages before we arrive at a time that works for both of us.
And because we're trying to do this in a timely fashion, we're probably going to keep checking our inbox where we're waiting for the next message.
So if I have to receive four of those messages and I'm checking my inbox 10 times for each, I've now generated 40 inbox checks, each with a corresponding context shift that's going to slow down my mind and fatigue me and makes me anxious.
And now that cost of getting you on the phone made that five minutes kind of a pain.
but I'm comparing that the 40 cognitive context shifts throughout the entire day, maybe not as bad as we think.
Now, on the other hand, if we're just constantly on the phone or constantly in meetings, that's not going to work either.
So this is why I come back to for each of the things that you repeatedly do in your work, and I call these processes, you have to actually think, what is our rules, what is our systems, what is our guides for how we do this type of work.
And then you can deploy things like synchronous communication, but in a very structured and intentional way.
And so maybe it turns out, well, I don't want to just call people all the time, but what we do is we have these like daily.
check-in meetings. They take 15 minutes. We can get through a lot of these all at once and, okay,
that's going to be more efficient. Or I have these office hours. So instead of trying to set up these
meetings in the first place, you always just come grab me in the office hours because they're Tuesday and
Thursdays. You're never more than one workday away from them, right? So once we get intentional about
how we do each of these things, then we can get pretty innovative. And that's when the difference
between synchronous and asynchronous, like, oh, I see what's going on here. Yeah, I don't want this to be an
asynchronous thing. But I want to just call you at any time anyway. So let's figure out something that works.
And that's what we start to get the big wins.
Yeah, also email and asynchronous comms, right?
They miss things like tone and cues.
And that can lead to further inefficiency.
Like, oh, I think Cal's mad at me because he sent me a one word reply.
Well, no, I don't think he's mad at you.
Not that I would normally go down that way of thinking, but it can definitely happen.
I've definitely gotten one word or two word replies and gone like, oh, what's this person's
problem?
The problem is they're answering a thousand emails and they're in a meeting.
Yeah.
Right?
So they're distracted.
They're not upset.
it doesn't really add to efficiency to have people wondering what's going through your head.
It's easier to be misunderstood. You can think that somebody, once they say, sure, go ahead and do that
is actually wanting you to go ahead and do it, but really they were being sarcastic because
it's a terrible freaking idea. So then you start making steps towards executing something and they go,
I thought we decided that was stupid. You know, and you might say, don't be sarcastic in an email.
I can't tell. There's no context. And they're wrong for doing that. But it's also like,
well, maybe you should communicate in ways where the context is not completely lost.
Well, we're bad at that.
Yeah.
So we're really bad at linguistic-only communication.
I cite a lot of studies about this.
Written text is a very impoverished form of interaction.
And we're very bad at it.
We have a very tough time actually conveying emotional context just with written words, right?
And when I say this sometimes, people are like, well, what are you talking about?
Like, letter writing is great.
Think about all the great letter writers of times past and George Bernard Shaw writing these letters.
And Darwin had on these conversations with these great thinkers.
And you say, yeah, but have you ever read those letters from a past time when people primarily communicated by letter?
They're really long. And when you read them, they seem really florid, right? Like you go on for paragraphs because it was very hard to actually try to establish like, how do I feel? What's my tone? What am I trying to communicate? You'd have to go on for pages to do this. You know, we make fun of young kids because like look at all these emojis. But you know what? Because they're so text bound young kids, they have actually evolved this very complex use of these.
icons to try to make a more sophisticated way of try and deliver emotional context through
linguistic only communication. So yeah, we're terrible at linguistic only communication. We should be
very wary about it. We're getting a fraction of the information stream we get when like you and I
right now can see each other and hear each other is order of magnitude more information is going
back and forth right now than if we were typing back and forth on a Slack channel. And so yeah,
that's another issue with we'll just figure things out over text. Humans are bad at communicating with
text. Right. Yeah, that's a good point.
made a really dumb joke the other day with a friend of mine,
and I knew it was a dumb joke, he knew it was a dumb joke,
we were all in on this dumb joke.
And so I put an upside-down smiley face emoji,
and I went, you know, it's funny how this doesn't mean anything.
You're never upside-down smiling at someone.
You can't turn your face around your head around.
But everyone knew, this is Jordan's emoji for,
we're all in on this really dumb, stupid dad joke pun, whatever,
that he's sent by text.
And that got me thinking, wow,
emojis are kind of more efficient than me having written a piece.
paragraph about how that joke was dumb, but we all knew it was dumb, and that's kind of why it's funny.
Yeah, but if you were just telling that joke to me right now, no further explanation would be needed.
Right.
I would be like, yeah, he's joking.
Yeah.
It would just be clear because of your tonality, your body language, the context of the conversation.
Yeah, it would have been obvious.
Yeah, and I cited the study I found was funny because they were measuring the sender and a receiver
of emails.
And it's not only do the receivers have a hard time understanding emails, the senders are way too
optimistic about how clear they are.
So when you're sending it, this is where it really gets in trouble.
oh for sure they're going to understand it. And we are wildly off on how well people are going to
understand what we write. So it's not even like we're sending this out and like, I don't know if anyone's
going to get this. This is a bad communication form. In our mind, we're Shaw. Like, this is brilliant and
witty and everyone knows exactly what I'm doing? And on the other side, they're like, what the hell is Jordan
talking about? Pretty much. Yeah, I do not understand this. I'm guilty of that. My wife will look at an
email that she's CCed on and she'll go, you're such a bad communicator. And I go, what? What? I wrote exactly what I said.
And she's like, yeah, but they don't know if you mean now, if you mean tomorrow.
They don't know if you're talking about your company or their company.
And I'll go, oh, yeah, that's true.
It only seems obvious to me because we were just talking about their company and also because
we were talking about this thing that's going on tomorrow, none of which was in the email.
And this is me, like, I'm decent at this.
And yet my wife's still like, oh, my God.
So she has to add two paragraphs of clarification to it, which just illustrates your point
perfectly.
All of that should have been just present in the conversation.
and if I had had a 13 second phone call with somebody,
it would have replaced all of that.
So it does make sense.
I'd love to hear why you think the Tim Ferriss auto responder thing.
Not that we're picking on Tim, you know, nice enough guy,
but why that doesn't really work.
And I've always hated this.
I never used it, well, you know, for more than the obligatory five minutes
when it sounded like the greatest idea ever.
And anyone who tried to do that with me for inside my own company,
they got a couple warnings, and I've actually removed people years ago
from my company for using it.
and we used to make a joke about terminating them,
saying that they transitioned to a four-hour work week, e.g. got fired,
because it didn't really make sense,
and all it did was slow down everyone else in the company,
and we're like, you're the bottom of the totem pole.
You don't get to dictate the pace of communication and workflow.
Like, if I want to do that as the boss, I can.
And I tried that, and it screwed up everybody else, too.
Yeah.
So to give Tim credit, first of all,
like an interesting story about the four-hour work week is,
we think about it now, we think about the lifestyle design stuff, etc.
But if you go back and actually look at how that book took off in 2007, which, you know, he gave a talk at South by Southwest right when it came out that April. And then the book got really pushed by a bunch of Silicon Valley types that had met him at South by Southwest. If you look at the talk and the original interviews they did with him, it was all about email. That was the thing in his talk that actually made that book take off was him saying clearly, this is crazy. We can't work this way. He was like the first person to really say that. So it's actually a really.
important data point when we're trying to go from 1990. There's no email. 1995. It's pretty
widely spread by 2007. He's being hailed as a hero for being one of the first people who
really stand up and say clearly, this is crazy. So the auto responder solution, that's a standard
engineering response. Like it's very logical, right? You're like, well, the problem is I'm checking
email too much, so I should check it less often. And if I just explain how logical that is to
everyone else, of course, how could they possibly argue because I'm being so logical about it? I can
work better. What it was ignoring was human social dynamics. People do not like you explaining how
you're going to work if how you're going to work is going to make their life harder. And so one of the
points I make in the book is that in 99% of the case is better to don't explain yourself if you're
making a change. Don't explain the change to other people. Just do it. And if it generates issues,
then you can get into it and try to accommodate those. But instead of giving everyone a reason to be
upset at you, wait to see the small number of people who actually are, you know, and just deal with them.
But then there's the broader reach. That's social dynamics, right? So if you're going to start
working on some of these processes just on your own, I just recommend, just do it and don't make a big deal
about it. Just do it. Don't explain to people what you're doing. But the underlying point here that
you made is even more important, which is the auto responding batch, whether you do an auto responder
or not, the batching approach doesn't work if the underlying workflows to hyperactive hive
because if you wait until two to check your inbox, that's four hours of back and forth messages,
needed you to respond to you, right? So that goes back to that issue of like, just changing how you
interact with your inbox is never going to be enough to really solve the problem. Right. So let's say that
I work in an organization or even as a self-employed entrepreneur, whatever you want to call it,
if we're asking for forgiveness and explaining why I'm never available, it kind of just makes me
look bad. But if I'm not necessarily available first thing in the morning and somebody asks,
how come you're slow to respond? But I've hit every single project target over the past year or so. It seems
like then they're less likely to mess with the recipes. So the antidote to this could be just perform
really well, which might require you to not check email every five minutes. And then when you're doing that
and someone says, you don't respond to your email within a few minutes. You go, here are my sales targets,
and here is my performance. You know, it's much better than my targets. Nobody else is really doing
that. Or I'm consistently crushing my goals. Does it matter that my response? And then you can maybe
get some buy-in from your superior that says, all right, I know Jordan's not going to chime in on
this thread right away, but he's our top salesperson. So I'm not going to sit here and make him
check Google sheets or make him check slack on his phone because he's performing. So the key is to just
kind of, instead of asking for forgiveness or permission here, just accomplish what you're supposed
to accomplish. And then when people try and mess with your recipe, you say, the reason I'm able to
be at the top of the game is because I'm not doing the hive mind thing. And I think that's a key
idea. Adam Grant calls that the idiocyc secrecy credits. So I've earned credits to be idiosyncratic about
things like how I respond because I'm nailing it. I'm really delivering what I need to deliver.
The other strategy here is to use clarity as a substitute for accessibility. This especially
works with client communication. So often when you're in a situation where people are demanding
quick responses like accessibility, it's because they have no other real way of interacting
with you. And so if you're a client and you have a question, you're like, I don't want to keep track
of this, right? Like, let me just send it and I don't want to remember, I just, if I can answer back
right away, I don't have to worry about this anymore, right? Because there's no other way that
these questions get resolved, then I'd rather just have them answered when I need them.
If you come in and say, okay, here is our system for doing client questions, if it's really
clear and they trust it and it gets the job done, often they're happy, but great, I don't
need accessibility anymore because I have this. The key thing is the questions get answered and I
don't have to worry about them. And so, like, that's one example I like is a company that was just so
overwhelmed by Slack request from clients that they were like, we're going to take a risk.
If we lose all our clients, we lose all of our clients. We can't do this anymore. We can't be
on Slack all the time with them. And they said, once a week, we have a
call schedule. And we are going to write down in that call a summary of everything we talked about.
And importantly, and this is the key psychological trick, everything we committed to in the call.
We're going to write it down. We're going to send that to you right after the call.
The client's like, great, I don't need to be on Slack with you all the time. We know we have
this call on Monday. Whatever the things are that are coming up, great, we'll tell it to you on
Monday. And because it's written down in black and white and we see the commitments, I don't have
to bother you about it. I don't have to be like, hey, what about this? Hey, remember that.
I now can trust it's getting done. I have a paper trail. And they went from being bothered all day on
Slack to they have this one-hour conversation once a week. And the clients were fine because
clarity substitute for accessibility. If you don't give the substitution, you're in trouble.
Right. If there is no clarity about how you interact, people don't trust you to get things done,
if you drop the ball a lot, and then you say, stop bothering me so much in order to serve you better,
I will only be checking emails at 10 and 2. Well, then people are going to get really upset. But if you're
like, no, look, you often have questions about this project. I'm crushing it. And I think we
should throw the questions in the base camp and I check it every day and it gets done.
People are like, great, whatever.
The point is the ball's not being dropped.
I don't have to worry about it.
It's off my plate.
I don't care how you want to do it.
So accessibility can often be traded for this clarity.
This is a great point because there's, I've had a rule in the past and I still do that
I never hired digital nomads for anything.
Digital nomads, if you don't know, are these people that sort of like travel all over
the world, work remotely.
They're usually almost always freelancers that do things.
And I had so much bad luck with them because I noticed they make a ton of systems and they
keep talking about those systems, but they really seem to have almost no control over their time.
They're just sort of perpetually on vacation, and they're almost trying not to do any actual work,
which is a nice gig if you can get it, but I don't want that person in my organization saying,
hey, I don't have internet this weekend because their Airbnb that I'm in in Vietnam,
turns out they actually don't have working Wi-Fi, so I can't download any of the videos
and edit any of them, and I'm like, ah, this person sucks.
But my video editor now, he is a digital nomad, and he does a great job, and he's very good
at communicating expectations, he makes sure that everything is done, he never drops the ball.
So I am understanding of him losing internet for a few days while traveling because often he will
say in advance, hey, I'm going to Vietnam, I'm supposed to have internet, but you never know.
It's monsoon season. Please send me everything you can by tomorrow end of day, and I will get
to work on all of that because I'm going to download it before I leave my hotel in Sweden.
But if I'm hiring somebody else and they tell me they live a digital nomad lifestyle, I literally
throw their resume in the garbage immediately because I don't want somebody who's more concerned with
getting laid in Ukraine than they are about getting their work done. Yeah, I'm with you. So clarity systems,
this is what can really trump, like general accessibility or this or that. So yeah, I really get that. But it's also,
yeah, a good warning that systems are only as good as your actual commitment to executing them as well.
And you know, it's difficult. It's hard to figure these things out. Like here's our workflow for
podcast editing and production. Like it's a pain to get it right. You know, here's our workflow for
comments on our web development projects from our clients. Like I tell the story that I ran a web development
company when I was a teenager in the 90s. And so I was running a web development company where we had
like reasonable contracts, right, like $30,000 contracts, which was a lot for, you know, me as a teenager.
Sure. But I was in high school and I was doing sports. And this was before cell phones and before
laptops, right? So like, we had to figure out how to run a company in a notoriously sort of
demanding interactive industry with basically zero accessibility outside of like the occasional phone
call. And it was like a huge pain, right? We had to build this client extra net and had calendars.
We had to do. We figured out what the key thing was, by the way, work blog. If they could see what
was being done, that was 98% of why they wanted you to be accessible because they didn't trust
you, they were getting their monies worth. So if they could see it, like, all right, the work is getting
done. And then just some clear processes where we consolidated the decisions to meetings and then a
memo would be written and they'd have to sign off on the memo and then you would post the sign
memo in the client extradement.
Like, okay, we've had a creative brief and they could see deadline.
Like, it was a pain.
It was a pain.
It was hard to get right.
But once we got it right, we could run a business without actually having the ability
to communicate with people, basically at all during most of the working day, you know?
And the interesting story about web development is I've talked to some developers about
this.
That was the norm in the 90s when, like, people didn't have cell phones, et cetera.
It kind of went away when the hive mind took over.
Right.
And a lot of web developers today, lamenting.
it. Like, yeah, I remember, that was standard. You'd have these client portals and extra nets,
and the communication was very structured. And by the time that email was very ubiquitous by the
early 2000s, it was just easier to be like, you know what, let's just rock and roll, just go back
and forth all day. Yeah, just BCC, everyone. Yeah. And it made life much, much, much harder and
made web developers. So we know, like in that instance, we could do this. We used to do it,
but the hive mind sort of snuck in and destabilized it. Cal Newport, thank you very much.
there's a lot more in the book, specific strategies, boundaries, how to draw them, how to change up the
workflow, using task boards. I didn't get into all that here because, you know, you can really get in the
weeds on how-toes. But I love the psychology behind this. As always, of course, that's what the show
focuses on. And it's going to be a tough habit or set of habits to break. But there's a lot of ideas
in the book where I go, okay, I'm doing that, right? I'm definitely going to stop responsibility
shifting, aka email hot potato. I'm definitely going to carve out boundaries and stick to those.
and I'm going to encourage my team to do the same.
And in fact, we've done a pretty good job, right?
We have no meetings.
In fact, we just started doing a quarterly meeting
just because we literally never see each other
and it's good to build some camaraderie,
but the meeting is just catching up, chatting.
It's more fun than anything.
And, you know, I'm pretty proud of the lack of garbage
that goes around among the organization,
but there's like seven of us, right?
So the trick is when there's 700.
That's when it becomes like a magical kind of art.
and I think organizations can and should do this because I can imagine how many hundreds
slash thousands of hours each month you get back if you don't just keep the hive mind going.
So thank you so much for your work here.
Yeah, well, thank you.
And I like this pitch.
Buy this book so you can be more like Jordan.
That's right.
Yeah.
That's the tagline of the book.
We should have got a blur from you.
Yeah.
But I love your setup.
This stuff is not just about being less bothered.
It's not about being, you know, a little bit happier at work.
You're going to make more money.
And your company's going to make more money.
and if you deploy these ideas, you're going to be more successful.
So this is why, by the way, I'm optimistic that I'm not trying to change people's minds here.
This is coming.
There's just too much money on the table.
Companies are going to be so much more effective as they get more advanced about how they think about these things.
I'm just trying to give a few people a head start.
So I think that's the right way to think about it.
A world without email is inevitable.
Just a matter of whether you're going to get to that late or early.
And if you want to get there early, that's what I'm trying to help people do.
Right.
It's going to be one of those things where a couple of tech companies start off.
Everyone thinks they're nuts.
then some other companies start doing it. Then there's consulting firms going, hey, you know what?
Look at what Stripe did. And they doubled their productivity. And then in 10 years, Ford Motor Company is going to be like, no more email. We've got this other thing now.
100%. Yep, exactly. And then back to one car every hour. By 1925, everyone, every car company was using the assembly line. But Ford was first and it made them the largest car company in the world. Right. So everyone is going to be getting more sophisticated by how they work. But if you're one of the first to do it, you could reap those benefits. Good call. Well, thanks, Cal. Always fun.
All right, thanks, Jordan.
We've got a trailer of our interview with Howie Mandel, one of the most iconic comedians of our day, and a judge on America's Got Talent.
Howie spent some time with us being especially candid about his anxiety and about how he turned being impulsive into a superpower and more.
Check out episode 210 here on the Jordan Harbinger show.
So what happened was we were doing, not unlike we're doing now, we were doing an interview and he says, thank you.
And we'll probably go to commercial and thank you, Howie.
And I got up.
And I started walking to the door.
And I thought he was, like, wrapping it up and going to commercial.
And then I just said to somebody really quietly, can you back?
Can you back?
And he's going, what are you afraid of the door?
And then he goes, just open the door.
And I got, Ken, open the door.
He goes, just open the door.
And then what happened is I started getting a panic attack,
and I started breathing heavy.
And I just turned to him.
And thinking that he had already thrown the commercial because he was just talking to me,
Howard, please, this is really serious.
I go to therapy for this.
I have something called obsessive compulsive disorder.
I'm about to pass out.
If you don't open the door for me now, you'll be calling 911 and taking me to the hospital.
This whole thing was on the national radio.
I thought, oh, my God, that was probably the darkest space I've ever been.
And I'm walking through the lobby toward the door out into the steaming streets of Manhattan.
I might as well just continue walking and walk right into traffic.
And I stopped just outside the door.
You know, millions of people are on the street, but I felt very alone.
and some guy came into my periphery and said to me, are you, Howie Mandel?
And I just nodded affirmatively.
And he said, just heard you on stern.
And my heart dropped him in my stomach.
And right before I could take off in the traffic, he said two words, which means something
very different today.
But they changed my life.
And he went, me too.
For more with Howie Mandel, including some pretty awkward moments of my own making.
Check out episode 210 here on the Jordan Harbinger show.
Always interesting to wrap here with Cal.
Some of the practicals that are from the book create specific boundaries so that people are more likely
to follow them. An example of this is instead of saying, I don't know if I can review your paper,
I'm really busy right now. You might say something like, I've hit my quota of paper reviews for this
quarter. So in order to argue a point that's a specific boundary, people would have to argue the merits
of your rule or boundary instead of just insisting their request was important. And so this is going to be
far more effective, right? If somebody says, hey, I just need a moment of your time. You can say
something like, I've booked up all my phone time for this week on Monday, but I'm open next Monday.
I'd love to talk to you then. They would have to say, no, I'm so important we have to talk before then.
Or they would have to say, you don't need a boundary, right? It's a really tough argument for them to make.
So if you're specific, you create those specific boundaries, people are more likely to follow them,
less likely to argue. Some of the concepts in the book are kind of funny too. Responsibility shifting,
it's a fancy way of saying email hot potato, right? You get an email, you're not sure what to do with it,
so you fire off or reply asking for some clarification just to get it off your plate.
I definitely used to do this.
Now I flag things for later because nobody can give me anything urgent by design.
It's not possible, really, except for Jen.
She can always do that.
But if I can't figure out what to do with it or where it goes, I just say no.
And it's so liberating.
Hey, I don't know what to do with this.
It's going to require time.
You know what?
I'm just going to not do it.
Can't deal with it right now, not doing it.
The goal here is to spend less time talking about work and more time doing the important
work getting things done in the book.
Includes good case studies of highly optimized workflows if people are interested.
It goes into using task boards and automating what you can automate and then worrying about
what remains.
When we have too many tasks, we don't have enough space to actually reform the workflow to
become more efficient.
So we have to work on the systems so that we can get our deep work done, not just do endless
amounts of busy work.
And I love Cal for bringing this to our attention and showing us a better way.
Big thank you to him for coming on the show.
The book title is A World Without Email.
We will link to that and his other books in the show notes.
Links to all that stuff's going to be on the website.
Please use our website links if you buy books from this show from any guest.
Yes, they work in Canada.
Yes, they work in the UK.
Just use our freaking links, all right?
Worksheets for the episode in the show notes.
Transcripts for the episode in the show notes.
There's a video of this interview going up on our YouTube channel at jordanharbinger.
com slash YouTube.
I'm at Jordan Harbinger on both Twitter and Instagram.
Or just hit me on LinkedIn.
I love hearing from you there. I'm teaching you how to connect with great people and manage
relationships using the same systems, software, and tiny habits, all the same stuff I use to get
great guests like this on the show. That's at our six-minute networking course, which is free over
at Jordan Harbinger.com slash course, teaching you how to dig the well before you get thirsty.
And most of the guests on the show, they subscribe to the course. Come join us. You'll be in smart
company where you belong. This show is created in association with Podcast One. My team is
Jen Harbinger, Jay Sanderson, Robert Fogart, Millie O'Campo, Ian Baird, Josh Ballard, and Gabriel
Mizrahi. I couldn't make the show without them. Remember, we rise by lifting others.
The fee for this show is that you share it with friends so you find something useful or interesting.
If you know somebody who needs better productivity or you want to give your boss a little hint,
hint, share this episode with him. Hopefully you find something great in every episode of this show.
Please do share the Jordan Harbinger show with those you care about. In the meantime, do your best
to apply what you hear on the show so you can live what you listen, and we'll see you next time.
This episode is sponsored in part by Something You Should Know podcast.
Finding a new great podcast shouldn't be this hard, so let me save you some time.
If you like the Jordan Harbinger show, you'll probably like Something You Should Know with Mike Carruthers.
It's one of those shows that makes you smarter in a practical, useful way.
Same curiosity vibe we go for here, just in a fast, focused format.
Mike brings on top experts and asks the exact questions that you'd want to ask,
and the topics are all over the place in the best way.
recently they've covered things like
why we care so much what other people think
the benefits of laughter why sports fans
get so invested and what makes people
like you or not
the through line is always the same smart ideas
you can actually use in real life
something you should know has been featured in Apple's shows we love
and it's got thousands of five-star reviews
because it's consistently interesting
so if you want another show that scratches that
I want to understand how people in the world
really work itch search for something
you should know wherever you get your podcasts
look for the bright yellow light bulb
and start listening. You can thank me later.
