Breakdown
It Takes Three Weeks Because Nobody Gets Ninety Minutes
The hours exist. They arrive in pieces too small for the work to move.
Work that drags for weeks is not always short of capacity. It is being done in ten-minute pieces, and some work has to be restarted each time rather than resumed. Often the better fix is fewer interruptions, not just faster replies.
The proposal was scoped at two days. It has been open since the first week of the month, and the person who owns it is not slacking or stuck. They are in and out of it all day, ten minutes at a stretch, and they keep telling you they will finish it tonight when it is quiet. Sometimes they do, at half past ten, and it comes back needing another pass.
Where the two days actually went
Add up the fragments and you may find more time was spent touching the task than anyone realized. The problem is that much of that time was spent getting back into it rather than moving it forward.
What gets spent first in a short session is not the work. It is the reload. Opening the file, rereading the last paragraph, remembering the objection you were about to handle, finding the tab with the numbers in it. On a ten-minute window, a good part of it can go before anything new happens.
That points at the distinction worth having. Some work resumes and some work has to be restarted. Clearing a straightforward inbox resumes fine, because each item is self-contained. Pricing a proposal, writing a plan, or untangling a client’s mess needs the whole shape held in your head at once. Break that into pieces and the person rebuilds the picture every session and rarely gets past rebuilding.
Which is why finishing it tonight often does work. At half past ten they finally get an uninterrupted run at it. It also explains the extra pass. Judgment made late, after a full day of being pulled around, tends to need checking in the morning.
What is producing the fragments
It is tempting to read this as a discipline problem, but often the day itself is creating the fragmentation. The person’s day is being shaped by what arrives at it. Look at a week of the interruptions and most of them fall into a few recognizable kinds. Questions whose answers already exist somewhere. Threads with five people on them so nobody could be blamed for leaving someone out. Non-urgent items sent the moment they occurred to somebody, because sending costs nothing.
None of that is people behaving badly. It is what happens in the absence of a decision, and the decision may never have been made on purpose: what is allowed to reach a person, who actually needs to be on which thread, what can be answered without a person at all. With no answer to those, the default takes over, and the default is that everything reaches everyone the second it exists.
It gets worse when the answers only live in somebody’s head. If the process was never written down anywhere a colleague can find it, the person who knows becomes the search engine, and every lookup costs them a session. For an owner-operator, this can become a large part of the day. You are the default destination for anything ambiguous, which means your calendar is assembled by other people’s uncertainty.
What usually gets tried
First comes calendar hygiene. Focus blocks, notifications off until eleven, a rule about who can move the standup. All reasonable, until the interruptions start overriding the blocks again. Then a client escalates, the block comes down, and it never really goes back up. Blocking time without changing what arrives does not remove the interruptions. It stacks them into a burst that lands later.
Then comes tooling. Meeting recaps, thread summaries, drafted replies, an assistant that catches you up on what you missed. Each of these looks like a productivity win, and some of them genuinely save minutes. But notice which direction they push. They make responding cheaper, which can make it easier for more questions to keep flowing to the same person. The person who answers fastest often becomes the person people ask first.
There is a second-order version of the same miss, which is buying a tool for a capability you are already paying for. That happens often enough to be worth checking, and a convincing demo of software you already own is a common way money leaves a small business. Even when the tool is new and good, it still does nothing about the count. A tool that helps you answer things faster tends to leave you answering more of them.
A week of looking before you buy anything
Pick the task that has been open too long. For one week, ask the person who owns it to jot a line whenever they sit down with it: time in, time out, and whether they picked up where they left off or started from the top. It takes a few seconds a session, and after a week the pattern is usually easier to see. Ask them to note what pulled them away, roughly where it came from, and whether it needed them specifically.
Two things fall out. The first is the longest uninterrupted stretch that task got all week. If the answer is twelve minutes, nothing that drafts faster is going to close it, because the work needs a longer sitting than anyone gave it. The second is the ratio of restarts to resumes. Mostly resumes suggests the task may simply need protected time. Mostly restarts suggests something about how work is reaching that person deserves a closer look.
For the interruptions you have now seen a pattern in, there are three honest responses. Answer it from the record, so the question stops needing a person. Route it to one person once instead of to five people hopefully. Or hold it until there is a batch, because it was never urgent. Some of the first group may turn out to be a rule rather than a judgment, which makes it cheap to handle and safe to hand over. Working out which of the three you are mostly dealing with is the part worth doing before anything gets built.
So there is one question to put to any proposal aimed at productivity, whether it is software, an automation, or a change to how the week is organized. Does this reduce the number of times a person gets pulled out of work, or does it only make being pulled out cheaper? Both look like progress in a demo. Only one of them gets a two-day task finished in two days. Sometimes the answer is a mailbox rule and a decision about who belongs on which thread. Sometimes it is a system that answers the recurring questions from the record so they never reach a person at all. Either way, you are aiming at the count, not the speed.
How we architect AI systems
How we architect AI systems
About the author
Missy Ross
Missy Ross is the Founder and AI Architect of Vero Dawn, an AI architecture and solutions company that helps businesses see what could work better, determine the right solution, and bring it to life. Before founding Vero Dawn she spent 21 years in internal audit across banking and manufacturing, at Audit Director level.