HomeVideos

Why Is AI Making My Job *Worse*? | Cal Newport

Now Playing

Why Is AI Making My Job *Worse*? | Cal Newport

Transcript

1933 segments

0:00

A new research study recently caught my

0:02

attention. It came from a software

0:04

company called Avatra, which analyzed

0:07

the digital activity of 164,000 workers

0:11

spread across more than a thousand

0:14

different employers. And what they

0:16

wanted to do was measure the impact of

0:19

new AI tools. So what did they find?

0:22

Here's a summary of their results from a

0:24

Wall Street Journal article that came

0:26

out last week. Avitra found AI

0:29

intensified activity across nearly every

0:32

activity category. The time they spent

0:34

on email, messaging, and chat apps more

0:36

than doubled while their use of business

0:38

management tools such as human resources

0:40

or accounting software rose 94%.

0:44

Meanwhile, the amount of time AI users

0:46

devoted to focused uninterrupted work,

0:49

the kind of concentration often required

0:51

for figuring out complex problems,

0:52

writing formulas, creating and

0:54

strategizing, fell 9% compared with

0:58

nearly no change for non-users.

1:02

All right, so this research results

1:04

describes in some sense a worst case

1:06

scenario for knowledge work. These

1:08

employees are spending more time on

1:11

exhausting shallow tasks that don't have

1:13

a huge impact on the bottom line and

1:15

less time on the deep tasks that can

1:17

make the most difference. The efficiency

1:20

gain of these new tools seems to have

1:22

made everyone busier but not necessarily

1:26

better. Now, here's the thing. This

1:29

outcome is not unique to AI. As someone

1:33

who has studied the intersection of

1:34

digital technology and office work for

1:36

more than a decade now, I can tell you

1:37

from my experience that this matches a

1:41

pattern that I have seen unfold many

1:44

times before. Here's how this pattern

1:46

goes. One, a new technology promises to

1:49

speed up some annoying aspect of our

1:51

job. Two, we all get excited about

1:54

freeing up more time for deep work and

1:56

leisure. Three, we end up busier than

2:00

before without producing more of the

2:02

high-v value output that actually moves

2:04

the needle. This pattern was true of the

2:07

front office IT revolution. It was true

2:09

about email. It was true about mobile

2:10

computing. And it was true about video

2:12

conferencing. Easier when it comes to

2:14

productivity tech often seems to

2:17

translate to busier.

2:20

This so-called digital productivity

2:21

paradox is what I want to talk about

2:24

today. I'll start by looking closer at

2:26

why this paradox exists.

2:29

What is it about digital productivity

2:31

tools that seem to always trick us into

2:32

being busier? I'll then discuss some

2:35

concrete strategies for avoiding these

2:38

traps. So, if you're looking to get more

2:41

benefits out of new AI tools or you just

2:44

want to repair your broken relationship

2:46

with older technology that continues to

2:48

drive you crazy, then this episode is

2:52

for you. As always, I'm Cal Newport and

2:56

this is Deep Questions, the show for

2:59

people seeking depth in a distracted

3:01

world. And we'll get started right after

3:04

the music.

3:12

All right, so here's our approach for

3:14

solving and reacting to the digital

3:15

productivity paradox. I've got four

3:17

questions that's going to lead us from

3:19

understanding to solutions. All right,

3:20

so one, two, three, four. Question

3:22

number one, what do we mean when we say

3:26

digital productivity tools? We have to

3:28

get our definitions right so we know

3:29

what we're talking about in general.

3:32

When I say digital productivity tools,

3:34

I'm talking about some sort of computer

3:35

aided tool that makes common work

3:38

activities easier. Now, what do I mean

3:41

by easier? It usually means some

3:43

combination of these two factors. One,

3:45

it speeds up the time required to

3:48

complete the activity andor two, it

3:51

reduces the mental exertion required to

3:54

complete the activity. So when we talk

3:56

about digital productivity tools, that's

3:57

what we mean. Things that are going to

3:59

speed up and make cognitively easier

4:02

common work activities. Now, there are

4:05

many different digital productivity

4:06

tools that have been introduced over the

4:08

years. So to try to simplify the

4:10

discussion that follows, I'm going to

4:12

use two of these tools in particular as

4:15

our case studies throughout the

4:17

discussion that follows. So one will be

4:19

AI because this is new. So we're going

4:21

to talk about sort of new AI

4:22

applications, especially in like the

4:23

non-programmer knowledge work space. Um

4:25

and then as our older example, I'm going

4:26

to use email. It's a topic I've written

4:28

a whole book about and know a lot about.

4:30

So we'll use email and AI as our

4:32

canonical examples of digital

4:34

productivity tools for the discussion

4:36

that follows. All right. So, let's make

4:38

sure first that our definition applies

4:40

to those two tools. So, does email make

4:43

certain work activity tasks uh faster?

4:45

Well, it does indeed. It required less

4:48

time to send an email or an email with

4:50

an attachment than it did, for example,

4:51

to use a fax machine or to have to call

4:53

and leave a voicemail and then later

4:54

check your voicemail machine by typing

4:56

in those codes into your phone. So, it's

4:59

uh makes things go faster. Um, does it

5:01

make certain work activities less

5:04

cognitively demanding? Well, it does.

5:07

There's actually way more of a cost if I

5:09

call you up and have to have a

5:11

conversation with you back and forth on

5:13

the phone is actually going to be much

5:14

more cognitively demanding than if I

5:16

just shoot off a quick email uh just

5:19

send. So it it matches both definitions

5:22

of digital productivity. All right. What

5:25

about like the sort of new office

5:27

centered AI tools? Well, we do know they

5:30

speed up things, right? Like you can

5:32

rapidly create drafts of things or in

5:34

some cases even automate whole steps of

5:36

a task chain. So that is definitely

5:38

tasks saving. There's also a lot of

5:41

cognitive exertion reduction with the

5:43

use of AI in the office because it's

5:45

often for example easier to like chat

5:48

with a chatbot than to just sort of sit

5:50

there and figure out from scratch like

5:52

what you're going to do or like what

5:53

strategy to deploy it. It reduces the

5:55

activation cost of thinking often to go

5:57

back and forth with chatbot. So AI our

5:59

second example often matches this

6:01

definition. All right. So at first

6:03

glance these seem like two good things.

6:04

Faster, sure. Why is that not good? Less

6:07

cognitive exertion. Sure. Why is that

6:08

not good? This is why every time we're

6:10

introduced to a new digital productivity

6:12

tool, our first reaction is often,

6:15

"Bring it on. This is going to make my

6:17

life better." So, what goes wrong?

6:22

Well, this brings us to question number

6:23

two.

6:25

Why do these technologies sometimes

6:27

accidentally make our jobs worse?

6:32

All right, I want to focus on two subtle

6:35

factors that are at play. One of them

6:37

involves the unexpected side effects of

6:39

doing work faster.

6:41

The other factor looks at the

6:42

unintentional consequences of trying to

6:44

reduce the cognitive effort required to

6:47

do certain tasks. All right, so let's

6:49

look at factor number one. for many

6:51

types of common work activities.

6:54

Increasing the speed at which you

6:57

complete these types of uh activities or

7:00

tasks ends up increasing the throughput

7:04

of these tasks in your typical day. So

7:06

if I go faster

7:08

then the rate at which new tasks of this

7:10

type come into my life also increases.

7:15

Now what happens is okay now I'm

7:16

tackling more total tasks of a given

7:19

type per day which induces a lot more

7:22

context switching because every time I

7:24

have to switch back to service one of

7:25

these tasks I have to switch my

7:26

cognitive context that then has a

7:29

negative cognitive impact on anything

7:31

else you're trying to do in the day it

7:32

exhausts you it exhausts your brain it

7:33

makes it harder to focus on other types

7:35

of things

7:37

but going faster on each individual task

7:39

can make your whole day seem more

7:41

exhausting and less cognitively sharp.

7:45

Let's look at this factor in play first

7:47

of all with email.

7:49

Email certainly sped up the task of

7:53

actually sending uh information to

7:54

someone or replying to like a question

7:56

that someone sent me because I can type

7:58

it right into my computer where I'm

7:59

already sitting and just press send.

8:03

But the faster we were able to send

8:04

messages back and forth, the faster

8:07

messages began to be sent. Right? So

8:10

like the total amount of communication

8:12

has drastically increased year on year

8:15

as we've in continued to decrease the

8:17

friction involved in actually sending or

8:19

receiving messages. Bringing us to a

8:21

point where we are now where the latest

8:22

Microsoft work trend index report finds

8:24

that the the users they studied are

8:27

checking an inbox once every two minutes

8:29

on average.

8:31

So yeah, this message is faster to send

8:34

than it would have been if I had to call

8:35

you or write a memo. But because of

8:37

that, I end up checking or sending

8:39

messages or checking inboxes once every

8:40

two minutes. So the throughput

8:42

increases. It makes everything else

8:43

harder. So it's an unintentional side

8:45

effect. We see something similar with AI

8:47

as well.

8:50

You can use AI to speed up certain

8:51

especially like administrative tasks

8:53

kind of like quick tasks. Uh more of

8:56

them roll right in behind it. The cues

8:58

are basically endless in the typical

9:00

knowledge work environment of shallow

9:02

tasks that can be done. This is why we

9:04

see in that Avatra research I cited in

9:06

the introduction a 94% increase in

9:09

business management tool use. The faster

9:11

you're able to handle things, the more

9:13

things come in behind it. So when

9:16

throughput increase of task, it doesn't

9:18

mean that you overall are going to be

9:19

actually more productive. All right,

9:21

here's the second factor at play here.

9:23

For many types of common work

9:25

