Increase Your Productivity. Work in 45 minute blocks.
Over the years, I have settled on a system that best allows me to focus and be productive.
Work 45 minutes. 10 minute break.
Work 45 minutes. 10 minute break.
Work 45 minutes. Longer break.
Repeat as necessary.
How did I come about this system?
Mostly by trial and error and observing my energy. I would notice that it would take me about 45 minutes of working on something to come up with a solution. For example, if I was working on a bug fix, from the moment I started to the moment I finished would be 45 minutes. I would feel good about accomplishing my task and would take a break to relish in the accomplishment and prepare for what I needed to do next.
After doing this system for a while I came across a study that found people can only focus on one thing for about 45 minutes. After 45 minutes, your mind starts to wander and you have a tough time remaining focused. A break helps re-energize your focus.
(Unfortunately I do not recall where I read this. If I come across it again in the future, I will edit this post)
What about longer tasks?
Longer tasks are just broken down into smaller pieces. No matter how large the project is I break it down into something that can be accomplished in about 45 minutes. In fact, you need to do this otherwise the project would just seem overwhelming.
Sometimes I do want to keep working but I usually feel worse if I do. My muscles will start to ache from sitting so long. You need breaks. Standing up and walking around helps improve your circulation causing better blood flow to your brain.
During the breaks, I will usually use the time to think about what I want to do next. I try to turn this break time into planning/thinking time. Too often as programmers, we just want to do, do, do. It is important to spend some time each day thinking about and planning your work otherwise you may end up spending time working on something that is not important.
To make sure I take breaks, I use SlimTimer to time my work. I start by simply clicking on the task and when 45 minutes are up, I take a break. Sometimes I will go to 50 minutes if I just need a few more minutes or stop at 40 if I have accomplished my task already but it usually averages out around 45.
It is important to remain as focused as possible for the 45 minutes otherwise this system does not work. You must resist any temptations that may pull you away from your task. Stay focused on one thing. Turn off email notifications and IM and close your browser.
Give this a try for your own work. Use a timer but only time the periods you are focused and productive. When you notice your focus is slipping or you need to take a break, stop the timer and observe how long you remained productive for. Keep recording this information for a week or two and you will start noticing patterns about how you work.
Edit: Here is one reference I have come across from “How to Stop Worrying and Start Living” by Dale Carnegie (unfortunately no reference is given for this passage):
“Why is [rest] so important? Because fatigue accumulates with astonishing rapidity. The United States Army has discovered by repeated tests that even young men – men toughened by years of Army training – can march better, and hold up longer, if they throw down their packs and rest ten minutes out of every hour.”
–
(650) 319-8873
matt@mattmccormick.ca
mattmccor
mattmccorm
mattmccormick
I really want to try this approach when I’m coding, because I know I need to take breaks to rest my eyes and keep from overusing my hands. Sometimes I get so involved coding that either I don’t want to stop, or I am afraid if I stop I’ll lose my momentum. When I have structure for something in my mind that I’m figuring out as I go along, generating insights, is when I am most reluctant to stop. How do you handle those times?
Hey Tod,
I generally follow this but not always. If I am on a roll, I will keep going for another 45 minutes but then I notice that my joints start to ache and I can’t think as clearly. My body tells me I should have taken a break.
I never worry that I’ll lose momentum. Usually, a break helps to keep the momentum going once I return to work. It also helps me prepare for the next task. If I was struggling with something, I’ll find that I have an insight while on break and can then immediately solve it once I return.
Sometimes if I know I’ve almost solved something and the solution is just ahead, I will go another 5-10 minutes but I rarely need more than that. Sometimes I will break at 40 minutes if I have solved something and know there is nothing I can do in 5 minutes.
But usually, I find that after 45 minutes or so, I’ve accomplished something meaningful so I “reward” myself with a break and bask in that feeling of goodness. I always try to break after solving something so I feel good about it. Occasionally I will also break when I am frustrated with something but this is less often.
If you are worried about taking breaks, perhaps just start using a timer and notice when your biggest solutions occur or when you get that feeling that you need a break. Maybe it will be different for you and it will be better for you to go longer.
Hope this is useful.
I also follow this advice and find it works well, though I usually go for 40 minute blocks of time.
Hey Matt, I’ve just read through many of your blog entries and I think they’re great. Your experiences and advice mirror my own as a software engineer. Keep up the good work!
Thanks for the encouragement Jonathan!