Your Best Seller May Be Hiding a System Problem

Your store hits its sales target. Your strongest associate has another exceptional week. The team celebrates, and you move on to the next trading period.

But there’s a question the sales total can’t answer: how much of that performance belongs to the store, and how much belongs to one person?

A strong seller can improve the result while concealing the weakness underneath it.

They rescue uncertain customer conversations, remember the add-on everyone else forgets, follow up when others don’t, and turn hesitant shoppers into buyers.

Their contribution is valuable. The management risk begins when you mistake that contribution for evidence that the whole team knows how to sell.

A result can be repeatable for one person without being repeatable for the store.

That distinction changes what you coach, what you measure, and how confidently you plan.

An individual’s capability travels with them. Store capability remains available across shifts because several people can execute a reliable selling process.

You don’t need identical personalities or identical sales figures. You need enough shared competence that ordinary trading doesn’t depend on one exceptional person repeatedly closing the gaps.

The question isn’t whether your best seller contributes more. It’s whether the rest of the store can function effectively without borrowing their judgement.

Look for the rescue behind the result

Consider an illustrative footwear store with six associates.

Maya is the strongest seller. She asks thoughtful questions, explains fit clearly, and helps customers compare suitable options.

When someone hesitates, she can usually identify whether the issue is comfort, price, appearance, or uncertainty about the purchase.

The manager sees healthy weekly sales and assumes the team’s product training is working.

On the floor, a different pattern is developing.

One associate retrieves the requested size but rarely explores what the customer needs the shoes for. Another presents several alternatives without explaining their differences.

A third responds to “I’ll think about it” with “No problem” and ends the conversation.

When these interactions stall, they call Maya.

She joins the conversation, asks the missing question, narrows the choice, and helps the customer decide.

Depending on the store’s attribution practices, the sale might appear under her name or the original associate’s name. Either way, the store records revenue.

What the report doesn’t record is that several associates couldn’t independently complete the interaction.

Then Maya takes a week’s holiday. Sales soften. The manager initially concludes that the store simply misses its best seller.

That’s true, but incomplete.

The store also misses the person who’s been compensating for weak needs discovery, unclear recommendations, and premature endings to customer conversations.

Her absence exposes work the selling process wasn’t reliably doing.

This is why “sales fall when our best seller is away” is a signal to investigate, not a diagnosis.

A top performer might work the busiest shifts, serve established customers, or handle a more valuable category. Their absence could coincide with weaker traffic or unavailable stock.

You need to identify what disappeared: their own productive selling time, or the support that made other people’s selling time productive.

The second possibility reveals a deeper dependency.

Watch what happens immediately before the best seller steps in. Is another associate facing a genuinely unusual problem?

Or are they handing over a routine situation they should reasonably be able to handle?

Occasional help is healthy. Repeated rescue at the same point in ordinary interactions suggests a capability gap.

The moment of handover often tells you more than the completed sale.

Separate contribution from dependence

Use three questions to examine the pattern:

What does the person produce? What do they rescue? What can others reproduce?

The first question recognizes their direct contribution. Look at their own customer interactions and results, allowing for selling hours, customer opportunities, category, and responsibilities.

Raw sales rankings alone can confuse opportunity with skill.

The second question reveals hidden support. Observe where colleagues seek help and what the strongest seller actually does.

“Maya is better with customers” isn’t specific enough to guide coaching. “Maya asks what’s preventing the customer from choosing, while others keep showing more products” gives you something teachable.

The third question tests whether the capability belongs to the team. After watching Maya, can another associate make that same judgement independently in a different customer conversation?

Reproduction doesn’t mean repeating her exact words. It means recognizing the situation and choosing an effective response.

In the footwear example, the manager observes that Maya consistently establishes intended use before recommending products.

Other associates often begin with the shoe the customer picked up and stay focused on finding its size.

The manager now has a precise coaching priority: help associates connect the recommendation to the customer’s intended use.

That might mean asking whether the shoes are for daily walking, standing at work, occasional events, or another purpose. The associate then explains why a particular option fits that need.

The useful capability isn’t the question itself. It’s the connection between the answer and the recommendation.

An associate who asks about intended use and ignores the response has followed a script without improving the selling process.

This distinction prevents a common management mistake: copying the visible behaviour while missing the reasoning that makes it effective.

You can test transfer without engineering a difficult day or withholding help from customers.

Choose a routine selling situation that often triggers a rescue. Coach one associate on the missing judgement. Observe them handling comparable situations over several shifts.

Keep support available, but look for whether they can progress independently.

In this example, the manager watches whether the associate establishes intended use, recommends a suitable option, and explains the connection without calling Maya.

A successful interaction provides evidence of capability. Repeated independent execution provides stronger evidence that the improvement can survive normal variation.

Track the relevant behavior alongside the outcome. A sale can happen despite a weak interaction, and a sound interaction can end without a sale because the right product isn’t available.

Revenue matters, but it can’t tell you by itself whether the team has learned the process.

There’s another reason to examine rescues carefully: your best seller may be teaching dependence unintentionally.

If every uncertain associate hands the customer over, the immediate problem gets solved. But the associate may never practice diagnosing the hesitation.

The store protects today’s transaction while leaving tomorrow’s capability unchanged.

Instead of making the strongest seller the automatic closer, sometimes have them support the original associate through the decision.

Afterwards, ask what they noticed, why they chose that response, and what the associate will try next time. This requires time and judgement.

It shouldn’t interrupt service or turn every customer interaction into a training exercise.

Nor should development become an invisible extra workload for the top performer. If you expect them to coach, make that responsibility explicit and provide time for it.

Strong selling performance doesn’t automatically make someone a willing or effective teacher.

Your best seller should remain an asset whose strengths you recognize.

The management task is to identify which of those strengths can become shared capability and which reflect personal expertise that will remain distinctive.

Start with the routine gaps. Don’t try to reproduce everything that makes an exceptional person exceptional.

For each recurring rescue, ask: what judgement was missing, and who can now make it independently?

Until someone else can execute that judgement across ordinary situations, the store still depends on the person who supplies it.

And the next question becomes sharper: are you rewarding only the sales your strongest associate produces, or also recognising the system weaknesses their work keeps out of sight?