From Idea to Impact: Why Good Policing Strategies Fail and How to Make Them Work

Estimated reading time: 12 minutes

When a Good Idea Meets Real-World Policing

A mid-sized police department finally gets the green light to build a Real-Time Crime Center (RTCC). Command staff is excited. Patrol is hopeful. City leaders want to “become more data-driven.” They’ve seen other cities talk about how their RTCC improved case support, response, and situational awareness.

So now comes the big question:

“How do we roll this out so it actually works for us?”

This is usually where agencies start taking very different paths.

Some launch the RTCC without a clear plan. Some piece it together as they go. Some copy what a nearby agency did. Others pick and choose parts of different models and hope it all fits.

And this is where frustration begins.

Because most practitioners have seen some version of this:

“We tried something that worked great in another department… and it didn’t work the same way here.”

It’s not because the idea was bad.

It’s because the implementation didn’t match the agency’s context such as its people, resources, expectations, or community.

That’s where Implementation Science comes in.

What Even Is Implementation Science? (And Why Should Policing Care?)

Let’s keep it simple:

Evidence-Based Policing (EBP) = It tells you what research has shown works (e.g., hotspot policing, crisis‑response programs, procedural justice training)

Implementation Science (IS) = It helps you understand how to make those practices actually work in your department (e.g. given local staffing, culture, community expectations, resources, and organizational history)

EBP helps agencies choose interventions supported by evidence like hot spots policing, focused deterrence, or expanding a crisis response team, etc. But policing rarely studies the step between hearing about a strategy that worked somewhere else and actually getting it to work in your own department.

That middle part – the messy part – is where most evidence-based reforms fail.

IS is the field that studies how to adopt and adapt evidence-based practices so they make sense in the real world. Medicine uses it all the time. Policing… not so much.

IS looks at:

• leadership support
• local culture
• officer buy-in
• community expectations
• staffing realities
• whether the intervention can be tweaked
• whether people even like the new practice
• what happens after the “pilot phase” is over

In short:

IS explains why something that worked beautifully somewhere else might fall apart in your agency and how to prevent that.

The Article: A Practical Guide to Bringing Evidence Into Police Practice

The article by Brandon del Pozo, Steven Belenko, Ekaterina Pivovarova, Bradley Ray, Kaitlin Martins, and Faye Taxman isn’t a traditional research study. It’s more of a starter guide, a collection of frameworks, lessons from healthcare, and practical tools for blending EBP with Implementation Science.

It walks through:

• how IS developed in healthcare
• how those principles translate to policing
• how two major frameworks (CFIR and EPIS) help police actually implement EBP
• why agencies need to measure things they normally ignore (like acceptability or feasibility)
• why both effectiveness and implementation matter
• how IS can help de-implement bad or outdated practices

Think of it as a “how to” manual for not wasting time or money on reforms.

Using IS to Implement Good Policing Strategies

1. A good idea isn’t enough. Context matters.

A strategy or tool won’t automatically work just because it worked somewhere else. Agencies need to look at the conditions that will help or hinder success which includes things like staffing, community expectations, policies, union rules, and leadership priorities.

Example:

Suppose a department wants to launch a drone program. One of the things IS would direct the agency to examine is its staffing before moving forward. Key questions might include:

• Do we have personnel with the right skill sets?
  For example, are there officers or civilian staff who already have experience in aviation systems, evidence collection, or real-time operations?
• What training and certifications are required?
  Does the department have enough staff who can obtain FAA Part 107 certification? How long will that take, and who will cover their regular duties in the meantime?
• How will staffing patterns need to change?
  Will drone operations be a collateral duty or a dedicated assignment? Does the agency need a 24/7 on-call roster, and can current staffing support that?
• What supervision and support roles are needed?
  Who will oversee policy compliance, equipment maintenance, and quality assurance? Are supervisors prepared for these responsibilities?
• Is there sufficient capacity to sustain the program long-term?
  If a few key staff leave, does the program fall apart? Is there a plan to train additional operators?

