The Most Expensive “Yes” in the Dealership

A few years ago, a client brought me an idea and I did not think it would work.

I did not say that clearly. I softened my disagreement, agreed to move forward, and tried to repair the weak parts while we were building it.

The project failed. We lost about three months and spent money that did not need to be spent. When the client became frustrated, I became angry because I had known from the beginning.

That reaction exposed the part I did not want to own: I had kept my objection private and expected the client to somehow share responsibility for a warning I never gave them.

I see versions of that mistake all over dealerships.

An owner wants to add a vendor. The GM doubts the problem is a vendor problem but says, “We can try it.” A sales manager knows the new process will die on a Saturday but agrees in the meeting. A salesperson hears a customer commitment being overstated and stays quiet because correcting the desk feels dangerous.

Everyone leaves aligned.

Then they begin building workarounds.

Agreement is not alignment

Dealerships move through hierarchy. Ownership decides. The GM carries the store. Managers control deals, schedules, opportunities, and money. That structure is necessary.

It also makes a polite yes difficult to interpret.

The person may agree with the decision. They may understand that the decision is yours after they gave a different opinion. Or they may be protecting themselves from the discomfort of disagreeing with someone who has more authority.

Those are three different situations, but they sound the same in a meeting.

False alignment becomes visible later. The manager implements the new process halfway. The team keeps the old spreadsheet “just in case.” Nobody defines success because nobody wants a clean test. When the result is poor, the room fills with people who quietly knew it all along.

That is not candor. It is delayed self-protection.

The workaround is the receipt

When people do not believe in a decision but do not feel able to challenge it, they rarely refuse directly. They work around it.

They add a side process. They keep separate notes. They reinterpret the instruction for their department. They wait for the leader's attention to move somewhere else. They comply just enough to say they tried.

The leader experiences this as resistance or poor execution.

Sometimes it is. But before you blame execution, look for the moment when disagreement went underground.

Ask: What concern did people raise before the decision? What concern did they stop raising after they saw the leader's reaction? Which parts of the plan now require manual rescue? Who benefits if the test remains vague?

A workaround is often evidence that the real argument never happened.

Vendors benefit from polite leadership teams

This pattern gets expensive when a vendor is in the room.

The presentation is polished. The product solves a recognizable problem. Ownership likes it. The internet director or sales manager sees overlap with something already in the stack, but the meeting is moving fast and nobody wants to sound negative.

So the store buys the product and decides to figure out the details later.

Three months afterward, logins are low, responsibilities are unclear, reporting does not match the CRM, and the vendor says adoption is the problem.

The store may indeed have an adoption problem. It may also have purchased a solution before the leadership team was willing to argue honestly about the problem.

Before signing, someone should be able to say:

• Here is the exact problem we believe this solves.
• Here is what we already pay for that touches the same problem.
• Here is who will own implementation every week.
• Here is the evidence that will tell us to keep, change, or cancel it.
• Here is the strongest reason not to buy it.

If the room cannot produce the last answer, the decision has not been challenged. It has been sold.

Honest disagreement needs a structure

Telling people to “speak up” is not enough. The cost of speaking up is set by what happens to the first person who does it.

Use a simple disagreement format:

What I see: State the relevant fact or pattern without attacking the person who proposed the idea.

What I think it means: Give your judgment and make it clear where you may be wrong.

What I expect will happen: Name the operational consequence and the time horizon.

What I recommend: Offer a different move, a smaller test, or a condition that would change your view.

A sales manager might say: “I agree we need faster follow-up. I do not think another automation fixes the missing ownership after a reply. My concern is that we add more messages while the same customer still has no clear person responsible. I recommend we test one lead bucket with named ownership for two weeks before we add the tool.”

That is not defiance. It is useful disagreement.

The leader still decides.

Once the decision is made, remove the escape hatch

There is another side to this.

You do not get to state your concern, lose the argument, and then implement badly so you can be proven right.

After a real discussion, the decision owner should state what was decided, why, who owns what, how the test will be measured, and when the group will review it. People who disagreed should be able to explain the decision and execute it honestly.

If new evidence appears, bring it forward. Do not hide it inside weak effort.

That is the difference between disagreement and sabotage: disagreement happens before and during the decision; sabotage protects the person's prediction afterward.

Watch what the right move makes you risk

Most leaders already know when they are holding back a real objection.

The harder question is what saying it would put at risk.

Approval from the owner. The relationship with a vendor. The identity of being easy to work with. The possibility that you could challenge the plan, take responsibility for your alternative, and still be wrong.

That last one was mine.

Going along gave me an escape hatch. If the idea failed, I could tell myself it had never been mine. But the price of that protection was three months of work I did not believe in.

Do not confuse discomfort with proof that you are right. Sometimes the owner sees something you do not. Sometimes the manager's objection protects an old habit. Sometimes the vendor's proposal is the right move.

The point is not to reward the loudest dissenter. It is to make the real disagreement available before money, time, and credibility are committed.

The most expensive yes in a dealership is the one that means, “I do not agree, but I would rather resent this later than risk being wrong out loud now.”

Companion reading: I Knew It Was a Bad Idea. I Went Along With It Anyway., from The Self-Aware Leader.

Before adding another vendor or forcing another store-wide initiative, read The Vendor You Can't Cut (And the Three You Should Have Cut Last Year). If your leadership team keeps agreeing in meetings and working around decisions afterward, bring one real decision to a free 30-minute Dealer Leadership session.