Seeing what holds you back

Capacity is smaller than the calendar suggests. Handoffs and interruptions take time that no task list shows. Businesses have also grown more complex, even small ones, with many things running at once on different schedules, and that makes all of this harder to keep track of. This part gives you plain words for these things: queues, waits, capacity, handoffs, unstructured time and interruptions. The aim is to make them visible so you can look at them calmly. It does not name a culprit, and it does not tell you what to do about any of it.

A business with many clocks

A small business used to be easier to hold in your head. Today, even a three-person shop runs many things at once. Orders come in while a supplier is late. Priorities change in the middle of the week. A customer asks for something that was not on anyone's list.

And each area runs on its own schedule. The baking happens daily. The supplier order goes in weekly. The invoices go out monthly. The email campaign to regulars gets reviewed every quarter. The taxes are filed once a year, and the annual food fair comes around once a year too, with weeks of preparation before it and a few days of work during it.

Each of these makes sense on its own. Together, they are hard to keep track of, both as processes (who does what, in what order, what depends on what) and as time and cost (how many hours and how much money each one takes, over which period). The quarterly review and the yearly fair are the easiest to lose, because they are rare. They are easy to leave out when you think about a normal week, even though they use real hours and real money.

A map helps because it puts all of these rhythms in one place, each with its own hours, cost and people. Seeing them together lets you ask practical questions, and the answers are yours to decide:

• What here could be changed: simplified, moved to a quieter time, or shared differently?
• What is working well enough that you might want to amplify it?
• Where does the work look like it needs more resources, and of what kind: time, people, a tool?

The map does not answer those questions for you. It makes sure you are asking them with everything in view, not just the busy things you happen to remember today.

Two clocks: working time and waiting time

Pick any job that passes through your business, such as an order, a quote or a repair. It has two clocks running.

The first clock counts the time someone actually works on it. The second counts the time since it started. These are rarely the same. A quote that takes forty minutes to write might still reach the customer three days later.

The gap between the two clocks is waiting. Work waits for a person to be free. It waits for a part to arrive, a signature, a reply, or a batch to fill up. It waits because something has to dry, cure, bake or settle.

Waiting is easy to miss because nobody is doing it. A task list shows the first clock. A customer experiences the second. When you only look at the first, a process can seem fast while customers feel it as slow.

Not all waiting is a problem. Dough has to rise, and a customer may need a day to think. The map does not decide which waiting matters. It lets you see the two clocks side by side.

Queues: where work gathers

When work arrives faster than it leaves a step, it gathers. In systems language, this is a stock, an accumulation, and the arrival and departure rates are the flows (see Part 2).

A few things are worth knowing about queues.

• They are often hard to see. Physical piles, such as trays waiting for the oven, are obvious. Digital ones, such as requests in an inbox or tickets in a tool, are not. Orders waiting are one kind of stock. Flour on the shelf and cash in the bank are others.
• They connect size and time. Little's Law is a well-known result from queueing theory. It says that, in a stable flow over the same period, the average amount of work in the system equals the average rate at which work moves through it multiplied by the average time each piece spends there. If a bakery takes about four special orders a week and each spends about two days between order and pickup, you would expect roughly one order open at any moment. It applies to averages, not to any single job.
• A queue is information, not an accusation. A pile in front of a step tells you that, over some period, work arrived faster than it left. It does not tell you why. The reason could be the step, the information that came with the work, or something upstream. That reading is yours to make.

A related idea is the bottleneck: a chain of steps can only deliver as much as its most limited step allows. "Most limited" describes a step in a flow, not a person, and it may be somewhere unexpected, such as an oven or a single signature.

Capacity: smaller than the calendar

Capacity is how much a person, a team or a machine can give over a period. A person with a forty-hour week does not have forty hours of mapped work available. Honest capacity math starts by admitting this.

Some of the week goes to unstructured time: work that is real but appears in no process, such as answering a quick question, looking for a file or tidying up. It is not waste and it is not slack. It is part of how the week actually runs.

Some of the week may be reserved on purpose: time you have set aside for training, planning or maintenance, which is therefore not available for mapped work.

And some of the week is displaced by events that are likely but not scheduled. A client emergency, a sick day, a delayed delivery or a machine that needs attention each take hours from planned work. You cannot say when. You can often say roughly how often, and roughly how much. A single point estimate such as "about four hours a week" is enough. It is a direction, not a forecast.

Put these together and the capacity for planned work is usually smaller than the headline number. If planned work exceeds what is left, that is excess: a number on the page. It says nothing about the person. It can come from the volume of work, how much time was reserved, or how the estimates were made, often several at once.

Handoffs: the seams between steps

A handoff is any point where work passes from one person, team, tool or stage to another. Seams are where a lot of time hides.

At a handoff, the work may wait until the next person is free. The next person may need information that was not included, and ask for it. The work may change form, from a conversation to a document, say. Or it may land in a shared inbox where no one is sure who has it. None of this is anyone's fault. Two capable people can hand work to each other and still lose a day.

On a map, a handoff can be drawn as a line between two blocks. Waiting at a seam is often a different kind from time inside a step: the first is about waiting for attention, the second about the work itself.

A worked example

Illustrative only: Maple Street Bakery is an invented business, with invented numbers.

Maple Street Bakery has a few staff. Dana owns it, bakes and takes the special orders. Léo works the counter. Priya bakes. Dana maps a special-order birthday cake with one block per step: take the order, bake, decorate, box, hand over at the counter.

She assigns people to the blocks with the hands-on time she expects, about three hours in total across the steps. That is the first clock. Then she looks at the elapsed time, from the order being taken to the customer collecting the cake, as about two days. The gap holds some waiting that is simply physical: the layers must cool before they are decorated. It also holds waiting for the oven, which the morning bread bake fills first, and the hours the finished cake sits in the fridge until pickup. She enters those waits as Delay on the blocks that receive the cake. She sees that the two clocks differ a lot. That is information. She does not yet know why.

Next she looks at capacity at the counter. Léo works about 30 hours a week there. Dana reserves about 4 hours for restocking shelves and cleaning, and adds a rough allowance of about 3 hours for interruptions: phone calls about orders, a delivery driver, a question from a regular. That leaves about 23 hours for planned work. The counter schedule asks for 24 hours of serving. The difference is about 1 hour, a figure to review.

There are several ways to read it:

• The restocking reservation might be larger than needed, or just right.
• Special-order questions might arrive by phone because the order slip does not say the pickup time, so staff spend minutes asking again.
• The estimates might be a little high or low, since they are rough.
• Or one hour might be well within the normal give-and-take of a week.

The map does not choose among these. It has made the question easier to ask. She may take it to Léo, who knows things the map does not. The next step is hers.

Flour, eggs and the day's cash are stocks too, and she knows them well. The map does not hold them. She can mention them in a block's description, such as "flour order arrives Tuesday", or in a Note beside the map, and keep them in mind alongside the hours.