Brian Crain on Optimizing Productivity
June 18, 2014
There are many people in the QS community who are fascinated by understanding productivity. We’ve featured many different talks that explore different methods for tracking and hopefully improving productivity. At the 2014 Quantified Self Europe Conference we were happy to continue this exploration with a show&tell talk by Brian Crain. Brian has been thinking about his productivity since 2011. He tried a few different methods, but he’s found that using the pomodoro technique has been very helpful in understanding and improving his work. Watch his talk below to learn what he found by tracking the number of pomodoros he completes each day and what new methods he’s using to make sure he gets things done.
You can also view the slides here.
What did you do?
I started tracking my work time using the Pomodoro Technique in 2011 and have been logging all my sessions since September 2012. While, I have kept experimenting with different productivity methods, my consistent usage of the Pomodoro Technique has given me a great view of changes over time. I also discussed my experience with tracking my commitments over the past months.
How did you do it?
For the Pomodoro Technique, I would set a task, work on it for 25 minutes, then log the task. Over time, I built a large excel sheet that automatically updates with a variety of metrics that tell me how much productive time I spent working and how that has changed over time. For the commitment tracking, I would use an agenda, where I write down all commitments. I would then cross out completed commitments and track my compliance at the end of each day.
What did you learn?
I learned that having a continuous metric is enormously motivating since it allows you to continually improve yourself. These small, continuous changes make a huge difference over time. I also learned that building a user-interface is tricky, but very important to make tracking rewarding. This is something I successfully did with the Pomodoro Technique, but have found difficult to replicate with other methods. Finally, tracking commitments has taught me how critical one’s mindset is. When I would slip into thinking of commitments as simple tasks, my success with that method derailed completely. So for that method, I realized how important it is to build a system and user interface that helps maintain the commitment mindset.