Zee Spencer

Drift Work, Shift Work

Over the years, I've heard many ways to frame the tradeoff in work conditions that optimize contributors' work productivity and managers' work productivity. The most popular being "Maker schedule, manager schedule." While I agree that some kinds of work are best suited to specific work conditions, I'm unconvinced a manager versus individual contributor framing is helpful when attempting to determine how to structure my workday. Why?

  1. It exacerbates tensions between management practices and software development practices.
  2. It "walls off" work tactics or strategies that may be suitable across roles behind role boundaries.

I suggest an alternative: shift work and drift work. Instead of splitting work between a boss/worker hierarchy, we acknowledge that work fits best when and where the time and attention the worker has is well suited to the task at hand.

Thinking in terms of shift work and drift work gives us options for mitigating tensions around what work is and is not getting done. We can evaluate the work that is missing, determine whether it's more amenable to shift work or drift work, and adjust our work-schedules as appropriate.

Shift Work

Shift work is focused. It's the work where we are at our best in a flow state. Our goal is to complete all the things or perform a particularly time-intensive task to completion. Work like debugging, designing test plans, processing support tickets, shipping a feature, intensively reading a book or following a course, or providing thoughtful critique are some examples of shift work.

Shift work responds well to structures that enable a state of flow while performing that work. For some, these structures may be working in a particular place at a specific time. For others, they may be having the flexibility to drop deeply into work when inspiration strikes. Perhaps someone achieves flow when their workflow bubbles up the next piece of work worth doing. Or maybe it's easier to achieve flow in a distraction-free environment where only the current task matters.

There is no "right" or "wrong" way to perform shift work, and what works well for me may not work well for you.

Drift Work

Conversely, drift work is unfocused. The goal with drift work is not "complete all the things," but rather "notice what wants doing, and (perhaps!) do it." When doing drift work, we do not try to complete a known set of tasks. Instead, we try to take care of the things that may be at risk of falling through the cracks. Some examples of drift work are catching up on correspondence, double checking some numbers, jotting out a rough draft, fiddling a bit with a design that isn't quite baked, skimming a monitoring suite to evaluate system health, or casually reading a book or following a course.

Drift work responds well to structures that increase spaciousness while performing the work. For some, having clear time-budgets encourages spaciousness. For others, time limits feel constraining and over-bearing. Some drift work requires availability to be interrupted. Other drift work is done best when you don't have to worry about other people or pressing tasks wanting your attention.

Like shift work, there is no right or wrong way to make space and perform drift work.

Make Time for Both

In systems where people are not doing enough drift work may have stresses and tensions emerge where people feel there "isn't enough time" to get "all the things done." These tensions emerge not because there is not enough time to get all the things done, but because we are not doing enough drift to evaluate what is genuinely valuable and what appears urgent or critical at first glance.

Conversely, in systems where people are not doing enough shift work struggle to execute on work worth doing. People may feel pulled in too many directions, or like there isn't a point to the conversations they're having at work. After all, nothing gets done anyway.

It may come as no surprise that different people within the same team or organization may perceive the tensions as having different causes. People who feel most productive doing shift work or enjoy the feeling of pushing their limits may feel like doubling down on getting things done will make the tensions go away. People with a strong preference for drift work may feel exhausted by spending even a few hours a day in a focused, high-activation work state. Even more confounding, the same person may have different needs applying the drift work/shift work spectrum based upon factors outside the context of the organization.

What Works Well For Me (For Now)

I've found that my most productive days are ones where I can take thirty minutes in a "triage and respond shift" that slowly transitions into drift work. Once I no longer have things pulling my attention, I take a break, eat some food, move around a bit, and wash up. Once restored, I'm ready for some tightly-focused shift-work that can last two to six hours and ends when I'm fatigued or otherwise 'done.'

Browse posts about:

Want to get notified when I publish new articles or update old ones? Subscribe to my newsletter. It's a weekly-ish set of interesting links with a short essay on programming, design, technical leadership, or anything else that strikes my fancy.

Not sure? Read the archive.