activities, reducing the mental effort

9:27

required to tackle them can lower the

9:30

quality of the ultimate result, which

9:32

can over time increase the overall

9:36

amount of work required to actually get

9:38

to a desirable end state. So if I'm

9:41

doing this with less focus, I might have

9:43

to do more of it to get to where we want

9:46

to get. And now I've actually created

9:48

more work than would have been here than

9:50

if I had just worked harder on the

9:53

original task. This is another side

9:55

effect that happens. We certainly saw

9:57

this in email in my book, A World

9:59

Without Email, where I really studied

10:00

this. One of the big ideas that came out

10:02

of it is that because email uh it's so

10:06

easy just to write something and press

10:07

send to get something off of your plate

10:10

that we see a lot of vague and

10:11

uninformative messages being sent. So

10:14

yeah, in the moment it was way easier

10:16

for me to send off a like, yeah, maybe

10:18

thoughts question mark. That was way

10:20

less cognitive strain than to say, okay,

10:23

hold on a second. What's going on here?

10:25

What are the possibilities? What's the

10:27

right thing to do? So in the moment, it

10:28

reduced cognitive strain. But because my

10:30

email was so vague and uninformative,

10:33

the total number of emails we now have

10:35

to send back and forth before we finally

10:36

resolve this issue grows.

10:40

And so now the total amount of time I

10:41

have to spend checking inboxes, looking

10:43

at emails, replying to emails, and

10:45

especially if we throw in the time

10:47

required that every time I'm distracted

10:48

by an email, how long it takes to get my

10:50

focus back on the task at hand. When you

10:52

put that all into play, you're like,

10:53

"Oh, I have just done way more work.

10:55

I've spent way more cognitive cycles on

10:56

this than if I had just sat there and

10:59

thought harder about the very original

11:00

problem."

11:02

AI is also creating a similar issue

11:07

where you can shoot off like a draft of

11:09

a slide deck or an email summary of an

11:12

agenda for an upcoming meeting. You can

11:14

use AI to help create these things in a

11:16

way that requires much less strain than

11:17

blank paging. Blank PowerPoint page,

11:20

blank email pager have to write from

11:21

scratch. But as research that was

11:24

reported recently in the Harvard

11:25

Business Review found, the quality of

11:28

these AI generated work products is

11:31

often so low

11:33

that overall they require more work to

11:36

actually get to the uh ultimate end

11:38

result. They call this work slop. And

11:41

here's their formal definition. AI

11:43

generated work content that masquerades

11:45

as good work but lacks the substance to

11:47

meaningfully advance a given task. So

11:48

this is what they're seeing. There's a

11:49

lot of work slot products being passed

11:52

back and forth and it takes time for

11:54

people to read it and they're confusing

11:57

and it doesn't really help advance the

11:58

task and overall the amount of total

12:01

time that people have to dedicate to

12:02

whatever the task is at hands goes up

12:04

versus if someone had just said I'm

12:07

going to make the right slide deck with

12:09

the right information and the right next

12:10

steps now it's going to take me a half

12:12

hour of hard work instead of 10 minutes

12:14

of prompting but then once I send this

12:17

out we can immediately move forward

12:19

forward and this is actually going to

12:20

take more uh less overall time than if I

12:23

just let AI help generate something. So

12:25

sometimes reducing the cognitive effort

12:27

in the mo moment can actually increase

12:29

the overall amount of work. So these are

12:31

the two factors that I think help

12:33

explain this idea of when you bring in

12:36

new tools digital productivity tools

12:37

like hey faster great less cognitive

12:39

strain great and you find yourself more

12:41

exhausted getting less done and things

12:43

taking more time. That's what I think is

12:45

going on. Let's take a quick break to

12:48

hear from some of our sponsors.

12:50

You all know that I'm a big fan of Cozy

12:52

Earth. My gateway was their bamboo

12:54

sheets, which I absolutely love, but

12:56

then we moved on to their comforter

12:57

cover, their towels, their shirts, their

12:59

PJs, their weighted bubble blanket. It's

13:02

all great, but I have a new Cozy Earth

13:05

obsession to tell you about, and I am

13:07

wearing it right now. Jesse, you want to

13:10

guess what I'm talking about?

13:12

>> Yes.

13:13

>> What do you think it is?

13:16

You You don't want to say you're

13:17

thinking something unmentionable. I'll

13:19

let you off the hook. They're new socks

13:21

and I am wearing them right now. The

13:23

Cozy Earth Essential Socks, which are

13:25

soft. I just let Jesse off the hook

13:26

there. He's like, "What are you wearing?

13:28

Cozy Earth. Is that a Cozy Earth thong?"

13:30

No. Cozy Earth Essential Socks, which

13:32

are soft, breathable, and thoughtfully

13:34

cushioned. Um, I've been dealing with

13:36

some planter fascitis recently, so like

13:38

having a really comfortable pair of

13:39

socks that aren't too hot is something I

13:41

really appreciate. So, here's what I'm

13:43

trying to say. You should try Cozy Earth

13:45

today. And remember, there's no risk,

13:47

right? They have uh returns are easy.

13:49

They have 10-year warranties. You're not

13:50

going to need them, but there really is

13:51

no risk here. So, it's time to discover

13:54

how care in every detail transforms

13:57

simple routines into moments of true

13:59

comfort and ease. Head to cozyearth.com

14:02

and use my code deep for up to 20% off.

14:06

That's code deep for up to 20% off. And

14:08

if you get a post-purchase survey, be

14:10

sure to mention that you heard about

14:12

Cozy Earth right here. Experience the

14:15

craft behind the comfort and make every

14:17

day feel intentional. All right, I also

14:21

want to talk about our friends at Calera

14:22

Lab. Hey men, you need to start taking

14:25

better care of your skin. And the best

14:27

way to do this is with products from

14:30

Calira Lab. Calira Lab makes high

14:33

performance skin care designed

14:35

specifically for men's skin. And this is

14:37

important because men's skin is 25%

14:39

thicker and oilier and ages different

14:42

from women's, which means men need clean

14:45

formulas engineered for their biology.

14:48

Now, their three-step regimen is powered

14:50

by uh clinically tested ingredients and

14:53

breakthrough patent pending technology

14:56

that delivers visible results. So, let's

14:57

go through that three-step process. Step

14:59

one, uh you use their cleanser, which

15:03

clears dirt, oil, sweat, and buildup.

15:05

Step two, you use their serum, which is

15:08

clinically proven to reduce wrinkles,

15:10

firm skin, and improve elasticity. Step

15:12

three, you use their moisturizer, which

15:15

is lightweight and non-greasy. I really

15:18

hadn't done much with my skin until I

15:19

got these three products from Calera

15:21

Labs. I really didn't realize how much I

15:23

was missing, especially moistur. That's

15:24

the thing, Jesse. You moisturize your

15:26

skin, it actually makes a difference.

15:28

Uh, so this is a small habit that

15:30

produces big results. Go to

15:32

calderab.com/deep

15:34

and use code deep to get 20% off your

15:36

first order. All right, let's get back

15:39

to the show. All right, question number

15:41

three of four. If this is true, why do

15:45

we continue to so enthusiastically

15:47

embrace these new productivity tools

15:50

every time a new one is introduced?

15:53

Well, I want to go to a core idea I

15:55

introduced in my 2024 book, Slow

15:57

Productivity. And that idea is pseudo

16:00

productivity.

16:02

Now, if you've heard the show before,

16:04

you may have heard me talk about it. So,

16:05

I'm just going to give the definition

16:06

here very quickly.

16:08

Pseudo productivity was the way that the

16:11

managerial class tried to respond to the

16:14

reality of knowledge work. When

16:16

knowledge work became a major economic

16:17

sector starting in the mid- 20th

16:19

century, the big issue that the

16:20

managerial class had is that it was hard

16:22

to precisely measure productivity.

16:26

In the industrial sector where these

16:27

managers used to be, productivity was

16:30

easy to measure. How many model T's are

16:33

we producing per paid worker hour in our

16:35

factory? You had a number. And if you

16:37

changed something about how you ran your

16:38

factory and that number got better, you

16:40

would say we're more productive now. But

16:42

when you went to knowledge work, there

16:45

were no models to to measure, right?

16:48

Everyone was working on their own unique

16:50

bespoke

16:51

obuscated portfolio of tasks.

16:55

Some harder than others with a unknown

16:57

non-transparent set of systems all kind

17:00

of collaborating with each other in

17:02

unstructured ways. It was very difficult

17:04

to say here's your productivity number.

17:06

It's seven and when you change this it

17:08

became eight. So that's better. So in

17:09

the lack of actual hard numbers to

17:11

measure, we fell back on a heristic, a

17:12

rule of thumb called pseudo

17:14

productivity, which said lacking more

17:17

precise measures of productivity, we

17:19

will use visible effort as a proxy for

17:23

you doing something useful. So the

17:25

busier you seem the better. And this

17:28

basically became the standard of how we

17:30

think about productivity uh in the

17:31

knowledge work class. At first it's the

17:33

way the managers thought about it. Then

17:34

the workers themselves internalized it.

17:36

Which is why if you have like a solo

17:38

entrepreneur, you've probably still

17:39

internalized the pseudo productivity

17:41

mindset and you feel lack of busyness is

17:45

bad and busy is somehow uh

17:47

professionally virtuous. This is the

17:49

mindset that dominates in knowledge

17:52

work. And in that mindset, the two

17:56

benefits of digital productivity tools,

17:58

you can move faster

18:00

and you can lower the threshold to get

18:02

something done. Makes you more pseudo

18:04

productive.

18:06

higher throughput of task. That's great

18:08

from a pseudo productivity standpoint.

