Introduction:

A promotion can look like proof that someone is ready to lead.

Sometimes, it only proves they were good at the job they had before.

Patrick Carter learned that distinction the hard way. One Friday, he was a salesperson. By Saturday, he was responsible for leading people who had been his peers the day before.

The instruction was basically: go make them do what you did.

It sounds familiar because versions of this happen inside companies every day. Someone produces. They know the product. They hit the numbers. They understand the systems. So when a leadership position opens, they look like the obvious choice.

Then the job changes.

Success is no longer determined only by what that person can do. It depends on what happens through the people around them.

That was one of the central ideas in my conversation with Patrick Carter, founder of Edge Advantage. After decades working across sales and leadership, Patrick kept seeing the same gap: organizations know how to measure performance, but performance and leadership are not the same skill.

As Patrick put it, **“That transition from individual contributor to leader is fraught. That transition is fraught. It's dangerous because not every top performer is built for leadership.”**

The promotion may change overnight.

The person usually doesn't.

And that gap can affect more than the new leader.

It affects everyone they're now responsible for

Real Story

Patrick told a story about an employee named Jorge.
When Patrick stepped into a new general manager role, he tried to get to know the different people and departments he was now leading. Jorge was different.
Patrick couldn't connect with him.
The explanation he received from another manager made the situation sound simple.
Jorge was a B player. He produced his numbers. He didn't cause problems. There wasn't much reason to worry about him.
Then came the sentence that revealed the real problem:
**“We don't have to spend time on him.”**
So they didn't.
Jorge came to work. He ate his lunch. He made his sales. He went home.
When the store needed someone to give a little more, Jorge wasn't volunteering.
From a management perspective, nothing was necessarily broken. He was doing the job he was being paid to do.
Patrick saw something else.
He noticed Jorge frequently watching soccer on his phone. One day, Patrick sent him a clip and asked a simple question:
**“Hey, have you ever seen anybody this good?”**
The wall came down.
Jorge started talking. He pulled up clips. He explained players Patrick didn't know. He even corrected Patrick's pronunciation of Pelé.
The conversation wasn't about a sales target. It wasn't a performance review. Patrick hadn't suddenly discovered a better incentive plan.
He had discovered a person.
Not long afterward, the store needed someone to come in early to help cover a shift.
Jorge volunteered.
Patrick's explanation for the change was simple:
**“Because he took a step to us, because we took a step to him.”**
Jorge didn't suddenly become a different employee.
Someone finally gave him a reason to engage differently.
And that reveals something a performance dashboard never could.

The Truth (why it matters)

Management Can Measure the Work Without Seeing the Person

The Jorge story would be easy to turn into a lesson about being nicer to employees.

That would miss the point.

The deeper issue is the difference between management and leadership.

Patrick described it this way:

**“You manage things and you lead people.”**

You can manage a process.

You can manage a product rollout.

You can manage a system.

You can measure whether someone arrived on time, completed the required work, hit the target, followed the procedure, or produced the expected number.

Those things matter.

But none of them automatically tell you what a person is capable of.

That's where organizations can create a blind spot.

The skills that make someone easy to identify as a high performer are often the easiest skills to measure. Their numbers are visible. Their results are visible. Their product knowledge is visible.

Leadership asks for something different.

A leader has to understand why one person is struggling while another is disengaged. They have to recognize when the problem is the employee, when it's the system, and when their own management may be contributing to it.

That requires more than knowing how the job is supposed to be done.

It requires curiosity.

Patrick saw that distinction firsthand when he was first promoted.

He went from salesperson to leader almost overnight. But knowing how to produce did not mean he automatically knew how to help other people produce.

Years later, he found language for the shift:

**“You stop selling to people and you learn how to sell through people.”**

That changes the job.

Your own strengths are no longer enough.

Now you have to understand the strengths sitting around you.

One person may connect better with younger customers. Another may understand the technology. Someone else may be able to translate a complicated idea into language everyone understands.

The leader's value isn't only in being the strongest person in that group.

It's in being able to see what the group contains.

That is difficult to do when the organization keeps rewarding the new leader for behaving like the top individual contributor they used to be.

The Leadership Problem Companies Can Accidentally Create

There is a tension here that Patrick and I kept coming back to.

Businesses need results.

Leadership doesn't erase that responsibility.

Patrick was clear about it. A leader still has to understand the systems, execute the processes, and produce the numbers the organization needs.

But an organization can say it values leadership while primarily rewarding management.

That creates a strange incentive.

A newly promoted manager quickly learns what gets measured.

Quota.

Margin.

Acquisition.

Productivity.

Compliance.

Those measures tell them whether the work is getting done.

What they don't necessarily reveal is what kind of environment is producing those results.

Patrick described the tension with a distinction that stuck with me:

**“You can be a great manager and be a horrible leader.”**

A manager can get compliance.

A leader has the opportunity to create engagement.

Those two things can look similar on a dashboard for a while.

The difference often appears in what Patrick calls **discretionary effort**.

There is compensated effort: the work someone agreed to perform in exchange for being paid.

