back to indexCan You Implement Your Productivity Tips Without Time-blocking?
Chapters
0:0 Cal's intro
0:20 Cal reads a question about productivity and time-blocking
1:3 Cal explains his Time Management system
2:5 Cal talks about ticketing systems
3:30 Time-blocking might work for you still
00:00:06.920 |
As always, we start with questions about deep work. 00:00:14.960 |
Tanner says, "Can you implement your productivity tips 00:00:25.520 |
and I have implemented a capture configure control setup 00:00:28.680 |
that has greatly helped me reign in my caseload." 00:00:33.640 |
but he says he generally finds it hard to time block, 00:00:40.440 |
He says, "Often things bubble up throughout the day, 00:00:43.000 |
and I have more small tasks than can be easily scheduled. 00:00:54.980 |
So what is the patented Cal Newport productivity system? 00:01:01.320 |
to a video in which I explain this step-by-step, 00:01:13.980 |
and I have a core idea video on time management 00:01:16.720 |
where I say, "Here is my philosophy for time management. 00:01:23.880 |
for implementing those high-level principles. 00:01:26.640 |
So the high-level principles, as you mentioned, Tanner, 00:01:31.020 |
Time blocking is part of how I specifically implement 00:01:36.620 |
So you can certainly take those high-level principles 00:01:44.280 |
for that control piece, not having time blocking. 00:01:49.800 |
I would say the most commonly occurring example I get 00:01:54.760 |
or hear from in terms of individuals who use that system 00:01:57.640 |
but don't use time blocking in implementing control 00:02:05.240 |
will often run their days off a ticketing system. 00:02:07.880 |
So control, time blocking is not that relevant for control. 00:02:14.120 |
what they worry about is there's a small amount 00:02:20.000 |
that has to happen in addition to just servicing tickets. 00:02:24.040 |
And they typically put aside a certain amount of time, 00:02:30.560 |
And so they are definitely controlling their time 00:02:32.840 |
but they don't have to time block every minute. 00:02:34.120 |
It doesn't make sense 'cause most of their day 00:02:37.120 |
is actually executing one ticket after another. 00:02:41.080 |
that you have a different method of controlling. 00:02:46.560 |
And so capture is about not having things in your head, 00:02:53.520 |
You're not keeping track of things in your head. 00:03:02.280 |
clarifying, taking things off, moving things around. 00:03:05.060 |
So you really understand what's on your plate. 00:03:11.320 |
that you are not reactively just going through your day, 00:03:13.640 |
saying what's next in a way that is unintentional. 00:03:17.020 |
So however you wanna implement that is fine by me. 00:03:20.200 |
I will say though, Tanner, looking at your elaboration, 00:03:23.880 |
I'm not sure that time blocking is not gonna work for you. 00:03:35.760 |
that if you put a little bit more emphasis into configure, 00:03:39.120 |
you might be able to use time blocking and control 00:03:44.360 |
more small tasks that can easily be scheduled. 00:03:53.120 |
in a way that you can make intelligent decisions 00:04:08.240 |
You have certain times where you work on certain things. 00:04:10.080 |
You can make decisions about which of these things 00:04:17.280 |
is that you're getting to your time outside of cases 00:04:25.760 |
So I'm gonna say, and I don't know if this will work for you 00:04:27.600 |
because again, I only have two paragraphs here, 00:04:29.160 |
but I'm gonna say, lean in more into the configure step 00:04:49.800 |
It's not necessary and maybe not best for your job,