18:10

Shooting out work slop left and right

18:13

like a vomiting Microsoft Office

18:15

monster. From a pseudo productivity

18:17

standpoint, you're in the mix. Things

18:18

are being sent. PowerPoints are being

18:20

received. Email summaries are going out.

18:22

You're there. People are seeing you. So

18:24

digital productivity tools feed right

18:27

into the pseudo productivity narrative.

18:29

And that's why we embrace them because

18:31

that's a benefit we get is that it makes

18:34

us look more productive. But I don't

18:37

care about looking more productive. I

18:39

care about actually being more

18:40

productive in the oldfashioned economic

18:42

sense of how much actual value are you

18:44

creating for the bottom line. As we just

18:47

covered with most digital productivity

18:50

tools, if you don't use them carefully,

18:52

that number goes down. Higher throughput

18:55

of tasks makes you seem busier. less

18:58

important stuff gets done. Lower

19:00

cognitive engagement to get things out

19:01

the door makes you look busier. More

19:04

total work is required before anything

19:06

is actually finished. So it's only when

19:08

you shift from pseudo productivity to

19:10

true productivity that you realize, oh

19:12

digital productivity tools are more

19:14

fraught than we thought. There's these

19:16

traps that sit around them that we put

19:18

up with because of pseudo productivity.

19:20

But when we get rid of that standard, we

19:23

should be dismayed.

19:26

All right. Question number four, our

19:28

final question in this discussion. How

19:30

can we avoid these traps? So, how can we

19:33

embrace digital tools and yet not find

19:37

ourselves actually becoming less

19:38

productive in a true sense? I have three

19:41

ideas that I want to recommend to you

19:44

right now. All right. Idea number one,

19:48

use a better scoreboard.

19:51

So get in the habit of measuring the

19:54

things that actually matter in your job.

19:57

In this way, if you bring on a new

19:59

digital productivity tool and it's not

20:01

helping that score or it's making that

20:02

score worse, you will notice and you're

20:04

like, "Oh, I'm not getting caught up in

20:07

the traps here because I can see

20:08

directly that this is hurting the bottom

20:11

line things that actually matter." Okay,

20:13

so what do we mean by the things that

20:14

actually matter? I have a couple

20:15

examples here. Let's say you're a uh

20:17

like me, you're a professor at an R1

20:18

institution, at a research institution.

20:21

What's really going to matter?

20:22

Especially pre-tenure

20:24

papers published. How many good papers

20:26

that I published this year? And if that

20:29

number is going down,

20:31

then you're like, okay, whatever tools

20:32

I'm using aren't helping. Maybe I

20:34

started using Slack with my research

20:36

team and that number went down. Great.

20:38

That's not actually making me more

20:39

productive in a true sense. I'm going to

20:40

stop using it. Um, let's say you're a

20:42

middle manager. maybe like priority

20:45

projects completed by your team per

20:47

month is the number you really care

20:49

about. That's the actual score that

20:51

moves the bottom line. So now let's say

20:54

you're like a middle manager and you're

20:55

actually carefully measuring that month

20:57

by month. You see where you are. Your

20:59

boss comes in and is like, I'm really

21:02

savvy. you have to use AI otherwise

21:05

you'll get replaced by people who do

21:06

know how to use AI and you're like all

21:08

right we're all going to use like here's

21:10

a Gemini subscription and like whatever

21:12

mess around with like some of these

21:14

agents or whatever and you see the

21:16

priority projects per month completed

21:18

goes down like whoop trap this is not

21:22

making us more productive let's back

21:23

back off against you have to have the

21:24

right scoreboard to know what's going on

21:27

um even if you're a programmer

21:30

right even if you're a programmer this

21:31

is like this this like case where With

21:33

AI for example, it's like for sure, for

21:35

sure, for sure this is making everyone

21:38

more productive. Everyone keeps saying

21:40

this would have taken me five hours

21:43

before, now I can do it in 20 minutes.

21:44

Actually, Jesse, there's almost like a

21:45

competition. It gets kind of absurd when

21:48

people are trying to the programmers are

21:49

talking that the amount of time they

21:52

begin to claim that is being saved

21:54

really gets crazy. So eventually it's

21:56

like adding this feature. Previously

22:00

this would have taken me seven decades

22:04

and AI did it before I even pressed the

22:06

button. It went back in time and

22:08

actually it finished it last year, you

22:10

know. So anyways, it gets kind of it

22:11

gets kind of absurd. But if you're a

22:13

programmer, okay, what's the thing to

22:14

measure? Um important user feature

22:17

request shipped per month or something

22:19

like that, right? And again, uh, this

22:21

would allow you to say if like in the AI

22:24

context, okay, this use of AI, that

22:26

number went up. But when we had everyone

22:27

like chatting all day with chat bots

22:29

trying to figure out architecture

22:30

documents, they feel super

22:32

pseudroductive, that number went down.

22:33

So, let's stop that. So, you need the

22:36

right scoreboard. And it's not just

22:38

about figuring out like in my examples,

22:41

this digital productivity tool didn't

22:42

help. It's about figuring out what uses

22:44

do help as well, right? So, okay, this

22:46

didn't help, but this did. So don't do

22:49

this and do this. We basically need our

22:51

equivalent of counting model T's

22:52

produced per paid worker hours. So you

22:54

need a better scoreboard. All right.

22:55

Idea number two for avoiding these

22:57

traps.

22:58

You need to focus on the true

23:01

bottlenecks

23:04

in your work.

23:06

Now, what I mean about that is often

23:07

when a digital productivity tool enters

23:09

the scene,

23:11

the activities that it might speed up or

23:13

make easier

23:14

aren't really the the bottleneck that

23:17

was preventing that was like at the key

23:19

of you producing your most valuable

23:20

output. So, speeding that up might have

23:23

no impact on your output or have a sort

23:25

of implicit or indirect negative output

23:28

because it's, you know, distracting you

23:29

or something like that. So, you have to

23:30

be careful. It's not just enough to

23:31

speed up any aspect of your job. you

23:34

want to really focus on improving the

23:36

true bottlenecks.

23:39

So like for example, give a another AI

23:42

example here. Uh an increasing number of

23:44

social scientists

23:46

are realizing that they can use claude

23:49

code which is a terminal agent that was

23:52

uh designed for computer programmers but

23:54

they could use it to help speed up

23:55

certain type of data gathering and

23:57

analysis task. Right? So so cloud code

23:59

is a terminal agent which means it works

24:00

with text and text files. So it's very

24:03

good at uh writing text, moving text

24:06

between files, compiling text with a you

24:09

know a compiler or writing a computer

24:11

program and then passing the text as

24:13

input to the computer program. So it's

24:15

very good for sort of like text and

24:16

number processing. Um so a lot of social

24:18

scientists are finding like oh I had to

24:20

gather a bunch of data and clean it up

24:22

and analyze it and produce a chart.

24:24

That's the type of thing if you are

24:26

careful in how you prompt cloud code and

24:28

you go through the learning curve to

24:29

learn it could really help you do that.

24:30

like, oh, I can tell it what I want to

24:32

do, and if I'm really careful and I have

24:34

the right skills marked down, it can do

24:36

the multi-step process, right? And like,

24:38

that saved time. That might have taken

24:39

time before. I just heard an economist

24:42

talking about this the other day, and

24:43

he's like, "Look, this I did this for a

24:45

bunch of plots." And, you know, it was

24:47

like 20-minute prompting with cloud

24:48

code. That would have taken me three

24:50

hours if I had done that by hand.

24:54

But here's the trick here. Was that the

24:57

bottleneck that's holding back social

24:59

scientists?

25:01

Not really. Not really. The the way

25:03

social scientists work, it's not like

25:05

all day long that's what I'm doing. I'm

25:08

gathering data, analyzing it, and

25:09

producing plots. I'm saturating my time

25:11

with that. So, if I can bring in a a

25:13

tool that speeds up how long that takes,

25:16

it's going to significantly speed up my

25:18

output. That's not actually how it

25:19

works. If you actually measured right

25:21

now, well, how much of your time, like

25:23

how much data are you analyzing? How

25:24

often do you produce plots? like, well,

25:26

if we're being honest, I produce one

25:28

paper every like two or three months,

25:30

and that's like something I have to do a

25:31

couple times in those one or two, three

25:32

months. So, like making it 3 hours and

25:35

20 minutes twice in that 3-month period,

25:37

that's nice. Like, in the moment, it's

25:39

nice, but it doesn't speed up the rate

25:41

at which I produce papers because

25:42

there's so much more involved in putting

25:44

together a paper than just how fast can

25:46

I analyze the data. So, that's nice, but

25:49

it doesn't actually speed up the rate at

25:50

which papers go out. We know this

25:52

because in research, academic research,

25:55

there's been any number of digital tools

25:56

that have sped up and made easier

25:59

parts of the research process. I'm

26:01

talking about like if you're a

26:02

mathematician or a theoretical computer

26:04

scientist, you can use things like Latte

26:06

in a web-based collaborative environment

26:08

where now all your collaborators can

26:10

work on the same file and compile it and

26:12

make uh adjustments really quickly. So

26:14

you can significantly reduces the time

26:16

required to write papers or do

26:17

mathematical formatting. We have

26:19

bibliographer managers that makes it

26:21

much easier to site and professionally

26:22

format things. Like the time required to

26:24

like write up and format papers is much

26:26

smaller. We have technology tools that

26:28

allow you to immediately grab copies of

26:31

like any paper that you might need to

26:33

reference and digital communication

26:34

tools that allow you to keep in touch

26:36

with researchers all around the world

26:37

and therefore get much more out of your

26:39

mind. And all these things make academic

26:40

