Every week, Built. Not Born. examines an assumption about work or leadership that deserves a harder look. We use current research, practical experience, and timeless principles to help you build better teams, stronger organizations, and, most importantly, a life by design.

We spend a lot of time teaching people what good looks like. Salespeople learn discovery frameworks, objection responses and qualification methods. New managers learn how to conduct one-on-ones, give feedback and hold people accountable. Then we give people opportunities to practice until the right behaviors start to feel natural.

I believe in practice. I also think we sometimes give it credit for developing something it cannot develop on its own.

The real test rarely happens when the conversation goes according to plan. It happens when the buyer says something you weren't expecting, an employee responds differently than you anticipated, or the situation no longer resembles the one you practiced.

I've spent a significant part of my career developing leaders and salespeople, and I have enormous respect for preparation. Great salespeople prepare. Great managers prepare. Great leaders rarely walk into an important conversation hoping they'll figure everything out when they get there.

But preparation has a weakness we don't talk about enough. You can become extremely good at performing something you've practiced without becoming particularly good at responding to something you haven't.

That matters because the most consequential moments in sales and leadership are often the ones that refuse to follow the script. A buyer you expected to discuss price suddenly questions whether they need to change anything at all. An employee you planned to coach about performance tells you they're considering leaving. An executive introduces a concern nobody on the account team anticipated.

The playbook may get you into the conversation. Judgment determines what happens next.

New research from Corporate Visions and the Florida State University Sales Institute gives us an interesting way to think about the difference.

Researchers followed 119 new inside-sales hires over 18 months. One group practiced repeatedly with AI role-play partners. Another learned largely by watching experienced sellers handle real sales conversations and evaluating what they observed. A third combined the two approaches.

Toward the end of the study, researchers tested what happened when the conversation followed the expected path and what happened when the buyer unexpectedly changed direction.

The AI-heavy group performed well when the conversation went according to plan, but their adaptability fell sharply when the buyer changed course. Sellers who had spent more time observing experienced sellers were better at adapting, while the strongest overall results came from combining observation with practice.

I don't think the most interesting lesson is about AI. It's about what practice actually develops.

Repetition can make a behavior more fluent. It doesn't necessarily teach someone when that behavior is wrong for the situation.

That requires judgment.

This happens all the time in sales. A new rep learns the discovery framework, practices the questions, rehearses common objections and eventually sounds confident enough that the manager decides they're ready.

But we've mostly tested whether they can perform what we've taught them.

A real buyer isn't obligated to cooperate with the training program. They don't introduce objections in the order they appeared on the slide. They may tell you price is the issue when price isn't actually the issue. They may answer the question you asked without giving you the information you really need.

Managers face the same challenge. You can teach a new manager a feedback model, give them a structure for a one-on-one and show them how to prepare for difficult conversations. But eventually an employee will say something that wasn't in the training.

The better someone becomes, the less their job is simply to remember what comes next. Their job becomes recognizing what is actually happening and deciding what to do about it.

That's where execution gives way to judgment.

Sales organizations value consistency for good reasons. We build methodologies, define stages, document questions and establish criteria for what should happen next. I wouldn't want a sales organization where everyone simply improvises.

But a methodology should help someone think. It shouldn't do their thinking for them.

Watch the best salesperson on your team and you'll often see something more interesting than perfect adherence to a process. They know when to slow down. They recognize when the buyer's stated concern isn't the real concern. They ask a question that wasn't on the call plan because something they just heard changed their understanding of the deal.

That doesn't mean standards don't matter. Good judgment requires something to judge against. The point of the playbook is to create a foundation, not a ceiling.

If our goal is simply compliance, executing the process may be enough. If our goal is performance in situations that refuse to behave predictably, people also need to understand why the process exists, what problem it is meant to solve and what signals should cause them to reconsider their approach.

There's another part of the research I find especially useful. The sellers who developed greater adaptability didn't simply practice more. They watched experienced sellers in real conversations, evaluated specific behaviors and compared their assessments with an experienced-seller standard.

Instead of being shown the correct response and asked to reproduce it, they had to watch something unfold, decide what mattered and form a judgment about what they were seeing.

Managers often miss this distinction because experience makes it tempting to provide the answer. A salesperson brings a stalled opportunity into a deal review, and the manager immediately tells them what to do. A new manager describes a difficult employee situation, and their leader gives them the words to use.

