The Dangers of Institutional Consensus

Download The Dangers of Institutional Consensus white paper

The most dangerous words in law enforcement are “we’ve always done it this way.”

I’ve heard them in agencies of every size, and I’ve watched the mindset behind them take hold in every bureaucracy I’ve worked with. It rarely shows up as a bad decision. It shows up as a habit nobody questions anymore, defended by people who’ve forgotten there was ever a choice involved.

How a Good Idea Hardens Into a Rule

Most bad practice starts as good practice. Someone faces a real problem and finds a fix that works. It works again, so a few more people use it. Word gets around. Within a couple of years the fix has a name, a paragraph in the policy manual, and a slot in the academy block. That’s usually where the trouble starts.

Once a practice becomes the standard, the reasoning behind it begins to fade. People learn the what and skip the why. The officer who built the fix retires. The supervisor who understood the tradeoff moves on. New officers inherit the rule with none of the context that made it smart in the first place. Ten years later you’ve got a department full of people running a procedure none of them can explain, and a culture that treats the question “why do we do this” as a sign of inexperience instead of leadership.

The academy and the field training process are where this locks in. A new officer learns a procedure from a trainer who learned it from a trainer, and somewhere up that chain the reason got dropped. By the time it reaches the street it’s muscle memory with no memory attached. That’s not a knock on training. Training is how a department moves knowledge at scale. But the same machinery that spreads good practice spreads unexamined practice just as fast, and it can’t tell the two apart on its own.

I call that institutional consensus. It’s the point where a practice stops being a decision and becomes furniture. Nobody picked it. It’s just there, and moving it feels like remodeling. The bigger the organization, the heavier that furniture gets, because more people have built their routines around it and more careers depend on it staying put.

Wisdom or Group Thinking

Here’s the part that makes this hard. Consensus isn’t always wrong.

Sometimes it’s wisdom built through years of experience, the distilled judgment of people who’ve run the same call a thousand times and learned what gets officers and citizens home. That kind of agreement is earned. Ignore it and you’ll relearn old lessons the expensive way.

Sometimes, however, it’s simply group thinking. The practice survives because no one wants to be the person who challenges it, not because anyone’s checked lately that it still works.

The challenge is knowing the difference, and from the outside the two look identical. Both produce the same confidence “that’s how we do it.” Telling them apart takes a few honest questions.

Ask why a practice exists. If the answer is a specific story about a specific outcome, you’re probably looking at wisdom. If the answer is “that’s policy” or “that’s how I was trained,” you’re looking at consensus that stopped thinking a while back. Earned wisdom can explain itself. Inertia gets defensive, usually because the people defending it don’t actually know the reason either. They just know it’s always been there, and the question feels like an attack.

Age is another tell. A practice written for a problem that no longer exists deserves a fresh look. Body cameras changed what gets recorded. Cell phone video changed who’s watching. Case law shifted, and what a community will tolerate shifted with it. A policy written in 2005 was written for a different country, and plenty of them never got revisited.

Why Questioning Costs Something

If spotting calcified consensus were the whole job, this would be easy. It isn’t, because questioning it has a price, and most people weigh that price long before they weigh the policy.

The officer who asks “why” usually pays for it. They get labeled difficult, or naive about how things really work. In a lot of agencies the safest career move is to keep your head down and run the play that’s already called. So the people closest to the problem, the ones who can watch a practice fail in real time, learn to stay quiet. Their silence reads as agreement. The consensus looks even more solid than it is, which makes the next person even less likely to speak up.

That’s the quiet machinery of bad policy. It doesn’t survive because everyone believes in it. It survives because the cost of saying so lands on one person while the cost of staying quiet gets spread across the whole department, paid later; usually by somebody on a bad call at two in the morning.

A leader’s job is to flip that math. Make it safe to ask why. Reward the deputy who brings you a problem instead of burying him for it. The agencies that stay sharp aren’t the ones with the best policies on paper. They’re the ones where people still feel free to question them.

Borrowed Policy Doesn’t Travel

The clearest place consensus breaks down is when one agency copies another.

Take a policy that works well in a 2,000-officer metro department. It was built for that world. High call volume, specialized units, a deep bench, mutual aid a few minutes out, a training budget that can absorb a new mandate without flinching. Move that same policy into a 12-officer rural agency and the outcome changes completely.

The calls are different.

The community is different.

The resources are different.

In the metro department an officer might never work a shift alone. In the rural county, one deputy may cover an area the size of a small state with his nearest backup forty-five minutes out. A pursuit policy or a staffing model that quietly assumes resources the small agency doesn’t have isn’t a higher standard. It’s a rule that can’t be followed. And a rule your people have to break on their first bad night is worse than no rule at all, because now you’ve trained them to treat the manual as fiction.

So why would the solution be the same?

It gets copied anyway. A model policy circulates. A consultant recommends it. An accreditation checklist rewards it. A department adopts a practice built for a place that looks nothing like home and calls it best practice. Best for whom? Built for what conditions? Those questions get skipped, and the consensus rolls downhill into a hundred agencies that never asked whether it fit.

There’s a logic to the copying, which is what makes it stick. Adopt the same policy as the department next door and the agency two counties over, and if it ever lands in court you can point to it as the accepted standard. That’s real cover, and no chief gets fired for matching everyone else. But “everybody does it” is a legal defense, not an operational answer. It tells you the practice is common. It tells you nothing about whether it works on your ground.

Thinking From First Principles

