On a regional call, the same slide shows up every quarter. “Execution is inconsistent.” Someone proposes the familiar fix: tighter standards.

A dealer principal responds with the equally familiar pushback: “If you tighten this any further, my team will stop doing it altogether.”

Both statements can be true at the same time. Networks don’t fail because they lack standards. They fail because standards are designed as if the network will comply, rather than as if the network must adopt.

Consistency at scale does not come from controlling dealers. It comes from defining a small execution spine that dealers can accept, then building governance that protects that spine under pressure.

Tight standards trigger the very variance they are meant to reduce

When performance disappoints, central teams often add detail. More steps. More required fields. More mandatory scripts. More reporting. It feels rational because the process becomes more specific.

In dealerships, it often produces the opposite outcome. The more the standard feels like additional load without local payoff, the more it gets compressed into a “checkbox version.” The network ends up with two systems: the standard on paper and the real routine in practice.

When resistance appears, the pendulum swings back toward autonomy. “Let dealers adapt.” The intent is sensible. The result is usually drift, because “adaptation” becomes an unbounded permission slip.

This is the oscillation that mature networks outgrow. They stop trying to win with either control or freedom. They design minimum standards that are narrow, operational, and defensible.

Minimum standards only work when they protect something dealers care about

Dealers accept non-negotiables when they understand what the standard is protecting.

A standard that protects the customer promise is easier to defend than a standard that protects the central dashboard. A standard that protects efficiency is easier to adopt than a standard that adds work. A standard that protects evaluation meaning is easier to accept than a standard that exists “because governance.”

This is the first design test. If you cannot explain what a standard protects in one calm sentence, the network will experience it as control.

The execution spine should be small enough to remember, specific enough to observe

Minimum standards fail when they are written as abstract intentions.

“Be proactive.” “Improve retention.” “Follow the process.” Dealers cannot operationalise that consistently because it doesn’t tell them what to do when the diary is full, the inbox is spiking, or a customer goes silent.

Minimum standards also fail when they are written as a full operating manual. If the execution spine is a long list, it won’t survive real weeks.

A workable spine is usually a handful of observable commitments. They look like this:

  • a clear trigger that starts the routine
  • an agreed follow-up cadence that doesn’t collapse into one burst
  • a rule that preserves targeting integrity so results remain interpretable
  • a clear owner for handoffs, plus an exception path for capacity reality

You will notice what is missing. There is no attempt to standardise everything. The spine defines what must stay intact so the program remains meaningful.

Dealers adopt standards that fit inside their cadence

A standard becomes real when it has a place in how the dealership runs the day.

If the standard lives in a PDF, it is a suggestion. If it lives in the CRM workflow and the morning huddle, it becomes routine.

This is where central teams can remove friction instead of adding it. You don’t need dealers to “try harder” to follow standards. You need the standards to travel through the tools and rhythms that already exist.

A simple example shows the difference. A standard that says “log all follow-ups” will be ignored when the system is slow and customers are waiting. A standard that makes follow-up completion the natural next step in the CRM workflow, with a clear owner and an exception option when capacity is saturated, will be enacted because it reduces decision-making in the moment.

Decision rights stop standards from turning into negotiations

Even good minimum standards break down when nobody knows who can change what.

Dealers will always face local exceptions. Central teams will always face network-wide consequences. Without clear decision rights, every deviation becomes a debate and every debate becomes politics.

A mature network separates three things:

  • what dealers may adapt without asking
  • what dealers may adapt but must declare
  • what dealers may not adapt because it breaks the execution spine

This is not bureaucracy. It is what prevents standards from being re-litigated every time pressure rises.

Governance should make exceptions safe, not hidden

Standards fail quietly when dealers feel forced to pretend.

If the only acceptable answer is “we complied,” the network will lose visibility precisely when it needs it most. Dealers will create workarounds, managers will protect their teams, and the central team will learn about drift through outcomes too late to fix it.

Healthy governance creates a safe way to surface exceptions. Not as an excuse, and not as a complaint, but as operational information.

The key is to standardise the exception path as part of the standard. When capacity is full, what is the approved downgrade? When the audience is unworkable, what is the approved adjustment? When the handoff role is missing, what is the approved temporary owner?

When exceptions are explicit, you reduce hidden variation and you learn faster.

What it looks like when networks get this right

Networks that mature in this area look boring in the best way.

They keep the spine short, and they defend it calmly. They allow flexibility around the spine, and they expect dealers to declare meaningful adaptations. They spend more effort removing friction from the workflow than writing longer standards. Their governance conversations start with enactment signals, not with blame.

In those networks, dealers still have autonomy. They just don’t have to reinvent the essentials.

A diagnostic question for your next standards reset

If you tightened standards tomorrow, would you increase adoption discipline or would you increase quiet workarounds?

If you loosened standards tomorrow, would you preserve evaluation meaning or would you lose the ability to compare execution across the network?

A practical test sits in the middle:

Can you name the execution spine in dealer terms, keep it small enough to remember, and design decision rights and exception paths that make it adoptable under real operating pressure?