Then there is everything they choose to give beyond that agreement.

The extra shift.

The idea nobody asked them to bring forward.

The willingness to help a teammate.

The interest in learning another part of the business.

The moment someone says, “I can come in.”

Patrick's point was that discretionary effort isn't something a manager is entitled to receive.

**“To get to the discretionary effort, the effort that that individual chooses to give, to get to that, you have to earn it.”**

That changes how you look at Jorge.

Before Patrick connected with him, Jorge wasn't failing.

He was giving the organization what the relationship had earned.

No more.

No less.

The Dashboard Isn't Wrong. It's Incomplete.

This is where the conversation gets more complicated.

It would be easy to make the numbers the villain.

They aren't.

A business that ignores performance eventually has another problem.

Patrick talked openly about that tension. Companies still need people who can operate the systems and drive the work. Leadership doesn't replace management.

The problem begins when the measurement becomes the entire picture.

A dashboard could tell Patrick that Jorge was a B player.

It couldn't tell him why.

It couldn't show whether Jorge had more to offer.

It couldn't measure what would happen if someone became curious enough to find the doorway into a relationship with him.

And it couldn't predict that the employee people said wasn't worth spending time on would eventually volunteer when the team needed something extra.

This applies to more than the employee being evaluated.

It applies to the person being considered for leadership too.

A top performer's numbers tell you what that person can produce.

They don't automatically tell you whether that person can develop someone else.

They don't tell you whether they can have a difficult conversation.

They don't tell you whether they can recognize potential that doesn't look like their own.

They don't tell you whether they know when to push, when to listen, or when the problem in front of them isn't actually a people problem at all.

The promotion doesn't answer those questions.

It exposes them.

The Other Side of the Leadership Gap

There was another part of my conversation with Patrick that matters here.

Development isn't only the company's responsibility.

Patrick challenged the idea that an employer is obligated to build your career for you.

Companies may provide training. They may offer mentorship, education, or opportunities to advance. Some will do this exceptionally well.

But Patrick's view is that the individual still owns their growth.

**“Whether you're an individual contributor and you want to move into management, you have to own your development.”**

That makes this a two-sided problem.

Organizations can promote someone without adequately preparing them for what leadership requires.

At the same time, people can accept leadership positions without recognizing that the skills that got them promoted may not be the skills the next role demands.

Both can be true.

That's part of why Patrick eventually built Edge Advantage.

His career gave him different views of the same problem: salesperson, manager, general manager, multi-store leader, and someone helping other leaders develop.

As he described his career during our conversation, each experience became another brick.

Eventually, the pattern was hard to ignore.

There are a lot of people carrying leadership accountability who were never really taught how to lead.

What To Notice

Before calling someone a people problem, notice what you're actually measuring.

Jorge's numbers told one story.

His behavior told another.

The relationship around him revealed something else entirely.

That's the tension worth sitting with.

When someone is doing exactly what their job requires but nothing beyond it, the easiest conclusion is that you've discovered their ceiling.

Maybe you have.

But maybe you've only discovered the ceiling of their current engagement.

That distinction matters because management tends to ask whether the employee is meeting the standard.

Leadership becomes curious about what the standard isn't showing.

Patrick described the qualities he watches for in people as **curiosity, drive, and enthusiasm** because those traits can reveal capacity that a current performance number may not capture.

The point isn't to ignore the numbers.

It's to recognize what they can and cannot tell you.

Sometimes a B player is a B player.

Sometimes Jorge is waiting for someone to notice there's a person behind the number.

Conclusion

Patrick said something near the end of our conversation that captures the tension leaders live with:

“We have two jobs: develop our people and grow the business in that order.”

The order matters because the two jobs aren't separate.

The people are how the business gets grown.

That's why promoting the best performer and handing them a team isn't leadership development.

It's a change in responsibility.

The development has to happen somewhere else.

Patrick's own career is proof of that. He learned leadership over years, across different roles, through mistakes, observation, curiosity, and people who gave him opportunities to become more than whatever his current position said he was.

That's also what he eventually gave Jorge.

He didn't lower the standard.

He looked beyond it.

And maybe that's one of the clearest differences between managing and leading.

Management tells you what someone is doing.

Leadership stays curious about what else might be there.

About Patrick Carter

Patrick Carter is the founder of Edge Advantage. After decades working in sales and leadership, Patrick built Edge Advantage around a problem he repeatedly encountered: frontline and mid-level leaders can be given responsibility for people and performance without receiving the development needed to lead well.

Edge Advantage provides training, development, and coaching for frontline and mid-level leaders. During our conversation, Patrick described its development track as a 12-month program that explores one leadership topic each month and connects those lessons back to the leader's actual team and work.

Learn more about Edge Advantage at edgeadvantage.net.

What's Your Next Move

Want to continue conversations like this with other entrepreneurs, founders, and leaders?

Join the Majority Media communities → https://community.majoritymedia.us/

Ready to work with me? → https://seanmatkinson.com/start-here/
Subscribe to The Strategic Thinkers Podcast to catch the rest of the series.