I apparently got 50% better at my job last month

…by spending 50% more time on the important parts instead of Slack/email/busywork/things I do when I’m unfocused. I actually didn’t even notice until I checked my monthly RescueTime report—at which point I realized I had gotten an extra 40 hours of engineering work in September compared to August.

I had no intuitive sense of that difference—if you’d asked, I’d have guessed my engineering time in September was roughly the same as August. It’s disturbing to me that I didn’t notice such a huge difference. On the other hand, a consistent difference of 80 minutes daily can easily be swamped by the 3-4 hour day-to-day swings depending on my schedule, level of focus and how much I feel like working. So I can sort of understand.

Here’s the comparison of my RescueTime reports:

As the table shows, it’s not just that I had more time in September. Instead, I got my programming gains by taking time away from other activities—roughly 50% from communication and 50% from other activities.

The decrease in communication time partly explains why I didn’t notice; the bulk of my communication happens in small chunks with frequent context switches to other things, so it’s hard for me to notice when it takes a lot of time. On the other hand, when I’m doing programming work I frequently get so absorbed that I lose track of time, so I don’t realize when I spend more time on that either. I suppose the point is that my impression of how I spend my time is incredibly unreliable!

It remains to be explained what actually caused this shift, though. I changed a lot of things about how I worked between August and September, and it’s not clear which ones were important. But here they are, in order of how sexy of a productivity tip they are.

Meetings. At the beginning of August I had an ad-hoc meeting schedule—I had one-on-ones on two different days of the week, a company all-hands meeting on Tuesday, hiring interviews scheduled throughout the week, and smaller one-off meetings whenever we felt like it. But I realized that every meeting destroyed some time beforehand (because I had to spend attention worrying about making it to the meeting on time) and afterwards (because I had to get back into a focused state). So I started batching my meetings on Tuesdays and alternate Fridays. I pretty immediately saw a huge increase in the amount that I got done on non-meeting days.

I get the sense that this doesn’t really work at larger companies, given e.g. how excited this Facebook guy is that they have one whole day where he doesn’t have any meetings. But I’ll enjoy it at Wave while it lasts.

Closing Slack. I realized that I spent a lot of time reading Slack in short bursts simply because it was sitting there in the middle of my Cmd-Tab switcher. I wrote a piece of AppleScript that used Notifications Scripting to pop up a notification every 10 minutes reminding me to close Slack if I wasn’t waiting on a response from someone:

The only sad part is that the Slack desktop app takes about 30 seconds to start up (yes, in 2015), which makes me close it less often than I otherwise would, and waste more time waiting for it to load than I otherwise would. (Slack people, are you listening? Stop re-coloring your plaid and fix your startup time!²)

BS timeboxes. I realized that I was spending a long time on things that needed to get done but didn’t feel important (a random recent selection: buying a mouse on Amazon, doing accounting, planning a trip, applying for Global Entry). My default pattern was basically doing things whenever I remembered about them and felt like I had time, or like they were sufficiently urgent. Instead of that, I added three weekly one-hour “BS timebox” events to my calendar and committed to working on urgent-but-unimportant tasks only during those windows. This both forced me to do them efficiently, and meant that I didn’t have to think about them for the other 163 hours in the week.

Delegation and automation. At Wave I ended up being assigned one particular task that interrupted me a few times a day—I had to look through our systems for transactions that encountered unexpected errors or got stuck and deal with them. I took two steps to fix this. First, I whined about it enough to our CTO that it got delegated to a less-technical employee (who would take care of the common cases herself and escalate confusing/rare ones back to me). Second, I refactored the transaction handling system so that it had a much easier and more uniform error handling interface. This made it much easier for us to automate the handling of new errors, which meant that we were gradually able to reduce the load of manual error-handling even further.

Office. Midway through September I moved into a private office about 10 minutes’ walk from my house. I’m very easily distracted by any sort of visual or audio interruption happening nearby me, so working from home, or from an open office, is distracting and unpleasant. Having a place that’s just me and my computer has done a lot for my focus.

Moving. In mid-August, Ruthie and I moved into our new group house. The move didn’t seem to affect the amount of time that I spent on the computer overall (since that didn’t change between the two months), but I definitely benefited in September from not having to worry about random house-related things as much.

Edited Nov. 8 to clarify a few things for the easily-confused Hacker News readers.