The fix isn’t to throw out everything that came before. That’s just recklessness with better marketing. The fix is to think from first principles.

First-principles thinking means stripping a problem down to what you actually know is true and building back up from there. Not “what does the model policy say,” but “what’s the problem I’m solving, what outcome do I need, and what do I really have to work with.” You start from your own ground instead of from somebody else’s .

Run a pursuit policy through that filter. The problem isn’t “we need a pursuit policy.” The problem is that vehicle pursuits get people killed, and so does letting violent people drive off into the night. The outcome you want is the fewest dead and injured across both of those failures, given your roads, your traffic, your population, your air support or lack of it, your dispatch, and the training your officers actually have. A department with a helicopter and four-lane highways will land somewhere different than a department with gravel roads and no air. Both can be right. Neither got there by copying the other.

That’s the line between borrowing a policy and translating one. Borrowing takes the answer and hopes it fits. Translating takes the reasoning and re-solves the problem for your own ground. It’s slower. It’s also the only version that holds up when a real incident tests it.

You can run almost any decision through the same filter. A new training mandate, a body-camera retention schedule, a use-of-force reporting process, a shift bid. Strip it to the problem and the outcome. Look hard at what you actually have. Then decide. Most of the time you’ll keep a good deal of what you inherited, but now you’ll know the actual reasoning, and you’ll be able to tell your people why; which is most of what they subconsciously needed from you in the first place.

None of this is fast, and that’s the honest cost. Translating a policy takes more work than downloading one, and the work falls on people already short on time. But you pay either way. You pay up front, thinking it through, or you pay later, when a policy built for somewhere else fails on a call it was never designed for. The first bill is smaller, and you get to pick when it comes due.

Write Down the Why

Here’s a practical move that fights all of this. When you adopt a practice, write down the reasoning, not just the rule.

Most policy manuals record the what. Do this, don’t do that, in this order. Some do not record the why: the problem it solved, the conditions it assumed, the tradeoff it accepted. So the rule outlives its reasoning by default. Ten years on, the procedure is still in the binder and the logic that justified it left with the people who wrote it.

Capture the reasoning and you give the next generation something to test against. When the world changes, and it will, they can look at the original conditions, see that they no longer hold, and revise on purpose instead of by accident. You also make it harder for a practice to hide behind “that’s just how we do it,” because the answer to “why” is right there in writing where anyone can check whether it still holds up.

It costs an hour now and saves you a decade of accumulated nonsense later. Wise agencies do it. The agencies that do are the ones whose policies still make sense to the people following them.

You Can’t Question Everything

I’ll grant the obvious pushback. A patrol shift can’t pause to re-litigate every policy in the manual, and a department where every officer runs his own version of the rules isn’t thinking from first principles. It’s chaos with extra steps. Discipline matters. When the call is live, you run what you trained and sort out whether it was right at the debrief.

That’s the whole point. The questioning belongs in the right room at the right time. That room is the policy review and the after-action, where the command staff who own the manual can do the work deliberately. It doesn’t belong to the newest officer improvising in a doorway at two in the morning. Building a culture that questions practice isn’t the same as tolerating freelancing. It means the people responsible for the rules treat them as decisions that have to keep earning their place, and it means the officer who watches a rule fail has somewhere to take it.

A good agency runs disciplined and thinks critically at the same time. The discipline keeps the operation safe tonight. The questioning keeps it safe ten years from now, when the conditions a rule was written for have quietly changed and nobody filed the update.

The One Question

Every leadership decision I’ve watched go well started from the same question.

Is this what’s best for the community we serve?

Not what’s easiest to defend in a deposition. Not what the department down the road happens to do. What actually serves the people who live here, on these streets, policed by these officers, under these conditions.

That question sounds simple. It isn’t. It forces you to know your community well enough to answer it, which means knowing the gap between the place a policy was written for and the place you actually work. Most bad decisions in this profession come from skipping that question, or from assuming somebody upstream already answered it for you. Usually nobody did.

What Task Force 70 Is For

That question is the reason I built Task Force 70.

We don’t exist to tell agencies what to do. There’s no shortage of people willing to sell the chief an answer in a binder. We’re not in that business. We exist to help police chiefs, sheriffs, command staff, and the frontline leaders under them think through their own problems from first principles.

Every community is different, and the people who understand a community best are the officers and leaders who serve it every day. They don’t need an outsider to hand them a conclusion. What helps is a structured way to pressure-test the conclusion they’re already moving toward, to surface the assumption they’ve stopped questioning, to pull the hard-won wisdom in their consensus apart from the inertia sitting next to it.

Our job is to help them make better decisions. Not to make the decisions for them.

Conclusion

Consensus isn’t the enemy. Unexamined consensus is. Every agency runs on practices it inherited, and most of them are worth keeping. The job of a leader isn’t to tear them down or to defend them on reflex. It’s to know which is which, and to keep asking “why” long after everyone else has stopped. That’s the difference between a department that adapts to the community in front of it and one that’s still policing a community that moved on years ago.

About the Author

John Chapman, known widely as Chappy, is a law enforcement professional with over 34 years of experience in operational, leadership, doctrinal development, applications engineering, and training roles. He is a published author and has specialized in the development and delivery of patrol and tactical law enforcement curriculums for over 28 years. Chappy is the Executive Director of the Task Force 70 Foundation, a non-profit organization focused on training, mentoring, and educating underserved rural and small-town law enforcement officers and agencies across the United States. Information and contact info can be found at TF70.org.