Work Doesn’t Happen at the Computer
thesweetsetup.com
thesweetsetup.com
No. Just no. I learned this in a past life working in the film industry and apply it daily in the military. If you have three things that must happen in a day, do the easy tasks first, especially where these tasks involve multiple people and/or equipment.
Think of what happens if you start with the hard task. Little problems happen. Delays stack up. The quest for perfection stretches the one task into the entire day. Soon the sun is going down and you haven't accomplished anything. If you start with the simple things those little problems are easier to solve. On a film set this is why the big action shot, the complicated bar scene with the moving camera and twenty extras, happens at the end of the day. The core team warms up by doing the easy two-person dialogue scenes early in the morning. When it is time for the harder tasks all the equipment has already done its thing. You know all the necessary people are present and ready. And the looming deadline means there is a sense of urgency in the air. Everyone wants to go home and so puts maximum effort into making that final shot work in as few takes as possible.
> Think of what happens if you start with the hard task. Little problems happen. Delays stack up.
Well yeah... if there's likely to be delays in the hard task then I want them started as soon as possible so there is time for the delay to be cleared and I can do other easy things in the delay time. If I start at 1630 and then there's a delay, then the task isn't done on that day.
In my work there is an infinite number of easy but still reasonably productive things I could do.
Starting with hard tasks, I tend to do a lot of unproductive procrastination (browsing reddit, youtube, HN...) while trying to work myself up to do the difficult thing. But, like you, if I decided to get all the easy tasks out of the way first, I could do that indefinitely. I also tend to do my best work in the morning; by the end of the day I'm too tired to do a good job on a hard problem.
So, I start with one or two easy tasks, to ease myself in to working, then move to the hard ones, then ease off again as my energy fades.
Admittedly this was to corral a bunch of hard-drinking journos, but the time-boxed idea does have merit.
For many years working at a large defense contractor (SAIC, now called Leidos) I only worked 32 hours a week, and when at work, I would often talk co-workers into taking walks around La Jolla Cove, near of office, when we had to plan work, discuss problems or improvements with our software, etc. That was decades ago, and I feel that it was the correct strategy for getting valuable work done and making a positive impact.
A little off topic, but I have been exploring ways to spend much less time at my computers, easier for me to do now that I am (mostly) retired. As an experiment, I have been using a high compute capacity VPS and a small iPad Pro to write code examples and do some of the actual writing for a second edition of a book [1]. I find that I do even more thinking away from any device, usually while hiking or walking around the block. I do cheat and occasionally plug my iPad into a large high resolution monitor that my mosh client takes great advantage of. +1 for Mosh + tmux + a VPS far more powerful than a laptop.
Maybe I need advice on how to collaborate with the day, so that me and the day can get to know each other, enjoy each other's company, and become more than the sum of our parts.
This is an extremely office-centric view of the world. Most people’s work is not like this.