Earlier in my career, I thought experience would eventually mean having more answers. I assumed that after enough years in automotive sales, I would recognize most situations quickly and know what to do without having to think about them very much.
In some ways, that has happened. There are situations I can understand much faster today because I have seen versions of them before. I know the sales process better. I understand where problems commonly occur. I can usually recognize when something needs immediate attention and when it can wait.
What I did not expect was that experience would also make me ask more questions.
The longer I have worked in automotive sales, the more careful I have become about assuming that I understand a situation based on the first piece of information I receive. Two problems can look almost identical at first and have completely different causes. Two customers can ask for the same thing for completely different reasons.
Knowing what usually happens is useful. Assuming that the usual explanation is always correct is where experience can become a problem.
Having an Answer Is Not the Same as Understanding the Problem
When you are newer in a career, there can be pressure to prove that you know what you are doing. Someone asks a question, and you want to have an answer. A problem comes up, and you want to solve it quickly.
I understand that instinct because I have had it myself.
There is satisfaction in being the person who can immediately say, “Here’s what we need to do.” Sometimes that confidence is justified. Other times, you are solving a problem before you fully understand it.
I have become more comfortable saying, “Tell me what happened.”
That simple question has saved me from making assumptions more times than I can count.
A salesperson may come to me with an issue and describe the part that seems most important to them. Once I ask a few questions, I may realize the actual problem started several steps earlier. A customer may tell me they are unhappy with one thing when the real frustration is that they did not understand what was happening.
If I respond only to the first thing I hear, I may fix the wrong problem.
Customers Often Know What They Want, but I Still Need to Know Why
This is especially important when working with customers.
Today’s car buyers often arrive at a dealership having already done significant research. They may know the model they want, the features they prefer, and the specifications they have compared. I respect that preparation.
At the same time, I still want to understand why certain things matter to them.
If someone tells me they need more space, I could immediately start thinking about larger vehicles. However, “more space” can mean many things. Do they regularly carry passengers? Do they need room for work equipment? Are they planning for a growing family? Is the problem actually cargo space rather than passenger space?
One additional question can completely change the conversation.
I have learned that recommending something too quickly can sometimes look efficient while actually making the process longer. If the recommendation is based on an assumption, we eventually have to go backward and figure out what the customer needed in the first place.
Taking another minute at the beginning can save a lot of time later.
The First Version of a Problem Is Rarely the Whole Story
The same principle applies to management.
When something goes wrong during a busy day, information usually arrives in pieces. One person tells you what they saw. Someone else knows what happened earlier. A customer may have understood the conversation differently from the salesperson.
The first explanation may be completely accurate, but I have learned not to assume that it is complete.
I want to know what happened before the problem appeared. I want to understand who was involved and what each person believed was supposed to happen next. I want to know whether this is a one-time issue or something we have seen before.
That does not mean turning every small problem into an investigation. There is a balance.
Automotive sales moves quickly. Sometimes you have enough information to make a reasonable decision, and continuing to ask questions would only slow things down. Experience has helped me recognize those situations too.
The goal is not to collect every possible detail. The goal is to find the details that could change the decision.
Experience Can Create Blind Spots
There is another reason I try to ask questions before reaching conclusions. Experience can make you overconfident.
When you have seen a situation many times, your brain naturally starts recognizing patterns. That is useful. Pattern recognition is part of what makes experience valuable.
It can also make you stop looking closely.
You think you know why a customer is hesitating because you have seen similar situations before. You think you know why a process slowed down because you recognize the symptoms. You think you understand what an employee needs because you have coached someone through something similar.
Most of the time, you might even be right.
The problem is what happens when you are not.
I try to remind myself that recognizing a situation does not mean I know everything about it. Sometimes the question I almost did not ask turns out to be the one that matters.
Asking Questions Does Not Mean Avoiding Decisions
I also think there is an important distinction between being thoughtful and being indecisive.
There are situations where a manager has to make a call. You cannot keep asking questions forever because you are afraid of making the wrong decision.
I have certainly made decisions without having every piece of information I would have liked. That is part of the job.
What has changed is how I think about the information I need.
I ask myself whether another question could realistically change what I am about to do. If the answer is yes, I probably need to ask it. If the answer is no, then it may be time to make the decision and move forward.
That judgment has become easier with experience, although I would never say I get it right every time.
Good Questions Make People Better at Solving Problems
Asking questions has also changed how I work with other people.
Earlier in my career, if someone brought me a problem and I knew the answer, I was more likely to simply give it to them. That was efficient in the moment.
Over time, I started wondering whether it was always useful.
If someone asks me what they should do, I may now ask what they think the next step should be. I want to understand how they are looking at the situation. Sometimes they already know the answer and just need confidence. Sometimes their response shows me exactly where the confusion is.
That conversation takes longer than simply giving an instruction, but it can save time in the future because the person becomes better at handling similar situations independently.
I Am More Comfortable Not Knowing Immediately
Maybe the biggest change is that I no longer feel the same pressure to have an immediate answer to everything.
I still want to be useful. I still believe managers need to make decisions and provide direction. I just have a different idea of what that looks like now.
Sometimes being useful means having the answer. Sometimes it means knowing which question to ask before anyone decides anything.
Experience has given me more answers than I had earlier in my career, but it has also shown me how often the obvious answer is incomplete.
That is why I ask more questions now, not fewer. I have learned that good judgment is not about proving how quickly you can reach a conclusion. It is about understanding enough of the situation to make the conclusion worth trusting.