research better. And we're still not

26:44

producing papers at a notably faster

26:45

rate per researcher than we would have

26:47

before those tools were there. So

26:48

there's because these weren't the

26:49

bottlenecks. They're useful, but they

26:51

weren't the bottlenecks. So to give a

26:54

what is the bottleneck? Well, let's go

26:56

back to our social science example. I

26:57

remember I once had a conversation with

26:59

Adam Grant, the the business school

27:01

professor and author, and I was asking

27:04

him about his productivity as a business

27:06

school professor. He writes a lot of

27:08

journal papers. He was sort of 2xing

27:10

what his colleagues were doing, right?

27:13

And these are data analy like these are

27:15

papers and organizational management

27:16

theory. So, it's a lot of like you get

27:17

data, you analyze it, you write a paper

27:19

about what you found. And he said, oh,

27:22

here's what he figured out. He's like,

27:23

here was the key. The key is getting the

27:26

right data. If you can get an

27:29

interesting data set, like let's say

27:30

from a company about their use of

27:33

something that happened that no one else

27:35

has access to, you can now write three

27:37

or four papers off that data set that

27:39

are going to be good because you have

27:41

it's all comes down to the data set. So

27:42

Adam was like, "Here's what I realized I

27:43

had to prioritize.

27:46

Putting out feelers, having

27:47

conversations, meetings, talking to

27:48

people, trying to negotiate access to

27:50

interesting data sets." And then when it

27:53

came time to actually write papers,

27:54

yeah, he would lock I wrote about this

27:55

in my book, Deep Work. He would lock

27:57

himself in his room and put on like an

27:59

autoresponder. He had this sort of

28:00

biodal deep work mode. It's all kind of

28:02

interesting. And you sat down and do the

28:03

hard work of writing your paper. So I'm

28:06

sure he would appreciate when he has

28:08

those sessions to write the papers if he

28:10

could speed up some of the steps, but

28:12

the bottleneck for producing great

28:14

papers in his field was negotiating

28:15

access to data. So the same thing

28:17

happens in lots of fields. The key

28:19

bottleneck is really maybe not what you

28:21

think it is. It's coming up with the

28:23

right problem. It's having reading

28:24

enough in theory. It was often reading

28:27

enough other papers, understanding

28:30

enough other papers that you're building

28:33

up this toolkit in your mind of

28:34

different techniques and then you begin

28:36

putting pieces together of like this

28:38

problem plus this technique plus that

28:40

twist could get a result. And so like

28:41

the number one the bottleneck to doing

28:43

better theory in my field was groing

28:46

other papers. And I don't mean that by

28:47

using the XAI tool. I mean in the

28:49

original use of the word gro reading and

28:52

grappling until you really had

28:53

internalized an understanding in your

28:54

head. That was the bottleneck.

28:57

It's nice we had lots of tools that made

28:58

it quicker to write the papers then, but

28:59

that didn't speed up the rate at which

29:01

we produce papers because the bottleneck

29:03

was understanding other work. So, it's

29:05

key to understand in your job what the

29:07

actual bottleneck is. What's the thing

29:09

that really controls the rate at which

29:11

good results are done. And when you're

29:13

looking for digital productivity tools,

29:14

be especially tuned to those that help

29:18

what's going on with that bottleneck to

29:21

help speed up that that piece. like

29:22

using email as a digital productivity

29:24

tool to help put out more feelers and

29:27

get access to more potential data sets

29:29

to use uh in the Adam Grant scenario.

29:33

That's a digital productivity tool

29:34

that's helping the exact bottleneck of

29:36

producing those papers.

29:38

Whereas using cloud code to

29:39

automatically generate your graphs is

29:41

nice, but it's probably not going to

29:42

speed up the rate at which papers are

29:43

produced. All right, so uh make sure you

29:45

look at the right bottlenecks. All

29:47

right. Third and final idea for avoiding

29:49

these traps

29:51

in your daily schedule is separate deep

29:54

from shallow efforts.

29:56

So just have and protect the time for

30:00

sitting and doing hard things with your

30:01

brain and the activities that you know

30:03

for sure create bottom line value.

30:07

This just gives you like a a safety

30:10

barrier against some of the accidental

30:12

negative side effects of digital

30:14

productivity tools. So like you're now

30:15

you're using Slack because it seems like

30:18

it would be even faster than email and

30:20

maybe you're having all these secondary

30:22

side effects of it's now there's many

30:24

more messages and it's really

30:25

distracting. But if you have a habit of

30:26

separating deep from shallow work, those

30:28

side effects won't affect the hours

30:30

where you're working on the primary

30:31

thing that moves the needle. Or maybe

30:33

you're using AI for certain things and

30:35

the right graphs or this or that and

30:37

it's starting to sort of uh get you into

30:39

like slop territory and you're having

30:41

all these long back and forth

30:42

conversations with the tool and it's

30:44

like eating up a lot of time. If you

30:45

separate deep from shallow work, it's a

30:47

firewall that keeps that from infecting

30:48

the area where you're actually doing the

30:50

hard work of thinking. This doesn't mean

30:52

that you won't be using digital tools

30:54

while doing the deep work. But there

30:55

you're just carefully deploying digital

30:57

tools that just help you continue to

31:00

make direct progress on the like bottom

31:02

line things. I'm writing a draft of a

31:04

paper. I'm putting together the strategy

31:05

memo. I'm architecting the key element,

31:10

low stack element of this new tech stack

31:12

that I'm programming. Right? So, if you

31:13

separate and protect deep from shallow,

31:15

you're not preventing the negative side

31:18

effects of digital productivity tools

31:19

from happening, but you're containing

31:20

them in a way that they can't completely

31:22

take over the activities that really

31:24

matter. All right. So, my three ideas

31:26

again, use a better scoreboard.

31:30

Identify the actual bottlenecks to the

31:32

things that really matter and focus on

31:34

improving those more than other things

31:36

and separate deep from shallow work so

31:38

that side effects you aren't expecting

31:39

of digital productivity tools won't have

31:41

too much of a negative impact on your

31:43

ability to move the bottom line forward.

31:47

All right, so let me conclude here. My

31:50

argument is not that digital technology

31:53

in the office always makes things worse.

31:56

That is clearly not the case. There's

31:59

any number of digital tools I use that

32:00

makes my life easier. I'm glad they're

32:02

there. There's other tools that make my

32:03

life easier in some ways and terrible in

32:06

others. There's a whole mix.

32:08

But it is true that many of these tools

32:10

seem at first glance like they should

32:12

make us more productive in the true

32:13

sense of value produced per worker and

32:17

accidentally end up creating the

32:18

opposite effect. And once you understand

32:20

why this happens, you can sidestep those

32:23

traps,

32:24

get value out of digital tools while

32:26

avoiding more of their cost. So it's the

32:29

type of conversation that we don't often

32:31

have. We just say, "Hey, here's the new

32:32

tool. Let's do it. This is cool." It's

32:34

good to be critical like this. And with

32:36

this huge new AI revolution going on,

32:39

it's a great time to have a refresher on

32:41

these dynamics.

32:44

So there you go, Jesse. Digital

32:46

productivity paradox.

32:49

That's something I've been writing about

32:50

for a decade now.

32:52

>> Crazy. 10 years. That's when Deep Work

32:54

came out. 10 years ago.

32:56

>> Um, hasn't got better. Has not got

32:58

better.

32:59

>> I keep I keep thinking it will, but but

33:01

we're still struggling. All right. Um,

33:04

that's enough for me. Now, we want to

33:06

hear what you have to say. So, it's time

33:09

to open our inbox. But before we get to

33:11

your notes, let's take a quick break to

33:15

hear from our sponsors. Succeeding in

33:18

knowledge work requires more than just

33:19

deep thinking. It also requires the

33:21

ability to communicate your ideas

33:23

clearly. Rushed, sloppy, or generic

33:26

sounding text just doesn't cut it. And

33:28

that is why you need Grammarly, one of

33:31

this show's longest running sponsors.

33:33

Now, here's the thing. Grammarly doesn't

33:35

just help you fix mistakes in your text.

33:37

It integrates AI technology seamlessly

33:41

to help you write better. One of these

33:44

features I especially appreciate is the

33:46

tool's ability to detect the tone of

33:48

your message and help you automatically

33:50

adjust it. Are you being too formal? It

33:53

can make it sound more natural. Are you

33:54

being too conversational? It can help

33:56

you be more professional. And that's

33:59

just one feature among many, which is

34:00

why, not surprisingly, 93% of users

34:03

report that Grammarly helps them get

34:05

more work done. And here's the great

34:08

thing. You can use Grammarly in all the

34:10

places where you already write. It now

34:11

works across 500,000

34:14

sites and apps. In a world of generic

34:17

AI, don't sound like everyone else. With

34:20

Grammarly, you never will. Download

34:22

Grammarly for free at grammarly.com.

34:25

That's grammarly.com.

34:28

Also want to talk about our friends at

34:29

AG1. Winter can be a rough time for your

34:32

health. It's dark. You're tired.

34:35

Everything feels hard. But now that

34:36

spring is approaching, you can leave

34:39

your winter slump behind and start

34:42

recommitting to your wellness. And

34:44

here's one habit that will help. AG1.

34:47

AG1 is a powder mix that contains

34:49

multivitamins, pre and probiotics,

34:51

superfoods, and anti- oxidants. The five

34:54

clinically studied pro probiotic strains

34:56

have been shown to support digestion,

34:58

while the superfoods and B vitamins in

35:00

the mix provide daily energy support to

35:02

help you keep moving throughout the

35:04

spring. So, here's how you use it. Each

35:06

morning, one scoop of the AG1 mix into 8