A drone program that looked seamless in another city may struggle in a department that lacks the staffing structure, training capacity, or supervisory support to run it effectively. Understanding these factors upfront increases the likelihood that the strategy can be implemented and sustained successfully.

2. IS helps agencies test ideas on a small scale with less risk.

Policing is understandably cautious. IS recommends that agencies test programs in structured phases, gradually expanding as evidence of success emerges. Instead of rolling out a full program, agencies can test it in a limited area or timeframe and evaluate whether it’s actually workable.

Example:

If a department wants to implement body-worn cameras, IS would suggest starting with a pilot that focuses on whether day-to-day workflows are actually feasible. A small-scale test in one patrol district might examine questions such as:

• Are upload and docking workflows realistic?
  Do officers have enough time at the end of shift to dock cameras and upload footage without delaying shift turnover?
• Is evidence management manageable?
  Can records staff keep up with tagging, categorizing, and responding to discovery requests during the pilot?
• Are supervisory review processes workable?
  Do sergeants have the time and tools to complete required audits without overwhelming their workload?
• Do current policies align with operational reality?
  Are activation rules clear and practical, or are officers routinely running into ambiguous situations?
• Can IT support the system reliably?
  Are there bottlenecks with storage, integration with RMS/CAD, or wireless upload capacity?

By testing and refining workflows on a small scale, agencies can identify necessary adjustments, address barriers early, and make informed decisions before investing in a full-department rollout.

3. IS has agencies measure the things policing usually ignores

To understand why something worked (or didn’t), agencies must track:

• Feasibility: Can we actually do this with our current staffing and systems?
• Fidelity: Are we doing the strategy the way it’s intended?
• Appropriateness: Does this practice meaningfully address the problem we are trying to solve?
• Adoption: Are officers and supervisors actually using it?
• Acceptability: Do officers, community members, and leadership support the change?
• Sustainability: Can we maintain this over time?
• Penetration: To what extent has this practice become part of routine operations across the agency?
• Cost: What time, money, or workload does it require?

Examples of how to track these:

• Random audits of reports or videos to see if the strategy is being used.
• Short officer surveys after pilot shifts.
• Call logs or CAD data to see if co-responders are being requested.
• Monthly supervisor check-ins to document barriers.
• Tracking overtime or training costs tied to the program.

4. IS makes EBP more officer-friendly

Many officers feel Evidence-Based Policing doesn’t understand their realities with small shifts, rural environments, thin staffing, or unique community dynamics.

IS recommends to directly addresses this by building local context into every step. Instead of forcing a strategy “as-is,” IS asks:

• What barriers do officers face?
• What adaptations make sense here?
• How do we maintain core elements while adjusting to reality?

Example:

Suppose a department wants to implement a hot spots policing strategy focused on high-visibility patrols. In a rural area, the primary barrier may be long distances between hot spots, making foot patrol impractical.

Adaptation: Officers conduct short, targeted vehicle-based patrols in the identified hot spots rather than sustained foot patrol.

Core principle maintained: The strategy still focuses resources on high-crime areas to prevent incidents, preserving the evidence-based intent while fitting the department’s operational reality.

5. IS can help stop outdated or harmful practices

Implementation isn’t only about adding new programs. It also gives agencies tools to evaluate and wind down practices that don’t work or cause harm.

Example:

Suppose a department is reviewing its use of no-knock warrants after data shows they increase risk to both officers and civilians without improving case outcomes. An IS approach would guide the agency through several steps:

1. Assess the problem: Review outcomes, injuries, and complaints from past no-knock warrants.
2. Engage stakeholders: Talk with officers, leadership, legal staff, and the community about risks and concerns.
3. Plan reduction: Phase out high-risk warrants and update policies and procedures.
4. Monitor impacts: Track arrests, safety outcomes, and community feedback during the phase-out.
5. Support officers: Provide training on alternatives and create opportunities for feedback.

This approach helps the department safely reduce harmful practices while maintaining officer and public safety.

6. IS helps agencies build reforms that last beyond leadership turnover.

Most police chiefs stay only a few years. Programs that rely on one champion often disappear when leadership changes.

