Ask a leader where the organization's hours go and the answer arrives quickly. Meetings, email, client requests, the usual demands. Ask for a number and the answer slows. Almost nobody has one. The hours go somewhere every week, and the somewhere has a location.
Capacity leaves an organization through a small number of specific places. Those places can be found, counted, and named. Most leaders have never looked, because the leader is standing inside the leak, busy with the work the leak creates. The structural reasons organizations stall are covered in the piece on operational architecture. This piece is narrower and more physical. It is about locating the hours.
Three Ways Work Disappears
A leak is work that disappears. Hours get spent and nothing moves forward as a result. It takes three common forms.
Work gets duplicated. Two people build the same thing because neither knew the other had started. Work gets redone. A finished deliverable comes back for revision because the brief changed on the way. Work gets stuck waiting. A request sits for three days behind a single answer that one person has not yet had time to give.
Each form is invisible on a task list. The task shows as in progress, then complete. The hours consumed by duplication, revision, and waiting appear nowhere, so the organization records the output and loses sight of the cost.
Leaks resist the usual remedies. Faster effort applied to duplicated work produces duplicated work at speed. The hours are already gone before anyone's pace enters the picture.
Where to Actually Look
Leaks cluster. Three places account for most of what an organization loses.
The first is the point of handoff. Work moves between people, teams, and tools, and every transition is a place where context drops. The receiving person asks a question the handoff should have answered. Someone writes a clarifying message, then another. Count the follow-up messages that trail a handoff and you have counted the leak.
The second is the recurring exception. A situation arises that the usual process does not cover. Someone improvises a solution, and the situation returns the next week and the week after. Each time it gets handled as new. Every recurrence costs the same hours, and the quarterly total surprises anyone who adds it up.
The third is the step that exists only because an earlier step is unreliable. A person double-checks a report because the report has been wrong before. A manager confirms a task was finished because tasks sometimes go unfinished. The check is sensible. It is also a tax on every unit of work that passes through, paid indefinitely, for a problem upstream that nobody fixed.
Each of the three can be found with a calendar, a message thread, and an honest account of what happened last Tuesday.
The hours leave quietly. You feel tired and cannot say why.
Why You Cannot See Your Own
You route around your own leaks automatically. The workaround is quick, it works, and it folds into the way the day runs. After a few months it stops registering as a workaround. It registers as the job.
Everyone inside an operation does this. The person who rekeys data between two systems every Friday describes the job as "the Friday report." The person who chases approvals describes it as relationship management. The labels are accurate and they hide the leak, because a label names the activity and leaves out the hours spent compensating for a gap.
The newest member of a team often sees a leak first, because the workaround has yet to become routine for them. Their questions about why a step exists are usually accurate, and they usually draw the answer "that is how it works here."
In founder-led organizations the pattern concentrates in a single calendar. The thirty-day test shows how much of an operation routes through one person. The leaks in that calendar tend to be the largest in the organization and the least visible, because the person holding them is the person who would have to see them.
What a Week Would Show You
A week of tracked hours would show something specific. Log what people did, in the order they did it, and mark which pieces produced progress and which pieces repaired, repeated, or waited. Set that log beside the job descriptions and the calendar. The distance between where the hours were assigned and where they went marks the leak.
Leaders who have looked tend to find the same shape. The hours cluster around a handful of recurring points. The cost at each point looks small on any given day. An hour a week, multiplied by every person who touches the same handoff, multiplied by fifty weeks, ranks among the largest line items in the operation, and it appears in no budget.
That figure also changes the conversation about capacity. Capacity conversations usually begin with headcount. A leak count begins the same conversation with a different number. A team described as stretched thin is often a team carrying a few specific leaks. The hours exist. They are being spent somewhere else.
Three places now have names: the handoff, the recurring exception, and the compensating step. A leader who can find those three in their own operation holds the language for the rest of the work.
Which leak to close first, and what closing it asks of the structure around it, is its own discipline. Naming the three comes before all of it. Leaders who get that far can point to where the exhaustion comes from, and a location is something an organization can work with.