Policing doesn’t fail for lack of big reforms. If anything, policing has had more large-scale reform attempts than nearly any other profession in America. Commission reports, consent decrees, federal reviews and task forces. Every few years, a new banner gets unfurled, and chiefs are told this is the fix.

Then the spotlight moves and nothing changes. Officers keep grinding under the same pressures. The public sees little difference, and leaders are left with yet another binder of recommendations gathering dust.

The problem isn’t that reforms are poorly intentioned. The problem is that policing keeps trying to solve a chronic issue with acute solutions. Big dramatic changes that require perfect conditions, sustained political will, uninterrupted funding and long-term attention.

Policing never gets those things, and even when it does, frontline realities stay home. Recruiting pipelines shrink, supervisors juggle too many priorities, systems stay outdated and workloads outpace staffing.

Under those conditions, even the best reform will buckle.

Task forces create compliance. What policing actually needs is capability. Capability doesn’t come from the next big initiative. It comes from what Toyota figured out decades ago.

What Toyota understands that policing doesn’t

Toyota didn’t become the most reliable automaker in the world because of one brilliant decision. They did it by making thousands of small ones. Every day, by everyone.

The difference wasn’t tools or flowcharts. It was culture. Continuous improvement isn’t an event, it is the expectation. Every employee, regardless of rank, could identify inefficiencies and test solutions. Leaders measured success by whether the work got easier, faster, safer or more consistent.

As a result, small changes get stacked up, problems get solved by the people closet to them and systems got better instead of stuck.

Toyota’s philosophy doesn’t depend on political cycles, national attention or once-a-decade overhauls. It survives because it’s designed to outlast all of them. 

That’s what policing needs. Not another task force, but a system where improvement is constant, expected and owned by the people doing the work.

Why policing resists

If continuous improvement works, why hasn’t it taken root in policing?

Because policing operates on a cycle of urgency and exhaustion. Agencies spend so much time reacting there’s no space to redesign. Every reform comes from outside pressure — a viral incident, consent decree, a federal monitor. Change becomes something done to them, not by them.

But the biggest obstacle isn’t time, it’s belief. The belief that real improvement only comes from above. This belief gets reinforced every time change arrives as a mandate instead of an opportunity. Every time an external review produces recommendations agencies didn’t ask for. Every time progress gets measured by compliance with someone else’s checklist instead of capability to solve their own problems.

Looking upward feels safer than looking inward. It diffuses accountability. If the reform fails, “It wasn’t our idea.” If it succeeds, “We followed orders.” But that safety comes at a cost. Agencies never build the muscle to improve themselves.

Continuous improvement flips that assumption. It assumes the people closest to the work know best how to fix it. Instead of looking upward for reform, it looks inward for opportunity.

The three factors that determine success

Every organization knows what needs to happen. Map processes. Find waste. Test changes. Standardize what works. The concept isn’t the barrier.

But understanding the concept and sustaining it are entirely different things. Some organizations embed this and watch it transform operations. Others try it, get early wins, then revert to old patterns within six months.

The difference comes down to three factors. Organizations that have all three sustain change, while organizations missing even one don’t.

1. Distributed authority (not centralized programs). Organizations that sustain improvement don’t create “lean teams” or “process improvement units.” They make it part of every supervisor’s job.

   When a sergeant sees a bottleneck in report approval, they don’t submit it to a committee. They map it, test a solution, and report results. Maybe that means eliminating one signature that adds three days to every report. Maybe it means shifting approvals to the next shift instead of waiting for a specific supervisor. The solution matters less than who owns finding it.

   When a lieutenant watches recruits wait weeks for background updates, they don’t wait for HR to fix it. They convene the stakeholders and redesign the workflow.

   This isn’t about adding work. It’s about redefining what leadership means. Leaders don’t just manage people. They remove obstacles, and they’re accountable for whether work got easier, not just whether it got done.

   Organizations that fail treat improvement like someone’s special project. It becomes an initiative with a launch date, a committee, and eventually a quiet death when priorities shift.

2. Rapid learning cycles (not annual reviews). The best organizations don’t wait for quarterly reviews or annual audits to know if something works. They build feedback directly into operations.

   If they remove an approval signature from a hiring workflow, they known within two weeks if turnaround times improved. If they introduce new field training documentation, they check in weekly with FTOs to see if it’s actually easier or just different.

   Bad ideas die quickly. Good ideas spread before momentum fades.

   Organizations that struggle treat every change like a policy revision. This means months of deliberation, approvals at multiple levels, and formal announcements. By the time they know if it worked, the people who championed it have moved on.

3. Failure tolerance (not blame culture). This is the hardest shift. Organizations that sustain improvement kill what doesn’t work and move on. No defending the decision. No “let’s give it more time.”

   This creates a culture where experimentation is safe. People will only test new ideas if they know they won’t be blamed when those ideas don’t work.

   Organizations that revert do the opposite. They either cling to ineffective changes because someone important championed them, or they use one failure as proof that “this improvement stuff doesn’t work here.” Then people stop trying.

What this creates

Culture isn’t built through initiatives. It’s built through repeated behavior.

When people see that problems get addressed quickly, improvements don’t require permission, leaders remove obstacles instead of creating them and that small wins stack, momentum builds itself. 

That momentum is what separates organizations that build capability from organizations that just check compliance boxes.

The bottom line

Policing has been chasing the wrong thing. Compliance is what task forces create. It’s measurable, it’s auditable and it satisfies external pressures.

But compliance doesn’t make the work easier. It doesn’t reduce burnout. It doesn’t fix broken processes that waste hours every week. It doesn’t build the organizational muscle to adapt when conditions change.

Capability does.

The organizations that build capability don’t wait for the next reform mandate. They don’t wait for funding, and they don’t wait for permission. They start Monday morning with one broken process and the authority to fix it.

That’s what Toyota built. That’s what policing can build. Leaders need to stop treating improvement like a special event and start treating it like part of the job.

Last thing, and the most important one, too: For just a moment, consider how admin buy-in would embolden everyone you work with. New efficiencies would multiply effectiveness, and hope will finally take hold. So, whether it’s your cover-
memo attached to this article sent to the chief by way of chain of command, or maybe your union making a formal request for consideration, right now, decide how you will pursue implementation.

Reform is episodic. Improvement is every day. Start now.