We all start with big plans on working days: a few hours we’ve blocked out for proper progress, a list that looks achievable, and a picture of finishing the day with most of it ticked off. Then context switching gets in the way, often within the first hour, when a message pops up in the team chat asking if you can spare a minute.
Answering may only take that one minute, but returning to the task you were previously focused on takes a lot longer. This scenario is the reality for most delivery teams. It happens a lot more often than people generally admit when I bring it up with them.
Small requests add up
It’s fair enough that someone needs a second opinion on their design work, another pair of eyes on a bit of complex code, or a quick answer for a client who’s waiting. Add to that the notifications that have your hand reaching for the phone before your brain has even placed the sound, and the “quick catch-up at 11.15, hope that’s OK?” that appears in your calendar mid-morning.
Whoever’s asking is usually just trying to keep their own work on track, and a single request on its own barely registers for most people. Over a full day though, four hours of planned focus can easily end up as just one or two.
Plenty of teams have come to treat that as just how work is, so finding focus means starting early, staying late, or sticking headphones on and hoping for the best.
The production line that keeps stopping
I tend to picture it as a big production line, where each time someone asks for input, the person they ask has to switch off their part of the line and walk over to help. When they get back, the machine takes a while to get up to speed again, and any work queued up behind them, along with the people who rely on them, sits waiting too.
Delivery work is messier than a factory, but the same thing happens to a developer halfway through a tricky bit of code, or a designer with a half-finished layout. Answering takes a minute, and getting back to where they were can take up to fifteen minutes, depending on the task.
Paul Graham wrote about this in his essay on the maker’s schedule and the manager’s schedule. A manager’s day is split into hour-long slots, so one more meeting barely registers, while people who make things need half a day at a time, and a single meeting in the middle can break it up into less-productive blocks.
In most agencies, project and account managers work on a manager’s schedule because client work needs them to, and they book calls into developers’ days for the same reason. It’s a sensible way to run client work, but the two schedules were never designed to share a calendar.
The two schedules were never designed to share a calendar.
How long things can wait
Apart from people working on the same piece of work together, there’s very little in a delivery team that can’t wait a few hours for an answer. Quick replies have become the norm though, and asking feels free to whoever’s doing the asking. Agreeing a short gap between a question and its answer is usually enough to get started.
Small steps
The teams I’ve seen do best at this didn’t start with a big change programme. They started small and adjusted and reviewed as they went.
Block out more than half the day, usually the mornings, when nobody outside the team expects a reply and client calls and check-ins wait until the afternoon.
Give questions somewhere to wait, like a shared thread or channel that gets checked at set times, say before lunch and before home time. They still get answered, without pulling people out of their work.
Think about context when you ask. A question about the thing someone’s already working on costs them far less than one about a different project, so where you can, send it to whoever’s closest to it.
Put stand-up at a natural break, either first thing or straight after lunch, so it doesn’t cut a morning in half.
If you want something for your team’s working agreement, this is a good start:
Mornings until 12 are focus time. Messages from outside the team get a reply after lunch. If it really can’t wait, call.
Try it for a couple of weeks, then have a look at what got done and how folk felt about their days.
Most people join delivery teams because they like getting stuck into a problem. A morning without interruptions gives them the chance to do that, with a bit of time to stop and think as well.
I’m Harry Bailey. I work with delivery teams whose days get chopped up by everyone else’s quick questions. See how a team reset works.
Photo by amin khorsand on Unsplash