The Leadership Inflection Point | Article 2 | Strategy Without Minimum Standards Is Just Theater.
Most dealerships do not suffer from a shortage of strategic priorities.
Customer experience is a priority. Retention is a priority. Digital retail is a priority. Employee development, reputation, operational efficiency, artificial intelligence, content, community involvement, service growth, and data-driven decision-making are priorities.
The organization may have presentations explaining each one.
What it often lacks is a clear definition of what must happen consistently because the priority exists.
That is the distance between strategy and operating reality.
A strategy describes where the organization intends to go. A minimum standard determines the behavior the organization will require while getting there.
Without that standard, the strategy remains interpretive.
One manager embraces it. Another waits for the enthusiasm to pass. One rooftop builds a process. Another continues operating as before. One employee receives support. Another is told the initiative matters but still has to complete it after everything else is finished.
Leadership may continue repeating the priority.
The organization learns that execution is optional.
Strategy becomes real at the minimum standard.
This is why dealerships can speak credibly about innovation while continuing to tolerate inconsistent processes, neglected tools, weak follow-up, fragmented customer handoffs, incomplete reporting, abandoned content, and departments operating through entirely different definitions of acceptable execution.
The issue is not always that people disagree with the strategy.
Frequently, nobody has translated it into a requirement sturdy enough to survive the month.
Strategy theater occurs when an organization receives the emotional and reputational benefits of having a strategy without accepting the operating discipline required to execute it.
The language is present.
The behavior remains largely unchanged.
A leadership team announces that customer experience will differentiate the dealership. The website continues forcing customers through unnecessary friction. The CRM continues losing context between departments. Employees continue asking customers to repeat information the organization already collected.
The dealership announces a commitment to content. Marketing receives no defined production cadence, no reliable access to subject-matter experts, no publication accountability, and no expectation that department leaders participate.
The store adopts an artificial-intelligence platform. Employees attend one demonstration, receive a login, and return to the same workflows, incentives, and priorities that existed before the implementation.
The organization launches a retention initiative. Thirty-day sales pressure continues rewarding decisions that weaken service loyalty, trust, referrals, and repeat business.
In each case, the strategy may be sincere.
The theater appears because leadership has not changed the minimum operating requirement.
The initiative becomes something the organization is encouraged to support rather than something the organization has been designed to execute.
This distinction can be difficult to see during the launch period.
New strategies initially benefit from attention. Leaders discuss them. Meetings are scheduled. Vendors provide training. Early adopters create visible momentum. The organization can appear aligned because the initiative remains novel enough to attract energy.
The real test begins when novelty disappears.
Does the work continue when the month becomes difficult? Does the process survive a management change? Do employees know what is still expected when competing priorities arrive? Does leadership return to the initiative after the announcement stops producing attention?
If the answer depends on who happens to be working that day, the organization does not have a standard.
It has a preference.
Strategy theater allows leadership to announce a new direction while the organization retains permission to behave exactly as before.
A minimum standard defines the lowest acceptable level of execution the organization is prepared to consider normal.
It establishes what must happen regardless of enthusiasm, personality, workload, rooftop, department, vendor, or temporary market pressure.
The standard does not describe the organization’s highest aspiration.
It defines the floor beneath which execution is no longer considered acceptable.
That floor matters because culture is shaped less by the exceptional performance leadership praises than by the ordinary performance leadership tolerates.
A dealership may have one salesperson who creates exceptional customer follow-up, one advisor who communicates with unusual clarity, one marketer who keeps the entire content operation alive through personal effort, or one manager who consistently coaches the team.
Those people demonstrate what is possible.
They do not prove the organization has operationalized the behavior.
The standard exists when acceptable execution no longer depends on finding the exceptional person.
For example, a customer-experience standard might require that:
A content operating standard might require that:
An AI operating standard might require that:
The standard makes the strategy observable.
Leadership no longer has to ask whether the organization “supports” the priority.
It can examine whether the required behavior occurred.
Aspirations are useful.
They help organizations establish direction, meaning, and ambition. They tell people what the dealership hopes to become.
But aspirations are intentionally broad.
“Create the best customer experience in the market” may inspire a team. It does not tell an employee what to do when a shopper has already submitted the same information online, the CRM record is incomplete, and the next department is asking to begin again.
“Become an AI-enabled organization” may communicate urgency. It does not tell the team which uses are approved, which sources are trusted, where review is required, or how success will be measured.
“Build a content culture” may sound compelling. It does not establish who contributes, how often, through which workflow, with what support, under whose approval, or where the completed work must go.
A requirement translates the aspiration into behavior.
| Aspiration | Operating Requirement |
|---|---|
| Deliver an exceptional customer experience | Every customer handoff preserves prior information, names the next owner, and communicates the expected next step. |
| Become more data-driven | Every monthly review identifies what changed, why it matters, the next action, the owner, and the review date. |
| Activate employee expertise | Each department contributes recurring customer questions and at least one usable expert contribution within the defined cadence. |
| Use AI responsibly | Material claims must remain grounded, reviewable, attributable, and subject to defined human oversight. |
| Improve retention | Customer lifecycle measures are reviewed alongside current-period gross and influence operating decisions. |
| Build better content | Every asset begins with a real customer or market signal and remains tracked through publication, distribution, and evaluation. |
A strategy can contain both.
The aspiration tells the organization why the work matters.
The requirement tells the organization what leadership expects to happen.
When leaders provide only the aspiration, employees must invent the requirement themselves.
That creates variation by design.
Leadership often treats ambiguity as a temporary condition.
The process will become clearer after the team gains experience. Ownership will sort itself out. Managers will determine what makes sense locally. Employees will use good judgment. The vendor will guide implementation.
Some flexibility is healthy.
Not every operating decision should be centralized, scripted, or reduced to a universal checklist. Dealerships need room for local context, employee judgment, changing market conditions, and the practical intelligence of people close to the work.
But unresolved ambiguity carries a cost.
If nobody knows who owns publication, approved content may never reach the market. If contribution expectations are unclear, participation will depend on personal enthusiasm. If compliance review is undefined, teams will either publish risky material or route every low-risk asset through an unnecessarily heavy process.
If the organization has no shared definition of a qualified lead, an appointment, a completed follow-up, a published asset, a resolved customer issue, or an adopted workflow, every team can report success through a different interpretation.
Ambiguity is not neutral.
It transfers responsibility downward while preserving leadership’s ability to evaluate the outcome after the fact.
The employee is expected to use judgment.
If the result succeeds, the strategy worked.
If it fails, execution was inconsistent.
Minimum standards prevent this asymmetry.
They identify where judgment is welcome and where consistency is required.
When leadership refuses to define the minimum, the organization does not become flexible. It becomes uneven.
A functional minimum standard requires five elements.
The organization must define the expected behavior or outcome in language specific enough to observe.
“Communicate better” is not a standard.
“Every customer receives a named next step and expected response time before the interaction ends” can be observed.
“Create more content” is not a standard.
“Every department contributes recurring customer questions through the defined intake process each week” can be observed.
A standard must have an owner.
Several people may contribute, but one role must be accountable for ensuring the work occurs and for escalating the condition when it does not.
Ownership cannot remain attached only to the final stage.
Marketing should not be held accountable for employee participation if department leaders have no requirement to make employees available. A customer-experience leader cannot preserve continuity if each system and department can independently reject the shared process.
The organization needs a reliable way to determine whether the standard occurred.
The evidence should be proportional to the importance of the work. Not every action requires another dashboard, scorecard, certification, PDF, meeting, and commemorative plaque.
But leadership should not depend entirely on anecdote.
If the dealership says publication matters, it should know what went live. If follow-up matters, it should know whether the commitment was completed. If employee participation matters, it should know who contributed and whether the work reached the customer.
The standard must exist within a recurring rhythm.
When is the work expected? When is execution reviewed? When does the organization improve the process?
A priority without cadence is continuously vulnerable to the next urgent request.
The work will occur when someone remembers, when the month is quiet, or when the executive asks why momentum disappeared.
Leadership must define what happens when the standard is missed.
The response should not default immediately to punishment. Missed standards may reveal inadequate resources, poor system design, weak training, conflicting incentives, unclear ownership, or an unrealistic requirement.
But the miss must produce something:
If nothing happens when the standard is missed, the organization has communicated that the standard is optional.
The five elements become a simple operating framework we call the Minimum Standard Stack.
| Standard Layer | Operating Question |
|---|---|
| Definition | What must consistently be true? |
| Ownership | Who is accountable for making it true? |
| Evidence | How will we know whether it happened? |
| Cadence | When does the work occur and when is it reviewed? |
| Response | What happens when execution falls below the standard? |
The stack is deliberately simple.
Organizations do not usually fail because they lacked a more complicated framework. They fail because one or more of these basic elements remained undefined.
A dealership may have a clear definition but no ownership.
Everyone understands what should happen. Nobody is responsible for ensuring that it does.
It may have ownership without evidence.
A manager is accountable, but leadership cannot distinguish consistent execution from a compelling explanation during the meeting.
It may have evidence without response.
The dashboard repeatedly reveals the same failure. The organization reviews it, nods thoughtfully, and continues.
It may have cadence without purpose.
The team attends the weekly meeting, updates the tracker, and produces the report without the underlying behavior improving.
The stack helps leadership identify the missing operating layer.
It also prevents a strategy from becoming more complicated than the team can realistically execute.
Most customer-experience strategies are built around the expected journey.
The customer finds the vehicle, submits information, receives a response, arrives at the store, purchases, services, and eventually returns.
The visible process may look polished when everything goes as planned.
Customer experience is more often defined by what happens when the process stops behaving normally.
The customer changes vehicles. The trade information is incomplete. The promised employee is unavailable. A system fails to transfer the record. The advertised unit sells. The service recommendation is disputed. Consent preferences are unclear. A manager needs to intervene.
These moments reveal whether the dealership has a standard or merely a workflow.
A workflow describes the expected path.
A standard tells employees what the customer should still be able to expect when the path breaks.
For example:
These expectations create continuity across exceptions.
Without them, the customer experience depends on the instincts, authority, and emotional condition of the person who happens to receive the problem.
One employee rescues the relationship.
Another defends the process.
The dealership reports an average.
The customer remembers the moment.
A customer-experience strategy is only as credible as the minimum experience leadership protects when the process becomes inconvenient.
New technology is frequently implemented through an access standard.
The platform is configured. The users are invited. The integration is connected. Training is completed. Leadership receives confirmation that the implementation is live.
Access is not adoption.
Adoption requires the organization to define which behavior should now occur differently.
What work should move into the system? What previous process should stop? Which role owns the transition? What usage is expected? How will friction be surfaced? When will leadership evaluate whether the tool is creating the promised operating value?
Without an adoption standard, the technology competes against every established habit already inside the dealership.
The old spreadsheet is familiar. The existing message thread feels faster. The previous vendor still controls one part of the workflow. The manager has not changed the meeting. Employees are asked to use the new platform while continuing to maintain the old system “just in case.”
The organization creates duplicate work during the transition and then concludes the new system created more work.
A strong adoption standard might define:
This is how a product implementation becomes an operating-model decision.
The standard does not guarantee success.
It gives the organization enough clarity to determine whether the problem is the platform, the process, the resources, the incentives, or the leadership commitment.
Artificial intelligence makes minimum standards more important because it expands capability faster than most organizations can develop governance around it.
Employees can generate customer communications, advertisements, articles, scripts, images, reports, summaries, and recommendations before leadership has defined which uses are appropriate.
This creates a familiar temptation.
Allow the experimentation now. Establish the standards later.
Some experimentation should be encouraged. Organizations cannot learn entirely through policy development. Teams need room to test ideas, discover valuable use cases, and understand where AI genuinely removes friction.
But scale should follow standards.
Before AI-generated work becomes a normal part of the customer experience, leadership should define minimum expectations around:
These standards should vary by risk.
A brainstorming prompt does not require the same process as a customer-facing pricing claim. An internal summary does not carry the same consequence as service guidance, financing language, or a public statement attributed to an employee.
The objective is not to surround every useful AI interaction with enough governance to make the fax machine feel agile.
The objective is to define where speed is safe, where review is required, and where the system must not guess.
AI should not scale faster than the organization’s ability to define what acceptable use looks like.
Technology amplifies the standards already present.
Where standards are absent, it amplifies variation.
Leaders often attempt to repair inconsistent execution through stronger accountability.
The instinct is understandable.
People must be responsible for their work. Standards without accountability eventually become suggestions.
But accountability cannot compensate for an undefined system.
When ownership is vague, resources are insufficient, expectations conflict, evidence is incomplete, and managers enforce different rules, holding an individual accountable may identify a convenient person rather than the actual operating failure.
True accountability begins before the miss.
The employee understands the expectation. The owner has the necessary authority. The process is workable. The evidence is accessible. Competing incentives have been addressed. Leadership has demonstrated that the standard matters.
Only then can the organization distinguish:
This is a more mature form of accountability.
It is interested in improving the operating system, not merely locating the nearest individual when the system produces an unwanted result.
Leaders should still enforce consequences where necessary.
Repeatedly ignoring a clear, supported, and reasonable standard is a performance issue.
But consequences become credible only after leadership has completed its own part of the agreement.
The phrase “minimum standard” can sound like an invitation to mediocrity.
It is not.
The minimum is the foundation beneath improvement.
High-performing teams require room to exceed the standard, experiment, develop new practices, and pursue exceptional outcomes. Leadership should celebrate people who create better methods, stronger experiences, and more ambitious results.
But excellence cannot become the substitute for consistency.
An organization that depends on extraordinary employees to compensate for an undefined operating model may produce moments of exceptional performance while remaining structurally weak.
The minimum standard protects the customer and the organization from falling below an acceptable floor.
Above that floor, improvement can become more meaningful because the team is no longer spending all of its energy recovering from preventable variation.
This creates three levels of execution:
| Execution Level | Meaning |
|---|---|
| Minimum Standard | The lowest acceptable level of consistent execution |
| Target Standard | The level the organization expects competent teams to achieve regularly |
| Excellence Standard | The evolving benchmark demonstrated by the strongest execution |
The minimum protects consistency.
The target directs performance.
Excellence expands what the organization believes is possible.
Leadership should manage all three.
Minimum standards are often written for employees.
Leadership remains outside the document.
Salespeople must follow up. Advisors must communicate. Marketing must publish. Managers must inspect. Employees must adopt the platform.
The leader’s responsibility is implied.
That is incomplete.
Leadership behavior should be part of the standard.
If employee contribution matters, department leaders must make participation possible. If a new platform matters, executives must retire conflicting processes and return to adoption after launch. If customer experience matters, leaders must resolve incentives that reward departments for creating friction elsewhere in the journey.
If long-term retention matters, leadership must review lifecycle outcomes alongside thirty-day performance. If responsible AI matters, leaders must resource authoritative information, governance, and review rather than asking employees to “be careful.”
A leadership standard may require that:
This protects the initiative from becoming another responsibility assigned downward without corresponding leadership change.
Leadership cannot require a new operating model while continuing to behave according to the old one.
Dealerships can establish a simple recurring review around six questions.
State the requirement in observable language.
Review the available evidence without replacing evidence with explanation.
Identify variation by department, rooftop, role, workflow, or circumstance.
Separate knowledge, resources, incentives, process design, technology, management reinforcement, and individual performance.
Assign corrective action, support, redesign, coaching, escalation, or consequence.
Minimum standards should be durable, not permanent.
As the organization improves, the standard may need to rise. As technology or customer expectations change, the requirement may need to evolve. If a standard creates unnecessary work without protecting customer or business value, leadership should revise it.
The purpose is not bureaucratic permanence.
It is disciplined execution.
Choose one priority the organization discusses frequently but executes inconsistently.
Do not attempt to standardize the entire dealership in one meeting.
Define the lowest acceptable behavior or outcome in observable language.
Remove words such as “better,” “stronger,” “more,” “world-class,” and “best-in-class” unless the organization can explain exactly what they require.
Document:
Write down what leaders must provide, stop, inspect, resolve, or protect for the standard to work.
Examine the moments when the normal workflow breaks.
Determine what the customer or employee should still be able to expect.
If a new platform or workflow is becoming the standard, identify one legacy behavior the organization will stop maintaining.
Do not require teams to adopt the future while preserving every obligation from the past.
Do not count implementation, logins, invitations, or completed training as proof of adoption.
Define the behavior that should now occur differently.
Find a standard the organization misses regularly.
Before blaming the person, examine definition, ownership, evidence, cadence, resources, incentives, and leadership reinforcement.
Place the thirty-, sixty-, and ninety-day operating reviews on the calendar before announcing the initiative.
Leadership attention should not expire when novelty does.
Next in the series: Thirty-Day Gross Is Eating the Customer Lifecycle.
Hrizn v6 is designed to help dealership marketing teams move from fragmented activity toward a more connected operating advantage—bringing intelligence, creation, participation, distribution, proof, and improvement into a more coherent system.
Begin your Hrizn journey before August 1 to secure current pricing ahead of the v6 launch.
Dealership creators, marketing leaders, operators, and agency partners can also raise their hands for the first Hrizn Creator cohorts.
See how much easier this gets with Hrizn.
We Rise Together.