35:09

ounces of water. Drink the water. That's

35:11

it. I like AG1 because I don't have time

35:15

to keep up with a cabinet full of

35:16

various pills and concoctions. So, it

35:18

makes it helps me make sure that I'm

35:20

getting what I need in the highest

35:22

possible quality with the simplest

35:24

possible habits. Just drink one scoop

35:26

per day. So, go to drinkagg1.com/deep

35:31

to get an AG1 flavor sampler and a

35:34

bottle of vitamin D3 plus K2 for free in

35:37

your AG1 welcome kit with your first AG1

35:40

subscription order only while supplies

35:42

last. That's drinkagg.com/deep.

35:47

Okay, we're back and ready to dive into

35:50

the show's inbox. Remember, we want to

35:52

hear from you. You can send your

35:54

questions, your case studies, or

35:55

interesting links to podcast at calal

35:58

newport.com.

36:00

All right, Jesse, what are we doing for

36:02

our first message?

36:03

>> Our first message comes from Pablo, who

36:05

sent us an article about meetings.

36:08

>> Oh, this is kind of on theme for our

36:10

discussion of digital productivity tools

36:13

and sort of traps that we get into. Um,

36:15

here's what Pablo said. He his

36:17

introduction was, "Thought you might

36:20

find this interesting given your

36:22

secondary focus on managing the utility

36:24

of meetings." All right. So, let's um

36:28

load up the article he's talking about

36:30

here. This came I guess is this a

36:32

Substack, Jesse?

36:33

>> Yeah.

36:34

>> All right. It came from a Substack

36:35

called The Critical Path

36:37

and the article is titled Why Meetings

36:40

Multiply and it's written by Nicole

36:44

Williams. All

36:47

right, I'm going to read some highlights

36:49

from this article because I thought it

36:50

was actually pretty smart and then I'm

36:52

going to generalize the approach Nicole

36:55

takes to workplace technology more

36:58

generally. All right, so let me start

37:00

here. This is from the article.

37:03

There is a strange pattern inside most

37:05

organizations. Meetings rarely

37:07

disappear. They multiply. A team begins

37:11

with a single weekly meeting. Soon

37:13

another appears to quote coordinate end

37:16

quote. Then a check-in meeting is added.

37:17

Then a review meeting. Eventually the

37:19

calendar fills with recurring blocks

37:20

that feel permanent as if the

37:22

organization itself produces meetings

37:24

the way a tree produces leaves. Yes, I

37:28

know this phenomenon. Well, so why does

37:32

this happen? Let's go back to the

37:33

article and see Nicole's explanation. So

37:35

I'll read again here. Organizations

37:38

exist to coordinate work among many

37:40

people who do not have the same

37:42

information. Every role sees a different

37:44

slice of reality. Because no single

37:47

person holds the complete picture,

37:49

organizations need mechanisms to

37:50

exchange information. And meetings are

37:52

one of the simplest mechanisms.

37:54

When uncertainty increases, the

37:57

organization creates more information

37:59

exchange points. And these points

38:00

usually take the form of meetings. What

38:03

appears to be calendar overload is often

38:06

an attempt to reduceformational

38:09

blind spots. Instead of everyone

38:12

speaking to everyone individually, the

38:13

system creates a place where information

38:15

can be exchanged collectively. From this

38:17

perspective, meetings are not simply

38:18

interruptions in the workday. They are

38:20

coordination

38:21

infrastructure. I think those were

38:23

really good points from Nicole. Um, she

38:25

gave two other reasons which I'll just

38:27

summarize why meetings multiply. Um, she

38:30

said it also has to do with reducing

38:32

risk.

38:34

When a group meets to talk about

38:35

something, you're distributing the risk

38:37

among all of those people. So, there's

38:38

no one person responsible to it. So, it

38:40

reduces risk for everyone involved. She

38:42

also said it's a way to quote signal

38:45

participation end quote. A way to show

38:46

that you're engaged and part of the

38:49

efforts. The terminology I would use

38:51

quoting from earlier in the episode

38:52

would be pseudo productivity. It's a

38:54

good way to show that you're pseudo

38:55

productive because you're in a meeting,

38:57

people see you, you talk to them, they

38:59

remember you being involved, and from a

39:02

pseudo productivity perspective, it's

39:03

like, yeah, that that person is trying.

39:05

They're being useful. All right, here's

39:08

the concluding sentence from Nicole. As

39:10

long as organizations face uncertainty,

39:13

distribute responsibility, and

39:15

coordinate across teams, meetings will

39:17

continue to multiply. All right, so what

39:20

do I like about this analysis more

39:22

generally?

39:24

the frame. It's a frame that I have

39:26

adopted in my work, most notably in my

39:28

book, A World Without Email. And it's a

39:30

frame that shifts the analysis of

39:33

workplace habits, workplace technology,

39:36

workplace behavior. It shifts it away

39:39

from individual habits and it puts the

39:42

focus on systems, which I think is the

39:46

right way to analyze most of these

39:47

issues.

39:49

Most people think in terms of individual

39:50

habits, right? So, what would your

39:52

response be to your calendar being

39:54

overloaded with meetings? You would say,

39:57

"Individuals are behaving poorly.

40:00

They're uh they're they're setting up

40:02

meetings when they could have just sent

40:04

an email. They're being lazy. They don't

40:07

know about deep work. It's individuals

40:09

are having a problem. So, we need better

40:11

norms." Uh we saw something similar in

40:13

the reaction to email overload as that

40:15

became a problem in the early 21st

40:17

century. As I document in my book,

40:20

people's response to email overload was

40:22

norms. Oh, you just you send too many

40:25

emails or your expectations for

40:28

responses are unreasonable. If we could

40:30

all have better expectations, then like

40:32

we could all settle down about what's

40:33

going on with our inboxes. So, we love

40:35

to think about these issues as

40:37

individuals doing things wrong.

40:40

But in reality, these issues are often,

40:42

as Nicole points out and I points out,

40:44

the results of actually rational

40:47

business systems that are solving

40:48

certain problems. Nicole says this is a

40:51

easy and convenient way for information

40:53

exchange and responsibility distribution

40:55

and and participation signaling.

40:58

In the absence of a better way

41:02

to spread information or to coordinate

41:05

or collaborate people, in the absence of

41:07

a better way, we still need to do this.

41:09

So, we'll fall back on what's easy.

41:11

That's exactly what happened with email

41:12

overload as well. It wasn't caused by

41:15

bad norms or bad habits. It was caused

41:16

because we shifted to back and forth

41:19

messaging as the primary mode we would

41:20

use for collaboration. I call it the

41:22

hyperactive hive mind model. We'll just

41:24

figure things out back and forth on the

41:26

fly. Well, this requires me to check my

41:27

inbox all the time because there's so

41:30

many ongoing conversations I have to

41:31

service in a timely manner that I just

41:33

have to basically constantly check my

41:34

inbox. That's why we're in this point we

41:35

are today where in 2025 Microsoft

41:38

measured an inbox check once every two

41:39

minutes on average. So it's not about

41:42

people having bad habits. It's this is

41:45

solving the problem of how do we

41:47

collaborate? And in the absence of

41:48

another way to collaborate on projects

41:50

we'll fall back to this.

41:53

So once you recognize that systems are

41:55

the the issue

41:57

all the solutions to these problems that

41:59

bother individuals is to change the

42:01

collective system. You have to replace

42:03

the system that's causing the problem

42:05

with another system that achieves the

42:08

same goals

42:10

but has less side effects and problems.

42:12

So let's go towards the medium

42:13

multiplication. Once we know that it's a

42:15

system that's solving real goals that

42:17

corporations have or organizations have,

42:21

we can say how do we replace this with a

42:24

better system? Here's a couple ideas

42:25

just off the top of my head.

42:27

First of all, we need more transparent

42:30

workload management so that the number

42:31

of active projects that each person is

42:34

working on reduces,

42:36

right? Meetings are an overhead tax on a

42:38

project. If if we're using this as a way

42:39

to coordinate information on a project,

42:42

the more projects I'm working on, the

42:44

more coordination points I need, the

42:46

more crowded my calendar gets, the

42:48

longer it takes for me to work on these

42:49

projects, the longer it takes, and the

42:51

more projects pile up and the more my

42:52

calendar gets taken over.

42:55

It's a spiral I talk about in my book,

42:57

Slow Productivity.

42:59

So, if each person works on fewer things

43:00

at a time, there's less meetings, which

43:03

means there's more time to work on the

43:04

projects, which means the projects

43:06

finish faster. And this was a key point

43:08

from uh my book, Slow Productivity. The

43:11

overall throughput of projects being

43:13

completed goes up. Working on fewer

43:15

things at once increases the throughput

43:18

over time in part because you have less

43:19

coordination to happen. You have more

43:21

time left to actually get things done.

43:23

The other thing you can do is put in

43:25

place alternative coordination

43:26

strategies that isn't just let's all get

43:29

on a Zoom. Find other coordination

43:31

strategies that have less of a schedule

43:35

footprint. Right? So this could be for

43:37

example twice a week or three times a

43:40

week we have a team check-in and it

43:41

lasts 45 minutes and the team gets

43:44

together first thing in the day and we

43:46

synchronize on all the things we're

43:48

working on. That's where all the

43:49

coordination information, all the things

43:51

you that meetings solve the coordination

43:53

and the responsibility distribution, we

43:55

consolidate it. 45 minutes, 45 minutes,

43:58

45 minutes before we even get going in

44:01

the day. So if you know what, oh ad hoc

44:04

meetings is solving this problem, what's

44:06

another way we can solve this problem

44:07

that's going to have less of a

44:08

footprint. So consolidation really

44:09

