← All Posts

What You Allow Becomes the Standard

Secret Service agent in a dark suit and earpiece standing against a wood-paneled wall, his shadow on the wall beside him.

A protection detail can complete every assignment, satisfy every client, and still be getting worse at its job.

That's the danger of measuring security by whether something bad happened. An uneventful day doesn't mean the work was done correctly. Sometimes it means nobody was tested.

Standards rarely drop on purpose. They slip through small things that go unchallenged: a late arrival, an abbreviated advance, a missed update. Each one passes because the assignment ends without incident, and each makes the next one easier to accept.

The quickest way to lower a team's standards isn't to change the rules. It's to stop enforcing them.

What you allow becomes the standard.

The Actual Standard

During my time with the Secret Service, calling in sick for a protective assignment was close to unheard of. Agents got sick. But if you were ill, you reported for duty and let the detail leader decide whether you went home. The decision about whether the standard bent belonged to the person responsible for the team, not to the individual. It never eroded, because it was held by shared expectation long before anyone had to correct it.

Most teams rely on standards on paper: reporting times, communications procedures, vehicle plans, advance requirements. The actual standard is the level of performance the team has learned will be accepted.

If the report time is 0700 but arriving at 0708 is routinely ignored, 0700 is not the standard. If an advance is required but a rushed phone call with the venue keeps getting accepted, the definition of an advance has changed. If changes are supposed to reach the entire detail but people rely on word eventually getting around, the communications plan exists only on paper.

People figure this out fast. They watch what gets addressed and what gets ignored, and they take their cues from that, not from what the leader says about high standards.

Holding a standard rarely looks dramatic. It's addressing the late arrival when it happens. It's asking why something wasn't checked. It's telling someone to move the vehicle because that isn't where the team agreed it would be. It's making sure an important update actually reaches everyone.

Those conversations are easy the first time. After six months of the same behavior being accepted, they get hard, because the person being corrected has a legitimate question. Why is this suddenly a problem?

The honest answer is that it always was. Leadership allowed it to become normal.

Accountability Goes Both Ways

Leaders set expectations and have the authority to enforce them, but accountability doesn't stop with the person in charge.

Experienced agents shape a team's culture more than they realize. Newer personnel watch what the veterans take seriously and what they're willing to overlook. An agent who arrives prepared and finishes the unglamorous parts of the job reinforces the standard without saying a word. One who relies on reputation to excuse a shortcut sends an equally clear message.

The same goes for the leader. One who demands punctuality but arrives late has weakened the standard. One who insists on thorough advances but pressures people to abbreviate them has done the same. And one who overlooks a favored or experienced agent's lapses shouldn't expect anyone to believe the rules apply equally.

It also has to run upward. If the operations plan says one thing and the team has gradually started doing another, someone should be able to say so. If an agent sees something being missed, he should raise it. If the detail leader makes a bad call, experienced members should be able to challenge it professionally. A team where accountability only travels downhill isn't accountable.

This gets harder as teams grow familiar with each other. Nobody wants to be the difficult one, especially when the person cutting the corner is otherwise highly capable. So the small thing gets ignored. Then it gets ignored again. Eventually nobody thinks of it as unusual.

That's how degradation happens.

Standards Versus Preferences

Maintaining standards doesn't mean controlling every decision or requiring every agent to do a task exactly as the leader would.

There may be several perfectly good places to stage a vehicle. An experienced agent may see a better way to handle a movement. Conditions change, and a good plan sometimes has to change with them. A leader who treats every personal preference as a mandatory standard creates friction and a team that waits for instructions instead of using its judgment.

Tie the distinction to the mission:

  • Does it affect the team's readiness?
  • Does ignoring it interfere with another team member's responsibilities?
  • Could it delay moving the protectee if something changes?
  • Does it create a vulnerability or eliminate an option the team expected to have?

If the answer to any of these is yes, enforce the standard. If the answer to all four is no, it's a preference, and the team should have the flexibility to handle it differently.

Standards can also outlive their usefulness. Technology changes, resources differ, lessons are learned. A leader may decide a requirement no longer earns its place and retire it. That's a decision, made on purpose by the person responsible for the team. Drift is not. The problem isn't that standards change. It's that they change without anyone acknowledging it.

"Nothing Happened"

Those may be the most deceptive words in the business.

We shortened the advance and nothing happened. The driver was late and nothing happened. We skipped the briefing and nothing happened. We had no meaningful alternate plan and nothing happened.

The absence of a consequence doesn't tell you whether the decision was sound. It may only mean the weakness was never tested.

Protection work is mostly preparation for things that may never occur. Alternate routes may never be used. Emergency plans may never be activated. A medical kit may stay sealed for years. That doesn't make the preparation unnecessary. It means maintaining it takes discipline when there's no immediate reward.

That discipline is a leader's job. Set reasonable standards and explain why they exist. Address deviations before they become routine. Accept correction yourself. Give experienced people room to operate without confusing flexibility with lowered expectations.

A protection detail rarely wakes up one morning and decides to become less disciplined. One shortcut works, so it's repeated. One exception becomes several. What once would have been corrected becomes ordinary.

Eventually, the team is no longer operating below its standard.

It has established a new one.

Every engagement starts with a conversation.

Begin a Conversation →