Idle and overloaded at the same time

There's a company just past ten people where the leadership team works systemic overtime, and where, on any given afternoon, someone is sitting idle, waiting to be told what to do next.

Both things are true at once. The founder wrote them down three questions apart on a diagnostic without noticing the collision: "not enough people for how much we want to do," and, a page earlier, teams that need constant guidance and check-ins to make plans and stay on track.

Hold those two sentences next to each other. If the company of that size were actually short on people, nobody would be idle. Everyone would be saturated with clear work and delivery would still slip, purely on volume. That's not what's happening. The work exists, the people exist, and the thing connecting them, a decision about what to do next, is stuck behind an invisible wall.

Eliyahu Goldratt built a whole discipline, the Theory of Constraints, around one observation: every system has exactly one constraint at a time, and the throughput of the whole system is set by it. Adding capacity anywhere except the constraint changes nothing. His examples were factories, but the logic doesn't care what the machines are made of. You find the constraint the same way on a shop floor or in a tech company: find the clog. Where does work pile up waiting?

In this company, and in most companies that describe themselves this way, the clog forms in front of leadership. People aren't waiting for materials, budget, or tools. They're waiting to be convened. Waiting for the plan to be blessed, the priority to be confirmed, the next piece of work to be assigned. The constraint isn't headcount. It's leadership attention.

Here's why the contradiction survives so long without anyone naming it: waiting wears a costume. Nobody sits with folded hands until the next decision arrives. They fill the gap with something, inbox, tidying, a third polish pass on work that was already fine. The waiting gets silently absorbed into the appearance of busyness, so it never shows up anywhere. Leadership's overload, meanwhile, is extremely visible: they're the ones answering messages at midnight. The company sees one half of the picture and writes its story from it. Everyone is maxed out. We need to hire.

That story is the expensive part, because hiring is one mistake that makes this worse. A new hire arrives needing the one resource the company has least of. They need direction, context, decisions, check-ins, all drawn from the same pool of leadership attention that was already the bottleneck. You've added demand to the constraint and booked it as capacity. Six months later the overtime is worse and the payroll is bigger. The prediction is uncomfortable but reliable: when leadership attention is the constraint, headcount growth slows the company down before it speeds it up.

The counter-evidence usually sits in plain sight, and it did here too. When a decision didn't have to wait, the company moved fast. A minor internal policy came up one morning, was decided the same day, and rolled out within three. Nothing about this company is slow. Decisions it makes are quick and clean. Decisions waiting to be made are where all the time goes. That distinction matters, because it means the fix isn't "get better at deciding." The deciding works. The access to it doesn't.

Goldratt's answer to a constraint you can't instantly remove: exploit it, then subordinate everything else to it. Translated out of factory language, stop spending leadership attention by the drip, on whoever happens to catch someone in a hallway or a chat thread, and start spending it in deliberate, scheduled doses. Two mechanisms that I recommend do mooooost of the heavy lifting.

The first is a greenlight session: one recurring, bounded meeting where the queued decisions actually get made, and every decision leaves the room with a name and a date attached. Not a status meeting. Status can move to writing. This session exists only to convert waiting into direction, and its rule is that nothing leaves undecided; the allowed outputs are yes, no, or not-yet with a specific revisit date. Name the owner and you can predict the follow-through.

The second is gating your intake. If everything that gets started must pass through the session, the system gains something it never had: a place where "not yet" can be said by a rule instead of a person. Most small companies start work the moment it's imagined because no mechanism exists to hold it. The gate is that mechanism, and it protects the constraint from the thing that floods it fastest, which is new work nobody finished deciding about.

This, of course, assumes people are waiting on decisions. If they're waiting because they don't know how to do the work, rather than which work to do, you have a capability gap, and no amount of decision hygiene will fix it. The two look similar from a distance. The test is cheap: for one week, whenever someone is between things, write down what exactly they were waiting for. If the list is full of "confirmation," "approval," "the meeting," it's attention. If it's full of "help," it's skills. And if it's attention, you should see the line visibly shorten within two to four weeks of the first greenlight sessions; if it doesn't, the diagnosis was wrong, and the week of notes will tell you where to look instead.

This leader's instinct, "not enough people," wasn't foolish. It's the natural reading when everyone looks busy and everything is late. It just aims the money at the wrong spot. Before you write the job posting, spend the week watching what people are actually waiting on. Companies are usually not short of hands. They're short of identified work to put in them, and that's not a hiring problem. That's the operating system begging for an update.