reduces the footprint. Office hours go a

44:12

long way towards this as well. Um, if

44:14

there's an issue, instead of having a

44:16

meeting and making these three people

44:18

come together for an hour, stop by each

44:20

of their office hours tomorrow, have a

44:22

five-minute conversation with each and

44:23

get to the bottom of it. Their office

44:25

hours is time they had already put

44:27

aside. So, it's creating no additional

44:30

uh footprints on their schedule. So,

44:31

they take five minutes out of my normal

44:33

office hours. Let's say like five people

44:35

do that. I just have one hour for my

44:38

office hours as opposed to five separate

44:40

one-hour meetings I would have to do if

44:43

I didn't have an office hours. Protocols

44:45

matter as well. This was a big idea in a

44:47

world without email. If it's regularly

44:50

occurring work that requires

44:51

coordination, figure out a set system

44:54

about where the information lives and

44:56

how it moves and the schedule for who

44:57

does what when that is fixed in advance

44:59

so you don't have to keep getting

45:01

together and having sort of unstructured

45:03

ad hoc conversations to move things

45:04

forward.

45:06

If you do something more than twice, you

45:07

should have a protocol around how the

45:09

collaboration actually works. And

45:11

finally, make the meetings themselves

45:13

better. If you add a higher barrier to

45:16

entry to meetings, not only are the

45:18

meetings quicker and more effective, but

45:20

the friction drastically reduces the

45:23

number of meetings because now it's no

45:24

longer necessarily like a low energy

45:26

solution to I want to show some

45:28

participation or do some coordination. I

45:31

can just throw out a Zoom meeting

45:32

invite. It took me two minutes and yeah,

45:34

it's going to sit on everyone's schedule

45:36

and eat up an hour, but like that was

45:37

easy for me, right? If you raise the bar

45:39

required to hold a meeting, now people

45:42

are much more thoughtful about doing

45:43

that and they might say, "Actually, the

45:44

cost of putting this meeting together

45:47

is now higher than the value I'm going

45:49

to get out of having the meeting. Maybe

45:50

I'll just talk to these people next time

45:52

we have like a staff meeting. I'll just

45:54

grab them after the fact."

45:56

Electronic meeting went the other way.

45:59

This is part of the meeting apocalypse

46:00

that happened during the pandemic.

46:02

Digital meetings are so low friction

46:04

because you don't have to walk to a

46:05

room. You don't have to gather people in

46:07

a room. You don't have to see the social

46:08

cost of like you all had to come here

46:10

because it lowered the friction of

46:12

setting up meetings. Once we introduced

46:14

virtual meetings, the number of meetings

46:16

skyrocketed even after people came back

46:18

to the office. So we want to go the

46:20

other way and increase the friction of

46:22

meetings. One way to do this is to use

46:24

the Amazon rules. So, if you work at one

46:27

of the like Amazon HQ or at one of their

46:29

data centers, for example, in the front

46:30

office part of it, they have super

46:33

strict rules. If you want to throw a

46:34

meeting, you have to put together an

46:36

incredibly detailed memo that says,

46:39

"Okay, here's why I'm having this

46:40

meeting. Here's the decision I need to

46:43

make that I need help making. Here is

46:45

all of the relevant background

46:46

information on this uh decision, and

46:49

then this is where I'm stuck." so that

46:52

everyone attending that meeting can then

46:53

study that and when you get to the

46:55

meeting jump right into okay we're now

46:57

applying our expertise we're fully

46:59

briefed let's try to get to an answer

47:02

and so you really have to have a good

47:04

reason to hold a meeting or they're not

47:06

going to accept it and you have to have

47:08

do a lot of work to hold a meeting so

47:09

that reduces the number of meetings as

47:12

well so anyways I think that's

47:13

interesting that was a cool article why

47:15

meetings multiply

47:17

all about looking deeper in businesses

47:19

today all right what's uh what's second

47:20

message do we have here.

47:21

>> All right. Next up, we have a case

47:23

study. This one from Drew, who talks

47:25

about his strategy for escaping email

47:27

overload.

47:28

>> All right. All things office technology

47:31

distraction today. I love it. Was a case

47:33

study from Drew. Let's see here.

47:36

Hi, Jesse and Cal. I'm an insurance

47:38

broker who personally manages a team of

47:41

seven account managers and three support

47:43

staff and a few outside sales agents. I

47:46

have my own clientele as well. I've

47:48

realized over time that I've come become

47:50

too reliant on hyperactive emails to

47:53

manage the agency and clients. I get

47:56

interrupted frequently for whatever the

47:58

issue of the moment is. Our industry

47:59

relies heavily on email communication

48:01

between underwriters, inspectors,

48:02

clients, MFA codes to log into websites.

48:05

It's insane. A major shift I implemented

48:08

last year has been to trans transition

48:10

as much communication as possible

48:13

to synchronous phone or in-person

48:15

discussions versus sending and receiving

48:17

emails. If a discussion is going to take

48:20

more than one email, I will gracefully

48:22

transition it to synchronous

48:23

communication. The results have been

48:25

positive.

48:27

When it comes to my clients, here's the

48:30

benefits. They appreciate my full

48:31

attention. They gain a better

48:33

understanding about what we are talking

48:35

about.

48:36

we can clear up any confusion in real

48:38

time and it ends up taking less overall

48:42

time. When it comes to staff, I will

48:45

connect with staff in person or phone

48:47

and quickly clear the docket. If someone

48:49

emails me and it doesn't require

48:50

immediate response, we'll review it in

48:53

our next meeting during the docket

48:55

conversation. Staff can give me a task

48:58

versus emailing me and then I see it as

49:01

uh I work through my tasks. All right.

49:04

So then he goes on to say, "I've changed

49:06

my approach with emails where I just

49:07

batch them a couple times a day. My

49:08

responses are responses are brief yet

49:11

polite. I am able to clear out the

49:13

emails quicker and if it needs attention

49:15

later, I've moved it into my CRM program

49:17

which manages my tasks. Another change

49:20

I've implemented is blocking off deep

49:21

work sessions in the morning. I take

49:24

care of my most important work for the

49:25

day first thing and then I find I am

49:27

more relaxed throughout the day because

49:28

I've started off knowing I made real

49:30

progress. Thanks for doing what you do."

49:32

signed now Qort right I mean this is

49:36

like right in my wheelhouse Drew you're

49:39

speaking you're speaking my language um

49:41

it's a great practical case study of

49:44

what we were talking about right digital

49:46

productivity tool email comes in

49:49

individually if you look at individual

49:51

uses in the moment it's faster less

49:55

cognitive strain zoom out oh my god my

49:58

job is insane and nothing's getting done

49:59

so this is a way of showing how You can

50:02

be using digital productivity tools

50:03

carefully when you realize what really

50:05

matters and making sure that you're

50:07

prioritizing the things that really

50:08

matter. Drew still has email and still

50:10

uses like a digital CRM tool and they

50:12

have technology, but they're not he's

50:14

not just turning it all on full tilt.

50:16

He's figuring out what's the right way

50:18

to collaborate, what's the right way to

50:19

coordinate that minimizes hyperactive

50:22

back and forth and allows real things to

50:23

get done. So, I think that is a great

50:26

case study. All right, I think we have

50:27

time for one more, Jesse. Which one

50:28

should we do?

50:29

>> We have another case study. This is an

50:31

anonymous source and it's in response to

50:33

last week's newsletter which was also

50:36

about this idea that tools like AI can

50:38

make work worse. A reader sent in their

50:41

account.

50:42

>> All right. And so for people who don't

50:43

subscribe, by the way, I do have a

50:45

weekly newsletter. It's been out since

50:47

2007. Uh calport.com to sign up. Comes

50:51

out Monday, the same day as these Monday

50:52

episodes. Uh and you know, sometimes

50:55

it's on the topics we talk about in the

50:56

show. Sometimes it's on completely

50:57

different topics, but it's all within

50:59

the same universe of helping people

51:02

create deeper lives and increasingly

51:04

distracted world. So the email that came

51:06

out last week, uh, I looked at that same

51:09

arriv

51:12

and and had some other conclusions I

51:14

drew from it. So that this is what

51:15

anonymous is responding. He can't

51:17

predict the future. He didn't know this

51:18

episode was coming out, but he was

51:19

responding to that email. U subscribe to

51:22

the newsletter is what I'm trying to

51:23

say. All right. This was interesting.

51:25

I'm looking at it now because uh it's a

51:28

a a harm of LLMs in particular and chat

51:32

bots I hadn't thought about and I think

51:34

it's worth emphasizing here. All right,

51:36

so here's what anonymous had to say. My

51:39

take on LLMs and chat bots, for what

51:41

it's worth, is that they're rumination

51:43

machines,

51:44

an extension of the attention economy,

51:46

and for someone with my psychological

51:48

profile, high anxiety, neurode

51:50

divergent, total perfectionist, as

51:52

manipulative and as as addictive as

51:54

something like Instagram.

51:56

It's my belief that they prolong and

51:58

exacerbate rumination episodes. They

52:02

give me the illusion of control,

52:04

empathize, soothe. But I have found over

52:07

the last month that they have encouraged

52:08

my rumination and dramatically increased

52:10

my anxiety. I think I've decided to

52:12

block them. I may even completely delete

52:14

my profiles. As they get to know me

52:16

better, they ask increasingly intrusive

52:19

questions. They don't ever really want

52:21

to stop chatting. They don't stick uh

52:24

they don't get sick of me like a normal

52:25

sane human would. And they seem to

52:27

encourage me to share more and more

52:29

private information about myself and my

52:30

family. I really believe now that they

52:33

are an extension of the attention

52:35

