What Sales and Customer-Facing Professionals Can Learn from Drive
You're on your fourth call of the day, working off a script that specifies the exact objection-handling line for "I need to think about it," and you deliver it word for word even though this particular customer clearly needed something else — a straight answer to a question the script doesn't cover. Or you're a week from quarter's end, short of quota, and you catch yourself pushing a customer toward the plan that closes fastest rather than the one that actually fits what they described needing. Sales and support roles run almost entirely on external metrics by design — quota, commission tier, average handle time, CSAT score — because those numbers are how the business tracks whether the work is getting done. But when every conversation becomes primarily about hitting the number attached to it, the actual skill of reading a customer and solving their real problem starts to atrophy, and customers can usually tell the difference between being helped and being closed.
The whole book, compressed
This edition works through 4 core lessons — take them one at a time, not all at once.
What's different for your conditions
Tap whichever ones sound like you. Nothing here is sent or saved — it's just for your own noticing.
0 of 5 selected
The core lessons, applied to you
Find your discretion inside the required structure
Scripts and call flows usually specify the required steps but not the tone, the specific questions you ask, or how you sequence the conversation. That's real room to operate as yourself rather than as a recording.
A support rep follows the required troubleshooting script exactly in order for every call, even when the customer has already ruled out the first three steps, and customers start hanging up mid-call frustrated at being made to repeat things they've already said.
Identify the one part of your required process where you have genuine discretion, and use it deliberately with your next difficult customer instead of defaulting to habit.
Build skill in reading people, not just reciting the pitch
Anyone can memorize a pitch. The actual professional skill is diagnosing what a specific customer needs before deciding which parts of the pitch even apply.
A salesperson who consistently hits quota realizes, when asked to train a new hire, that he can't actually explain why he says what he says on a call — he's been running on memorized lines for two years without developing any real diagnostic skill underneath them.
After each significant call this week, write one sentence naming what the customer actually needed, separate from what you said to them.
Remember the actual problem you're solving for someone
"Close the deal" or "resolve the ticket" describes your metric, not the customer's experience. Behind the ticket number is someone whose actual day is affected by whether the problem truly gets solved.
A support rep closes a difficult ticket by offering a workaround he knows is unstable, purely to hit his resolution-time target, and the same customer calls back angrier three days later when the workaround fails.
Before ending your next customer interaction, ask yourself one question — did this actually solve their problem, or just close the ticket — and act on the honest answer.
Let commission chase the closeable, not the complex
Commission and bonus structures work well for reliably pushing volume on relatively standard, well-understood deals. But for complex sales requiring real judgment about fit, or support cases needing genuine problem-solving, chasing the metric too hard can push you toward the fast, easy resolution instead of the right one, and customers notice the difference over time in ways that cost you more than the bonus was worth. Let quota drive effort, not judgment.
Real customer-first purpose can pull against a quota built around volume and speed, since the right answer for a specific customer sometimes takes longer than the metric rewards. When that happens, treat quota as a floor you have to clear, not a ceiling on how well you're allowed to do the job — protect the extra two minutes that actually solves the problem, and make up the time elsewhere.
Name one thing, honestly
Think of your last difficult customer interaction — were you optimizing for their actual problem, or for the number the interaction would produce on your dashboard?
Good. Now look back at the "Try this" line under whichever lesson feels most connected to what you just wrote, and treat that as this week's actual assignment — not all 4 at once.
The practices from this edition
0 of 3 selected
Run this for seven days
Before ending your next customer interaction, ask yourself one question — did this actually solve their problem, or just close the ticket — and act on the honest answer.