When an agency slows down, the instinct is to ask for more — more officers, more civilian staff, more funding. It’s a reasonable instinct and, in most cases, it’s the wrong one.

Adding resources to a constrained system doesn’t accelerate the system. It pads parts that weren’t the problem. The slowdown persists, the investment
disappears and nobody can explain why the needle didn’t move.

The framework policing keeps ignoring

The Theory of Constraints has been applied successfully and extensively in multiple industries for decades. In policing, it is almost entirely absent. That gap explains why recruitment spending keeps rising while pipeline growth stays flat.

Dr. Eliyahu Goldratt introduced it in 1984 with a single uncomfortable premise: every system has exactly one constraint at any given time, and that constraint governs the output of the entire operation. It doesn’t matter how efficient every other step is. The bottleneck sets the pace, and improving anything else first is an illusion of progress.

His five-step process is direct: Identify the constraint. Exploit it — meaning squeeze every unit of capacity out of it before touching anything else. Subordinate everything else in the system to support it. Elevate it. Then repeat, because fixing one bottleneck reveals the next.

The methodology isn’t complicated. What’s hard is convincing leaders to look for the constraint before they start spending. In policing, that’s almost never where the conversation starts.

Where does the system break down? Walk the framework through three operational areas and the pattern surfaces fast.

It doesn’t matter how efficient every other step is. The bottleneck sets the pace, and improving anything else first is an illusion of progress.

Recruitment pipelines

Chiefs who struggle with recruitment volume almost universally respond by expanding advertising, attending more job fairs and increasing outreach. More applications go in the top of the funnel.

The funnel doesn’t move faster.

The constraint is rarely at the top. It’s in the middle: background investigations running three to five months, psychological evaluations backed up by weeks. Candidates get buried in background investigations and psych evaluations.

The diagnostic is straightforward: 

1. Map every stage of your pipeline.
2. Measure average cycle time at each step.
3. Identify where candidates sit idle.

That’s your constraint. Exploit it before spending another dollar on recruiting advertising.

Training throughput

The academy produces recruits. Field training programs certify them for solo patrol. Many agencies have limited FTO capacity because FTOs are assigned elsewhere, on leave or reluctant to take trainees. Graduating more cadets only deepens the queue.

The constraint is FTO availability. Until that is addressed through incentive restructuring, dedicated assignments or patrol load adjustments during training cycles, adding throughput to a backed-up system only extends the wait.

Case management

When clearance rates drop, the ask is almost always for more detectives. Caseload analysis typically tells a different story.

Detectives spend a disproportionate amount of time on administrative work: redundant data entry across non-integrated systems, digital evidence processing queues, paperwork that hasn’t been standardized or delegated. These are process constraints. Adding detectives to a broken workflow doesn’t clear cases faster. It distributes the wait across more people.

The questions to ask are precise: Where do cases sit, and for how long? Which step creates the longest idle period? The answers almost never point to headcount as the primary lever.

Why police leaders don’t think this way

The barrier isn’t conceptual, it’s structural. Police agencies are built around command accountability, not process accountability. Leaders are responsible for their people, not their workflows. When something slows down, the solution defaults to personnel decisions, because that’s the lever the system was designed to pull.

There’s also a political reality. Asking for more staff is easy to budget and easy to audit. It signals responsiveness to city councils and commissioners. It produces a line item anyone can point to.

Saying the agency needs to redesign its background investigation workflow before expanding recruiting advertising is accurate and counterintuitive for many. It requires explaining a concept most public-sector decision makers have never encountered, in a room where the default assumption is that public safety problems are solved by adding more personnel.

So, the path of least resistance wins. Resources get added to the wrong places. The constraint persists. The investment doesn’t produce results, and no one can explain why.

The reason is almost always the same: the wrong step got optimized. 

A diagnostic any leader can apply today

Finding the constraint requires a different set of questions, asked consistently.

Start with throughput mapping. For any operational process, chart every step from initiation to completion and assign an average cycle time to each. Don’t estimate; pull the data. If the data doesn’t exist, that absence is itself diagnostic.

Find where the work accumulates. The constraint isn’t always the slowest step in isolation. It’s the step where inventory builds. In policing, that’s candidates sitting on background decisions, cadets waiting on FTO availability and reports pending supervisor approval.

Before spending anything, ask two questions:

1. Can the constraint’s existing capacity be used more effectively without adding resources?
2. Can upstream and downstream steps be reorganized to support the constraint rather than operating independently of it?

The answers typically require process mapping and cycle time measurement most agencies aren’t structured to conduct internally.

Most of the time, the answer to the first question is yes — background investigators coordinating logistics instead of investigating, FTOs carrying full assigned duties during training cycles, detectives managing data entry that civilians could handle. 

Exploiting the constraint means ensuring the limiting step runs at full useful capacity before anything else changes.

Before the budget conversation starts

The chiefs who get the most from their existing resources share one habit. Before any budget request, before any hiring push, they ask a single question: Is this a resource problem or a process problem?

Most agencies never ask it. The system around them rewards the wrong answer. Headcount requests are easy to budget. Process redesign is not. The constraint gets funded instead, and the slowdown becomes permanent infrastructure.

What that looks like five years down the road is an agency that has added bodies and increased its budget but still can’t explain why response times haven’t improved, why the recruit pipeline stays thin, why clearance rates remain flat. The problem gets reframed as a workforce crisis, a morale crisis, a retention crisis. When the original constraint was never addressed, the system kept running — just slowly. And every cycle of investment reinforced the assumption that more was the answer.

The Theory of Constraints doesn’t require a budget increase to apply. It requires a different question asked before the budget conversation starts. It requires someone in the room willing to look at the workflow before they look at headcount.

The leaders who close that gap don’t wait for the budget cycle to force the question. They ask it first.