Imagine that you are explaining something you have spent months building.
You know every detail. You know why you chose one approach over another, which problems you solved along the way, and how many small decisions made the final product possible.
You are excited to share it with someone.
You begin explaining the features. Then the technology. Then the advantages. You remember another useful detail and add that, too. You want the other person to understand the full picture, so you explain the exceptions, the possibilities, and all the things they might want to know.
You have spoken for fifteen minutes.
The other person smiles politely and says, “That sounds interesting.”
But you are not sure whether they understood what you were trying to say.
Perhaps they did. Perhaps they didn't. Perhaps they understood the details but still have no idea why the product matters to them.
This happens more often than we realise.
When we care deeply about something, we tend to believe that explaining more will help others appreciate it. We add information because we want to be thorough. We anticipate questions because we want to be prepared. We explain every advantage because we don't want the other person to miss anything important.
And sometimes, in trying to make everything clear, we make the main idea difficult to find.
Clarity is not the result of saying everything. It is the result of helping someone understand what matters.
Why We Overexplain
Overexplaining often begins with good intentions.
We want to be understood. We want to appear knowledgeable. We want to demonstrate that our product is worth the price we are asking. We want to make sure the other person has no reason to reject our proposal.
There may also be a little fear involved.
What if the customer thinks our product is too simple? What if they don't recognise the effort behind it? What if they compare us with a competitor? What if they ask a question we haven't anticipated?
So we keep talking.
We add another benefit, another example, another justification. We try to address objections before they arise. We provide information the other person may not need, hoping that somewhere in all those words we will find the one thing that convinces them.
But the other person is experiencing the conversation differently.
They may be trying to understand the basic idea while we have already moved to the fifth feature. They may be wondering whether the offer solves their problem while we are explaining how the system was built. They may be interested but need time to think, while we interpret their silence as a sign that we should say more.
Our intention is to create confidence. The result may be confusion.
The difficulty is that we often measure a conversation by how much we have explained, rather than by how much the other person has understood.
These are two very different measurements.
A long explanation can be useful when the subject requires it. A technical discussion between experts may need precision and detail. A customer evaluating an expensive or complicated decision may need extensive evidence.
The problem is not length itself.
The problem is unnecessary complexity.
The Curse of Knowing Too Much
The more we know about something, the harder it can become to explain it simply.
A developer understands the architecture behind a software platform. They know about databases, APIs, authentication, infrastructure, caching, security, and performance. When describing the platform, all these details may seem relevant because each one contributes to how the system works.
But a business owner may not need to understand any of those things to decide whether the platform is useful.
The owner might simply want to know:
“Can my customers find my products, understand what I offer, and contact me easily?”
If the answer is yes, the technical details can come later.
This is a challenge for people who have expertise. We tend to explain a subject from the inside out. We begin with what we know and move towards what we think the other person should understand.
But the listener needs something different. They need a way into the subject that connects with what they already know and care about.
A good explanation begins there.
A doctor does not need to explain every biological mechanism to help a patient understand the next step in their treatment. A financial adviser does not need to begin with every calculation behind a recommendation. A teacher does not need to introduce every advanced concept before helping a student understand the basics.
The expertise is still there. It simply does not need to arrive all at once.
In fact, being able to explain something clearly often demonstrates a deeper understanding than being able to describe it with complicated language.
The challenge is not to make a complicated subject sound impressive.
It is to make the important part understandable without making it inaccurate.
Simple Does Not Mean Shallow
There is a danger in taking the advice to keep things simple too far.
We can remove so much detail that the message becomes vague. We can simplify a complicated promise until it sounds misleading. We can reduce a meaningful offering to a slogan that says very little.
“Grow your business.”
“Improve your life.”
“Save time.”
These statements are easy to understand, but they don't tell us much about what is actually being offered.
Simplicity needs substance.
Consider two explanations of the same service.
The first says:
“We provide advanced digital solutions to help businesses optimise their operational capabilities and leverage modern technologies for enhanced growth.”
The second says:
“We help businesses present their products and services online, receive enquiries, and make it easier for customers to understand what they offer.”
The second is simpler, but it is not empty. It gives the listener something concrete to understand.
They can picture the work. They can decide whether it is relevant to their situation. They can ask a useful follow-up question.
That is the difference between simple language and superficial language.
Simple language removes unnecessary effort from the listener. Superficial language removes the meaning itself.
We should aim for the first.
One Conversation, One Main Idea
Imagine that you are meeting a business owner who has never heard of your company.
You have a website platform, a content management system, e-commerce capabilities, enquiry forms, analytics integrations, booking functionality, automation options, and plans for AI-powered features.
You could explain all of them.
But what is the one thing this person needs to understand first?
Perhaps it is that you help businesses make their offerings easier to discover and act upon online.
That idea can become the starting point for the conversation.
If the owner wants to discuss product sales, you can explore the e-commerce capabilities. If the owner needs to receive enquiries, you can explain how visitors can get in touch. If the owner wants to publish articles, you can discuss the content tools.
The conversation expands according to the customer's needs.
You do not have to deliver the entire catalogue before discovering what matters.
This is a useful principle: begin with one clear idea, then add detail when the conversation calls for it.
It does not mean every meeting must have only one objective or that every product must be described in one sentence. It means the listener should be able to identify the main point without searching through a pile of supporting information.
When everything is presented as equally important, nothing stands out.
A clear main idea gives the conversation direction.
The Power of a Simple Question
Sometimes the best way to keep a conversation simple is to stop explaining and ask a question.
Suppose you have described your offering in a few sentences.
Instead of continuing with another list of features, you could ask:
“Does this sound relevant to what you're trying to achieve?”
That question creates space for the other person to participate.
They might say yes and ask for more details. They might explain a concern you had not considered. They might tell you that they need something different. They might ask how the solution would work in their particular circumstances.
Each response gives you information you did not have before.
A conversation becomes unnecessarily complicated when one person tries to anticipate every possible question and answer them all in advance. It becomes more manageable when both people help determine what needs to be discussed.
This is particularly important in sales because the customer is not merely receiving information. They are trying to make a decision.
They need enough information to understand the offer, assess its relevance, evaluate the risks, and decide what to do next.
They do not necessarily need every piece of information you possess.
A useful question can tell you what to explain next. It can also tell you when to stop.
A Simple Structure for a Sales Conversation
A sales conversation does not need to follow a rigid script. Every person and situation is different. But a simple structure can help us stay focused, especially when we are nervous or eager to explain our offering.1. Understand the problem
Start by learning about the person's situation.
“What are you trying to improve?”
“What is proving difficult at the moment?”
“What happens if this problem remains unsolved?”
You do not need to ask all these questions in succession. Choose the ones that fit the conversation and listen carefully to the answers.
2. Clarify the desired outcome
Understanding the problem is only part of the picture. You also need to know what the person wants instead.
“What would a better situation look like?”
“What would you most like to change?”
“How would you know that the solution was working?”
These questions help establish what success means to the customer.
3. Show how you can help
Now connect your offering to the problem and the desired outcome.
Keep the explanation relevant. Describe the capabilities that matter most, provide an example if useful, and be honest about what the solution can and cannot achieve.
You are not trying to demonstrate everything you know. You are showing why this particular offering may be a good fit.
4. Ask what the person thinks
Do not assume that a clear explanation automatically creates agreement.
Ask for their perspective.
“Does this address the problem you described?”
“Is there anything important that I have missed?”
“Would this work with the way you currently operate?”
These questions reveal whether you have understood each other.
5. Explore the concern
If the person hesitates, resist the urge to launch into another presentation.
First, understand the reason.
They may be concerned about price, timing, implementation, risk, or whether the solution will deliver enough value. Each concern calls for a different response.
Sometimes they need more information. Sometimes they need reassurance supported by evidence. Sometimes the concern is legitimate and the offer needs to change.
And sometimes the product simply isn't the right fit.
6. Agree on the next step
Finally, establish what happens next.
That might be a demonstration, a proposal, a follow-up conversation, a trial, or a decision not to proceed.
A useful sales conversation should leave both people with a clearer understanding of the situation and what, if anything, should happen next.
Notice how little of this structure depends on a brilliant pitch.
It depends much more on listening, asking relevant questions, explaining clearly, and allowing the other person to participate.
Don't Try to Remove Every Doubt
One of the most common mistakes in selling is treating every unanswered question as a threat.
We want the customer to feel confident, so we try to eliminate every uncertainty before asking for a decision.
But not every doubt can be resolved immediately. Some questions require research. Some concerns can be answered only after a demonstration or trial. Some decisions involve risks that must be considered carefully.
Trying to remove every doubt can make a conversation exhausting.
It can also create the impression that we are uncomfortable with the customer thinking critically about our offer.
A better approach is to distinguish between the questions that matter now and those that can be addressed later.
If a customer wants to know whether a system integrates with their existing software, that may be essential before proceeding. If they want to understand an advanced feature they may never use, it may not need to be the focus of the first meeting.
If a customer is uncertain about the investment, the right response may be to clarify the expected value, discuss the costs honestly, and give them space to decide.
Confidence does not require the absence of every question.
It requires enough understanding to take the next sensible step.
And sometimes, the next step is simply to gather more information.
Silence Is Not Always a Problem
There is another reason we overexplain: we are uncomfortable with silence.
We ask a question, and the other person takes a few seconds to think. We interpret the pause as awkwardness. We begin talking again.
We present an offer, and the customer looks thoughtful. We worry that they are losing interest, so we add another benefit or offer a discount before they have even responded.
In doing so, we may interrupt the very process we wanted to encourage: the other person thinking through the decision.
A pause can mean many things. The person may be considering the offer, recalling their own circumstances, or deciding what they want to ask.
We do not have to fill every gap.
After asking a useful question, give the other person time to answer. After explaining an important point, allow them to respond. After presenting a proposal, let the customer consider it.
Silence is not necessarily rejection. Nor is it necessarily agreement.
It is simply space in which a person can think.
Learning to tolerate that space is part of learning to communicate well.
Simplicity Builds Trust
Clear communication does more than save time. It can also help people trust us.
When we explain something plainly, people have a better chance of understanding what they are agreeing to. They can see what is included, what is not included, what the costs are, and what they can reasonably expect.
When we hide behind jargon, vague promises, or complicated explanations, we create distance between ourselves and the person making the decision.
This is especially important when selling something unfamiliar.
A customer who does not understand the product may feel dependent on the seller's assurances. They may agree because they are impressed, confused, or reluctant to admit that they do not understand.
That is not the kind of confidence we should be trying to create.
Our goal should be to help people make informed decisions, even when that means they ask difficult questions or choose not to buy.
A clear explanation respects the other person's ability to think for themselves.
It says, in effect, “Here is what I offer, here is how it may help, and here is what you should know before deciding.”
That is a stronger foundation for a relationship