This chapter focuses on work itself: how it enters your business, moves through it, and emerges as completed output. The distinction that matters most is one that many businesses overlook: the difference between effort and flow.
Effort Is Not Flow
Most businesses measure activity. They notice when people are busy and worry when people appear idle. This makes intuitive sense. If everyone is working hard, the business must be productive. If someone is not working, capacity is being wasted.
This intuition is often wrong. A business can have every person working at full capacity and still produce less than it should. The problem is that effort measures what people are doing, while flow measures what is getting done. These are not the same thing.
Consider a business where five people handle different stages of a job. Each person is busy. Each person completes their part efficiently. But between each stage, the job waits. It waits in an inbox, in a queue, on someone’s desk, or in a shared folder where no one checks it until they have time. The individual work is fast; the total time from start to finish is slow. Everyone is busy, but work is not flowing.
Where Work Actually Spends Its Time
In most small businesses, work spends more time waiting than being worked on. This is counterintuitive, especially in businesses that feel perpetually busy. But if you trace a single job from the moment it enters the business to the moment it is complete, the pattern becomes visible.
A request arrives and sits in an inbox until someone sees it. It gets assigned, but the person it is assigned to is working on something else. When they finally start, they realize they need information from someone who is unavailable, so the work waits again. Eventually it moves forward, only to need an approval from someone who is busy with other things. Each active step may take minutes or hours; the waiting between steps takes days.
The business feels busy because the active work is constant, but the output is constrained by how long work waits between steps, not by how fast people work.
The Constraint That Matters
When work moves through multiple steps, the speed of the whole process is determined by its slowest point. This is true whether the slowest point is a person, a decision, or an information gap. Everything upstream of that point eventually piles up waiting; everything downstream is starved for work.
In most small businesses, the constraint is rarely where people expect it to be, rarely the most complex task or the most skilled work. More often, it is something mundane: an approval that requires the owner, a piece of information that only one person knows, or a step that depends on someone who is perpetually overloaded. Constraints are often obvious in hindsight but difficult to see while you are inside the work itself.
Identifying the constraint changes how problems should be addressed. When work is backing up, the instinct is often to add capacity everywhere or to pressure everyone to work faster. But adding capacity at a point that is not the constraint does not improve the overall flow. It only creates more work waiting at the actual constraint. The only intervention that matters is the one that addresses the constraint itself.
Why Working Harder Can Make Things Worse
If the constraint is not addressed, working harder everywhere else can actually make things worse. When upstream steps produce work faster than the constraint can process it, the queue at the constraint grows. More work is waiting. The waiting time for each job increases. From the customer’s perspective, things are getting slower, even though everyone is working harder.
This dynamic explains why some businesses feel perpetually behind no matter how hard they work. The effort exists, but it is not directed at the point that determines how much can actually get done. Until the constraint is identified and addressed, additional effort produces additional waiting, not additional output.
Pressure is not the only misguided response. Improvement efforts can fail for similar reasons.
Local Optimization and Its Problems
Another common mistake is improving individual steps without considering how those improvements affect the whole. A step that becomes faster will produce more output. If the next step cannot absorb that output, the improvement creates a pile-up rather than a gain.
This is the problem of local optimization: making one part of the process better in a way that makes the overall process no better, or even worse. Each local improvement seems sensible on its own terms. The team that speeds up their part of the work is doing their job well. But if the work then sits waiting at the next step, the speed-up produced no benefit for the customer or the business.
Effective improvement requires seeing the whole flow, not just individual steps. The question is not “how can we make this step faster?” The better question is “what is preventing work from moving through the entire process more quickly?” These questions often have different answers.
Seeing the Flow
The concepts in this chapter describe something concrete: the path that work takes through your business. That path has a shape. It has points where work moves quickly and points where work accumulates. It has steps that are well-understood and steps that are ambiguous. Understanding this shape is the first step toward improving it.
You probably have an intuitive sense of where work gets stuck: which steps always take longer than expected, which people are perpetually overloaded, and which approvals create delays. What you may not have is a framework for thinking about these observations systematically: work flows through a series of steps, and the speed of the whole is determined by the slowest step. Effort at other steps does not compensate for a constraint. Local improvements do not help if they do not address what is actually limiting the flow.
The Constraint Is Usually a Person
In most small businesses, the constraint is a person, and more often than not, that person is you. This is common for reasons that should now be familiar: you hold information no one else has, approve decisions no one else can make, and connect systems that do not connect themselves. The next chapter examines what it takes to change that position without losing control of the business.
