Picture a hypothetical Monday morning at a dealership. The sales meeting has run long, two deliveries need attention, and the used-car manager is explaining why five vehicles promised for the frontline still aren’t ready. Someone at the desk says, “We need everybody to want it more.” Nobody leaves knowing which decision will get those vehicles ready—or who is supposed to make it.
That’s a familiar leadership trap approaching year-end. A missed forecast becomes a motivation problem before anyone checks whether it’s actually a capacity problem, an approval delay or an assignment that keeps changing. The distinction matters to the customer waiting for a vehicle, not just to the employee trying to explain the delay.
Pressure isn’t always the enemy. A clear number and a firm deadline can focus a department, especially when people understand what they can do to influence the result. Repeating the number while leaving the obstruction in place gives them little to act on. The manager’s job is to make the demand useful: settle competing priorities, get decisions made and address weak execution where it actually occurs.
Dealership team motivation needs more than a forecast
A GSM can own the monthly sales forecast. A salesperson cannot control traffic, lender decisions, inventory availability and every trade valuation needed to deliver it. That doesn’t excuse weak follow-up. It means the forecast conversation needs to lead to assignments people can complete: confirm a customer’s next step, resolve a missing document or get a firm answer about vehicle availability. “Find another deal” is an expectation, not much of a work plan.
When leaders treat every shortfall as an effort deficit, employees may start favoring activity that looks reassuring. More logged attempts. More optimistic delivery dates. Fewer candid updates about deals that are falling apart. A manager can mistake that busyness for progress until the promised deliveries fail to materialize. Ask what changed for the customer, rather than accepting a larger activity count as the answer.
Then management responds with another check-in.
Before adding one, look at the reporting already on the calendar. Consider a hypothetical store where eight managers each spend an extra 12 minutes a day preparing and delivering duplicate status updates. Some reporting earns its time by prompting a decision. But if the second update changes no priority, resource or approval, that time could be better spent coaching an employee or resolving a customer concern. Keep the review that helps managers act; combine or drop the one that simply repeats yesterday’s concern.
Watch the gap between responsibility and authority
The authority gap is the distance between what someone is held responsible for and what they’re allowed to change.
Take recon throughput. A used-car manager owns days-to-frontline but may not control technician allocation, parts approvals or sublet scheduling. If every exception waits for the same executive’s signature, the manager can chase harder without getting cars through faster. Agree on which routine decisions the manager can make, which require approval and who can respond when the usual decision-maker is unavailable. The benefit is a more dependable frontline date—and fewer promises sales has to walk back.
The same gap appears when a service director is told to protect margin and accommodate every internal rush job, with no agreed priority between them. Both requests may be legitimate. Before the next rush request arrives, leadership should decide how customer commitments and internal work will be weighed, and who settles a conflict. Otherwise, advisors and technicians are left negotiating priorities they didn’t set while both departments wait.
I’d argue that unresolved conflicts between management priorities can drain more energy than an aggressive target. People can work toward a demanding number; it’s harder when following one manager’s direction earns a reprimand from another. Giving someone authority doesn’t mean removing limits or letting expenses drift. It means making those limits clear enough that routine work can proceed, while genuine exceptions reach someone who will make a timely decision.
Keep the target. Change the management obligation.
At the next target review, replace the general demand for more urgency with four questions. Apply them to one missed commitment, not the department’s entire month. Start with what was agreed, rather than a judgment about the employee’s attitude:
- What specific action did the employee agree to complete?
- Did that person have the time, information and authority to complete it?
- Which dependency failed, if any, and who owns fixing it?
- What evidence will establish completion at the next review?
If the employee had what they needed and didn’t execute, coach directly and privately. State what was missed, hear their explanation and agree on the next action and deadline. Repeated misses still require a performance conversation; identifying obstacles is not a blanket excuse. If an approval sat untouched for two days, management gets an assignment too. An employee should leave the review knowing both what they owe and what help has been committed.
Recognition should follow the same logic. Acknowledge the person who surfaced a threatened delivery early enough to save it, not only the person who reported the sold unit. Be specific about why that mattered: the early warning gave the store time to arrange an alternative and protect the customer’s plans. That makes honest reporting worth repeating without lowering expectations for completed work.
Before your next forecast review, pull 10 missed commitments from the previous week. Mark each as an execution miss, a blocked dependency or an unclear assignment; where causes overlap, note the first obstacle that prevented completion. Count them. If six were blocked dependencies, clear the most common blockage before scheduling another meeting about attitude. Assign an owner and a deadline, then revisit those commitments the following week. The test is whether work gets finished with fewer avoidable delays—not whether the meeting feels more motivational.