IS recommends agencies build structures (policy, training, supervision, data tracking, and budgeting) that keep reforms alive.

Example:

If an agency adopts a drone program, sustainability might include:

• Embedding drone training into the academy
• Adding annual recertifications
• Writing clear policy
• Setting aside a budget line for equipment
• Including drone performance metrics in annual reports

This makes the program durable, no matter who the next chief is.

7. Implementation is not a one-and-done. It’s a cycle.

IS frameworks help agencies plan for change. The two mentioned in the article were:

• EPIS (Exploration → Preparation → Implementation → Sustainment)
• CFIR (Consolidated Framework for Implementation Research), with over 50 contexts to assess through it helps agencies truly identify the factors that support or hinder implementation.

These models give agencies step-by-step guidance on how to explore ideas, prepare for rollout, support staff during implementation, and keep the program running long-term.

Case Study: How Our RTCC Agency Should Actually Use IS

Let’s go back to our fictional agency building an RTCC.

Here’s how they’d apply IS across the full EPIS cycle:

1. Exploration: Should we even do this?

• What problem are we trying to solve?
• Do we have the staffing?
• What does our community think about increased surveillance?
• Are officers asking for more intel support?
• What’s the evidence from other RTCCs and how similar are we?

Concrete step: Run focus groups with dispatch, patrol, detectives, and community stakeholders.

2. Preparation: If we do this, how do we do it well?

• Identify barriers (tech literacy, staffing shortages, union issues, legal policies)
• Identify facilitators (strong IT team, analytical support, city funding)
• Develop training, policies, supervision structure
• Plan a pilot before going agency-wide

Concrete step: Create an RTCC “playbook” outlining workflows for intel support, data requests, and case follow-up.

3. Implementation: Start small, measure everything

• Pilot with one shift or one district
• Collect data on adoption (are officers actually using RTCC?)
• Track feasibility (does staffing allow it?)
• Track acceptability (do officers trust the intel?)
• Track service outcomes (does intel actually help investigations?)

Concrete step: Have sergeants review cases where RTCC intel should have been requested but wasn’t and ask why.

4. Sustainment: Keep what works, adapt what doesn’t

• Integrate RTCC workflows into policy
• Evaluate long-term staffing needs
• Institutionalize training
• Set up continuous quality improvement
• Celebrate wins publicly and internally

Concrete step: Add RTCC utilization and quality metrics into annual performance reviews.

Final Thoughts: Implementation Science Isn’t Extra Work. It Is the Work

Most police agencies want to innovate. They want to reduce harm, strengthen trust, improve investigations, and adopt strategies that actually work.

But too often:

• reforms feel chaotic
• pilots die with leadership turnover
• programs fail without anyone knowing why
• officers feel disconnected from the change
• communities feel left out

Implementation Science offers a roadmap that helps agencies translate good ideas into context-appropriate improvements aligned with the community, the agency’s culture, and the realities of police work.

If EBP tells you what to do, IS tells you how to make it work here.

It’s not glamorous. It’s not a quick win. But it’s the difference between innovation that sticks and innovation that never gets off the ground.

For more research‑based insights on how to move policing beyond reactive responses and build strategies patrol officers actually use, check out:

4 Research-Backed Tips for Proactive Policing

Rolling out a proactive policing plan but seeing little traction? Research reveals the 4 key steps that get officers to do more on the street.

Enjoyed this post?

Get more research translated into plain language delivered straight to your inbox twice a week.

Subscribe below and let me know which topics you want to hear more about. It only takes a minute.

If you found this helpful, share it with your team or on your socials. It helps more people make sense of research that matters.

Carlee Ruiz

Carlee Ruiz is the founder of PoliceResearchHub, a platform that turns academic research into practical insights for law enforcement. She brings seven years of experience as a crime analyst and justice researcher, with a focus on evidence based policing, gun violence prevention, and public safety strategy. Carlee currently works as a researcher at National Policing Institute, where she supports evaluations of law enforcement programs and criminal justice initiatives across the country. Through PoliceResearchHub, she aims to make research easier to understand and more useful for the people doing the work on the ground.