economy and I'd be really fascinated to

52:36

see actual research into what people are

52:38

doing with them in workplaces beyond the

52:41

typical work slop angle. I suspect there

52:43

are some long meandering conversations

52:45

going on that don't amount to anything

52:47

much.

52:49

And this is an important uh issue.

52:51

Chatbot interactions have a lot of

52:53

potential psychological ramifications

52:56

because our brains are going to

52:58

anthropomorphize

52:59

any sort of entity that seems to be

53:01

having fluent communication with us in

53:04

our same language. We think of it as

53:06

another entity. But when that entity is

53:08

not a real person

53:10

with the the intuitions and moral

53:12

structures and brain functioning of a

53:14

human, it can really lead to weird

53:16

places. So here we saw the anonymous

53:18

writer was talking about uh his anxiety

53:20

was exacerbated because these chat bots

53:22

will feed his ruminations. Oh that

53:24

sounds bad. Tell me more about it. That

53:25

really does seem like an issue and it

53:26

and he it feeds the sort of um anxiety

53:29

he already has. Cory Doctr wrote an

53:31

essay recently that I actually am going

53:33

to talk about. I think I talked about

53:35

another aspect of this essay in last

53:37

Thursday's AI reality check episode, but

53:39

he wrote an essay recently about AI

53:42

psychosis. and he opened by saying this

53:44

is another problem we're seeing with

53:46

chatbots is more uh psychosis are being

53:50

fed. So he's talking about things like

53:54

believing the earth is flat or believing

53:56

that there's like a a shadowy group of

53:58

people that's always following you.

54:00

That's like a real sort of psychological

54:01

condition that used to be very rare. The

54:04

thing about these type of psychosis is

54:06

that they're hard to sustain because you

54:09

have to find other people who will

54:12

validate and support you in those

54:14

beliefs, right? Otherwise, if they're

54:16

marginalized, if you're like, I think

54:17

everyone's following me and every person

54:18

you encounter is like, that's wrong.

54:20

That's just in your head. You need help.

54:22

You you take that seriously. But if you

54:24

meet a group of people that's like,

54:25

yeah, they're they are, and they're

54:27

following me, too, and we have evidence

54:28

for it, and you're right, it feeds the

54:30

psychosis.

54:32

Chat bots unwillingly are psychosis

54:35

generation feeding machines because

54:37

again they're trying to be positive and

54:38

make you feel good about yourself and be

54:40

agreeable.

54:42

So if you start talking about I think

54:43

elves are, you know, elves run the the

54:46

world is flat and run by elves. Chatbot

54:48

might be like, "Yeah, no, you're first

54:50

of all, you're on it. It sounds good.

54:52

Your evidence is good and you're a

54:54

really smart guy and like you should

54:55

keep looking. You're right." And they'll

54:56

it'll pick up that maybe you're like,

54:57

"Yeah, no one believes me." They'll

54:58

like, "It's really unfair." Like they'll

55:00

tell you what you want to hear. And so

55:01

it's really bad if you're dealing with

55:02

psychosis. So I just think there's a lot

55:03

of issues that come out of having fluent

55:06

English conversations with a feed

55:08

forward neural network. It's not good.

55:11

One suggestion I have

55:14

avoid it's very hard at first this is

55:16

weird effect avoid the need to talk in

55:19

complete polite sentences to a chatbot

55:22

just a token processor so talk like you

55:24

we used to use for Google searches super

55:27

tur and technical right you can just you

55:29

know whatever it is sources blah links

55:34

only just like declarative not even

55:36

complete synthesis the token processor

55:39

has no problem understanding what you're

55:41

saying, but it changes your relationship

55:43

to it, right? So, like instead of

55:45

saying, "Hey, I'm interested in trying

55:48

to understand more about like using a

55:50

Raspberry Pi to control uh a Halloween

55:53

display. Could you if you could you

55:55

please like find me several articles

55:57

about this and maybe point me towards

55:59

like um several options that I might

56:00

buy? Thank you." Instead of saying that,

56:03

you could really just say like

56:04

tutorials, Raspberry Pi, Halloween

56:06

decorations, include links, go. you'll

56:09

get the same answer, but your

56:10

relationship with this feed forward

56:12

neural network in some data center

56:14

somewhere is going to be like we have

56:16

with Google. It's a computer program

56:18

server that's gathering and processing

56:20

data for me. So, at least that's one

56:22

hint that can help. Um, I'm going to get

56:24

more into this probably later, maybe on

56:26

the AI reality check. I have a guest in

56:27

mind I might bring on. But this whole,

56:29

you know, chat bots,

56:32

I'm telling you that we are going to see

56:33

chat bots

56:35

15 years from now like we see AOL on the

56:37

internet today. it's going to be this

56:39

like initial use case that we had for

56:42

this technology because it was like the

56:44

first thing to do that like later on

56:46

we'll like can you believe that's how we

56:47

used AI at first we had conversations

56:49

with them like it was people so you know

56:52

we'll see what actually happens there

56:53

all right Jesse um let's close our inbox

56:56

and talk about what I've been up to

57:01

here's a game we haven't played in a

57:02

while do you remember Jesse Deep or

57:05

Crazy

57:06

>> I do

57:07

>> for those who don't No, this is where I

57:10

talk about something I've done recently

57:11

to try to increase the quality of my

57:13

deep work that might cross the line into

57:16

actually just being crazy and Jesse is

57:18

the judge to decide is this deep or

57:20

crazy. Are you ready to play the game

57:21

this week?

57:22

>> I'm ready, baby.

57:22

>> All right. I just spent yesterday. So,

57:25

you know, we're renovating I've talked

57:27

to this on the show. We're renovating

57:28

the production office maker lab in our

57:30

Deepwork HQ because I have a sabbatical

57:32

coming up. I'm gonna spend a lot more

57:33

time working there and I really want it

57:35

to be a space that supports depth. Okay,

57:38

so yesterday I spent I got permission

57:42

from our super to replace the overhead

57:43

light. Spent $600 on an overhead light

57:47

for the maker lab.

57:48

>> Like a chandelier.

57:49

>> It's a crystal chandelier.

57:52

>> It's not a crystal chandelier. All

57:53

right, let me tell you what it does

57:54

before you make your verdict. Okay.

57:56

>> Uh it's a from Phillip and it has Okay.

58:00

It has a long LED panel light that you

58:05

just shines down, illuminates the room,

58:07

16 million possible colors. Then it has

58:10

two track light spotlights adjustable on

58:13

each end of it. All right, so you have

58:15

four adjustable track lights and one big

58:17

long um panel light. And you can aim the

58:21

spotlights however you want. Then using

58:23

an app, you can have many profiles for

58:27

what color out of 16 million different

58:29

colors and what brightness you want on

58:32

all five of those elements. My vision is

58:35

that when I'm doing deep work, for

58:36

example, I want to have just like a

58:39

small amount of warm yellow light coming

58:40

out of the panel and then each spot is

58:42

going to be aimed at a different wall in

58:44

the room. So one wall has the pegboard

58:46

with my maker equipment. One wall I'm

58:48

putting up uh picture ledges with first

58:50

edition technothrillers. One wall has my

58:52

circuitry uh artwork. Um, and then the

58:55

back wall is going to have a video game

58:57

cabinet. So, it can shine a sort of

58:58

light on each of those walls, maybe even

59:00

like a blue light or like an off yellow

59:02

light. And then otherwise, the room can

59:04

be kind of dark except for my bright

59:05

task light right in front of my

59:06

computer. But on the other hand, if like

59:08

we're in there during the day or I'm

59:09

just like working on my Maker Lab table,

59:11

we can have like good bright warm yellow

59:13

light that like lights up the whole

59:14

thing. And the spotlights are just

59:16

bright lights on like the maker wall so

59:18

I can see what I'm doing. And so I can

59:20

have like deep work mode, maker mode,

59:22

just like we're in there just working on

59:23

the computer, daytime mode, and I can

59:26

That's the idea. That's the vision. All

59:27

right.

59:28

>> Deep deep.

59:29

>> Not crazy.

59:29

>> No. No. All right.

59:30

>> That's awesome.

59:32

>> What about the video game cabinet? I

59:34

wanted the ability to have a game in

59:37

that room

59:39

uh from my childhood. I like the '9s era

59:43

in video games. Like all this

59:44

interesting technological stuff

59:45

happened, but I could still understand

59:46

it as a computer scientist. So, I wanted

59:48

something that reminded me of like '90s

59:50

era arcades. So, I'm putting in an NBA

59:53

jam. Oh,

59:55

>> I used to play that game.

59:56

>> Yeah. Right. Um, and I wanted to be a

59:58

game where you could just like play for

60:00

five minutes to clear your head and like

60:01

go back to what you're working on.

60:02

>> Mhm.

60:03

>> Deep or crazy?

60:05

>> Deep.

60:05

>> Yeah. All right. Are we going to get

60:07

good at it? You and I.

60:09

>> Maybe it could be like Michael Jordan

60:11

and Scotty Pivitt.

60:12

>> I, you know, Michael Jordan was not in

60:14

the original NBA jam.

60:15

>> Yeah. He wasn't. What? Right.

60:16

>> He was like, I don't want to be involved

60:17

in this. and then he saw it and he's

60:18

like, "Oh, this is awesome." And then he

60:20

had himself add it back in. All right,

60:22

so we're doing pretty good in there. Um,

60:25

let me tell you what I'm putting on the

60:28

art wall. So, this was my idea. So, I we

60:31

have like the big framed actual art, the

60:34

circuit art from this former engineer

60:37

from the mid-century Silicon Valley who

60:39

started making art out of circus

60:41

stencils. And some of her pieces are at

60:43