That can feel like good leadership because the problem moves forward. Sometimes that's exactly what the situation requires.

But if it becomes the way you consistently coach, the person can get better at bringing problems to you without getting better at solving those problems without you.

Instead of immediately giving the salesperson your read on the deal, ask what they think is happening and what evidence led them there. Ask what they may be assuming and what new information would cause them to change their approach.

Giving the answer is faster. Developing judgment takes longer.

If your people always need your judgment to make the decision, you may be solving problems without developing the person responsible for solving them.

Every team has knowledge that never made it into the training manual. An experienced seller hears something in a buyer's answer and knows to keep digging. A strong manager senses that an employee needs a different conversation. Someone who's handled dozens of negotiations recognizes a pattern before everyone else does.

We often call that instinct. I think much of it is experience that has become difficult to see. Years of making decisions, getting some wrong, adjusting and seeing what happened next create patterns experienced people recognize almost automatically.

Leadership has to make more of that thinking visible.

Don't just have a new salesperson listen to your best rep's call. Ask the rep why they changed direction when they did and what they heard that caused them to reconsider the plan. When an aspiring manager observes a difficult conversation, talk afterward about what they noticed and why you made the choices you made.

The goal isn't to create copies of your best people. It's to expose others to the thinking experience has taught those people to do.

This matters especially for people who want to become managers. One of the easiest traps for a strong individual contributor is assuming the expertise that made them successful will make them successful at leading other people.

Someone asks for help, so you tell them what you would do. They follow your advice, the problem gets solved and everyone moves on. Do that often enough and you become the person everyone depends on.

That may feel like leadership, but dependence isn't the same thing as development.

Your job as a manager isn't to become the answer key for everyone else's work. It's to develop people who can make increasingly good decisions without needing you in every one of them.

You have to make your thinking visible without requiring people to think exactly like you. That's one of the hardest transitions from individual contributor to leader.

Pay attention this week to how often you're teaching someone an answer versus teaching them how to arrive at one.

If you're leading a sales team, listen differently during your next deal review. When a rep describes a problem, resist solving it immediately. Ask what they're seeing, what they're assuming and what evidence would cause them to choose a different approach.

If you're an individual contributor who wants to lead, start studying decisions instead of only outcomes. When an experienced seller changes direction or your manager handles a difficult situation well, don't simply copy what they did. Try to understand what they noticed that caused them to do it.

And if you're responsible for training people, ask what you're actually testing. Can they reproduce the expected response, or can they recognize when the expected response no longer fits?

We need people who know the playbook. We also need people who can recognize when the play has changed.

This distinction between execution and judgment is one I'd like to explore further on On the Shoulders of Giants.

AI will make practice easier to provide. People can rehearse conversations, receive feedback and repeat scenarios far more often than a manager could facilitate personally. That's valuable, but more repetitions aren't necessarily the same thing as better judgment.

The leadership question is how we help people interpret situations, recognize patterns and make good decisions when there isn't an obvious answer.

Whether you prefer to watch or listen, we'd love to have you join the conversation.

🎙️ Listen on Apple Podcasts, Spotify, or wherever you subscribe to podcasts.

📺 Watch on YouTube @HighAchieverLeadership.

If someone forwarded Built. Not Born. to you, we'd love to have you join us by subscribing. Every week, we challenge an assumption about leadership or work and examine the timeless principles underneath it.

If this week's argument made you reconsider how you're developing people, pass it along to a manager, salesperson or future leader who might benefit from the conversation.

For years I’ve said: Poor leaders hurt people. Great leaders change lives. .

Great leaders teach, coach, set standards and share what experience has taught them. But eventually, they have to let another person wrestle with the decision.

That's uncomfortable because experience often means the leader can see the answer faster. But giving someone your answer and developing their judgment aren't the same thing.

A script can tell a salesperson what question to ask. A framework can tell a manager how to structure a conversation. A process can tell someone what normally happens next. None of them can make the decision when reality stops behaving normally.

The highest purpose of training isn't to create people who perform perfectly when everything goes according to plan. It's to develop people capable of thinking when it doesn't.

Until next week, keep building.

- Jeff Wells

Sources: Corporate Visions research study conducted in partnership with Dr. Leff Bonney and the Florida State University Sales Institute. Study: Practice Makes Permanent: Should You Let AI Onboard Your Reps?
Published: October 1, 2026