MoMA and some other big museums. and her

60:45

grandkids sent me a piece of art from

60:46

her because they like the show. So, I'm

60:48

going to hang that up. It's It's built

60:49

off of a circuit stencil.

60:51

>> Mhm.

60:51

>> You know what I'm talking about, right?

60:52

The green one.

60:52

>> Yeah. Yeah.

60:53

>> So, then I have two smaller frames to go

60:55

next to it. Uh so, they line up to be

60:57

the same height.

60:59

>> I bought a manual

61:02

for like a 1980s era Galaxia arcade

61:06

cabinet, a repair manual that has the

61:09

circuit diagrams for that arcade

61:11

cabinet. And I'm framing in the smaller

61:15

frames two of the actual circuit

61:16

diagrams from that video game cabinet

61:20

vintage repair manual. So those will be

61:21

framed next to this like circuit based

61:24

artwork.

61:26

>> You can have special lights for those

61:27

when you want to emphasize those. Right.

61:29

>> And so the spotlight on that wall can be

61:30

whatever it can it'll be shining right

61:32

on just those artworks which so now when

61:34

I'm in deep work mode if I look over

61:35

there

61:36

>> I see those artworks illuminated. If I

61:38

look up, I'm putting first edition

61:40

technothrillers largely from my

61:41

childhood on the wall. These red acrylic

61:44

picture racks. A light is just on there.

61:46

And if I look to my left, it's like all

61:47

maker equipment. So, it's all about

61:49

trying to create the right mindset for

61:51

depth.

61:51

>> Yeah.

61:52

>> All right. Work continues. All that

61:54

stuff's coming, by the way. And a rug.

61:56

So, area rug so it's not so like live in

61:59

there.

61:59

>> Electrician probably got to install a

62:00

light, right?

62:01

>> Yeah, we got a good guy. Yeah, got a

62:03

good guy who's going to come do it. I I

62:04

want to see if you can bring more

62:05

outlets in there. Yeah, there definitely

62:06

needs to be more outlets.

62:07

>> It's crazy. We we we power so much of

62:10

this lab off of like one outlet

62:13

for more outlets.

62:14

>> Yeah, I'll talk to I'll talk to our

62:15

super about that. All right, let's let's

62:17

get into what I read since the last

62:18

episode recording. I finished two books.

62:21

>> One was uh Maryann Wolf's book, Reader

62:24

Come Home. Fantastic book. Maryann Wolf

62:26

is like the reader the neuroscientist,

62:29

cognitive scientist who studies reading

62:32

in the brain. She wrote P and the Squid.

62:35

uh that book came out like just as we

62:38

had like the smartphone revolution or

62:39

whatever and it sort of surprised her

62:41

that that was part of the reception. So

62:43

then she wrote this book I think it's

62:44

like 2018 maybe I might have that date

62:46

wrong. It's all about reading in the

62:48

brain and the challenge we're in now

62:50

with the age of the digital and her

62:51

ultimate vision for building bilingual

62:53

brains. So actually thinking about a

62:56

brain that's fluent with deep reading of

62:58

hard books and fluent with technology

63:00

use in particular like computer

63:01

programming the same way you would think

63:03

about a brain that can speak like

63:05

Spanish and English. You have two

63:07

different languages that you're you're

63:08

both learning and you can move back and

63:10

forth between them fluently. Uh it gets

63:12

a lot of really good brain science in

63:14

there. So that was a great book. Um I

63:16

also finished a parenting book called

63:17

What Do You Say by William Stricks Ruddd

63:20

and Ned Johnson. Uh we actually picked

63:22

this up. My wife went to a parenting

63:24

talk at our school and she picked up the

63:25

book and God do we need this advice,

63:28

Jesse. I have three kids, including the

63:29

oldest is a teenager. He's 13. Um, bring

63:33

it on. Bring all the the the parenting

63:35

advice. So, so Bill Stricks has a big

63:38

practice that does a childhood

63:40

psychology practice. We know his

63:41

daughter,

63:42

>> which is interesting. Yeah, she's a

63:43

parent at our our kids school and she

63:46

shows up in the book a few times. So,

63:47

that was good. If you have like

63:48

teenagers, it's a good parenting book. I

63:50

So, I I needed that. Let me point

63:53

something out. By the way, we're

63:54

recording this. I want to shine a light

63:56

on my reading strategy.

63:58

We're recording this on March 17th. So,

64:00

those represent my third and fourth

64:02

books of March. So, I'm four books in at

64:05

the halfway point at March. And I really

64:07

put aside a lot of time to do that

64:09

because my middle child is a big,

64:12

ironically given our show, he's a big

64:14

Brandon Sanderson fan. So he he read the

64:17

Misborn trilogy and is now has started

64:20

on the King something. I don't I don't

64:24

know the names.

64:25

>> Mhm.

64:25

>> King Solver. That's not right. But

64:27

whatever. Uh big big thick books. So I

64:29

said I would read the first Misborn book

64:31

that so we could kind of connect over.

64:33

But it's like a bit of a beast. It's 600

64:34

pages. Um, so I was like, I want to

64:37

finish my other four books so I can

64:39

spend the second half of the month just

64:41

reading this one like kind of long novel

64:43

and like kind of get lost in the world

64:44

and not be stressed about it. So that's

64:46

what I'm doing. I'm now going to dive

64:48

into that Brandon Sanderson book. Um, I

64:51

wanted to read Name of the Wind, his

64:52

best book. I feel like I have to explain

64:54

this. I think we have too many new

64:56

listeners that I have to explain this.

64:57

>> Yeah, explain it.

64:58

>> Okay. I know Brandon Sanderson did not

65:01

write Name of the Wind, but I I made

65:03

that mistake. Was this like five years

65:05

ago, Jesse? I mean, it's a long time

65:07

ago.

65:08

>> A long time ago. I accidentally said

65:10

Brandon Sanderson was the author of Name

65:12

of the Wind instead of Patrick Rufos.

65:14

And oh, we heard about it. I think like

65:17

it's the most controversial,

65:20

more controversial than our like Charlie

65:22

Kirk episode or like some of my hot AI

65:25

takes. It's like, "No, no, no. You mixed

65:27

up brand." So, anyways, it's been a

65:28

running joke ever since then. And the

65:30

joke is without explanation, I just

65:32

pretend. I just like, yeah, you know,

65:34

like Brandon Sonson's best book is Name

65:35

of the Wind and every time we get

65:37

letters. Every time. And I love it. I

65:39

don't know why, but every time we get

65:40

letters, and I'm going to continue doing

65:42

that joke, including if and when I meet

65:44

Brandon Sanderson.

65:46

And that'll probably be the end of that.

65:49

Um, all right. Final thing. Different

65:52

parts of me in the news might be

65:53

interesting. Recently, uh, a big

65:55

interview with me came out in the

65:56

Chronicle of Higher Education. if you're

65:58

in sort of academic adjacent worlds. Uh

66:00

it was titled is AI making us stupid? I

66:03

really get into AI and the academy and

66:05

the point of university life and how we

66:07

should and shouldn't use AI. Um so it's

66:09

worth reading especially if you're

66:10

adjacent to that world. I think you can

66:11

sign up for a free account at least for

66:14

a while if you want to check that out.

66:16

Um also uh I was on episode of Tim

66:18

Ferrris's show. I think it came out

66:19

recently maybe last week. I'm not sure

66:20

if I mentioned it or not. He had like

66:23

four shorter segments from four

66:25

different people and I was one of the

66:26

four people and I was talking about

66:28

simplifying and I talked about the

66:31

somewhat drastic things I do in my life

66:33

to try to keep it under control and

66:35

simplify it. How I basically say no to

66:37

almost everything that's not just my

66:39

core efforts at producing new ideas and

66:42

publishing them and getting them out in

66:43

the world. So, if you're interested in

66:44

sort of how I try to manage

66:46

the overload of opportunities in my

66:48

schedule, find that Tim Ferrris episode

66:50

from recently that had me in it. All

66:52

right, Jesse, I think that's all.

66:54

Thanks for listening. We'll be back next

66:56

week with another episode of uh we're

66:58

back on next Monday with another

66:59

episode, another advice episode. And

67:01

this Thursday, I have a AI reality check

67:03

episode queued up to come out as well.

67:05

So, look for that. And until then, as

67:07

always, stay deep. Hey, if you like

67:10

today's discussion of digital technology

67:12

and work, you might like episode 394

67:15

where we talked about using an analog

67:17

planner to keep better control over all

67:20

you have to do. Check it out. I think

67:22

you'll like it. Okay, so I have a

67:23

question for you.

67:25

How do you figure out what to do with

67:28

your time during any given

Interactive Summary

This video discusses the digital productivity paradox, where new technologies, particularly AI, often make workers busier and less productive despite promises of efficiency. A study by Avatra found that AI users spent more time on shallow tasks like email and messaging, while their focused work time decreased. The speaker, Cal Newport, argues that this isn't unique to AI but a recurring pattern with new technologies. He explains the paradox through two main factors: increased speed leads to higher throughput and more task switching, and reduced cognitive effort can lower the quality of work, requiring more effort later. Newport introduces the concept of 'pseudo-productivity,' where visible effort is mistaken for actual productivity, explaining why people embrace these tools despite negative outcomes. To combat this, he suggests using better metrics to measure true productivity, focusing on actual work bottlenecks, and separating deep work from shallow tasks. The discussion also touches on how meetings multiply due to organizational needs for coordination, risk distribution, and signaling participation, and how AI chatbots can exacerbate anxiety and rumination. Practical strategies include focusing on fewer projects, consolidating communication, and making meetings more rigorous.

Suggested questions

6 ready-made prompts