How Much of an Executive’s Success Travels With Them?

By Jody Weiss

We give executives a lot of credit for what happened while they were there.

Revenue grew.

Margins improved.

The company professionalized.

An acquisition worked.

A successful exit followed.

Those results matter.

But after enough years of sitting across from executives with impressive track records, I’ve learned that the result is usually the beginning of the assessment, not the end of it.

Because those results also create one of the harder questions in executive assessment:

How much of that success actually belongs to the executive?

When that executive moves to the next company, most of what surrounded the result stays behind.

The CEO stays behind.

The team stays behind.

The systems, capital structure and brand stay behind.

The market conditions stay behind.

So when I’m assessing an executive, I want to move beyond what happened while they were there.

I want to understand what happened because they were there.

Start with the result. Then keep going.

Past performance matters. I don’t know how you assess an executive without it.

But I think we sometimes ask a result to tell us more than it can.

A company growing from $40 million to $120 million tells me the executive has operated through that period of growth.

It doesn’t tell me what they did to create it.

Maybe they joined a company with tremendous momentum.

Maybe they inherited an exceptional team.

Maybe capital was readily available.

Maybe the market was growing quickly.

Or maybe very little of the infrastructure required for the next stage existed when they arrived.

The result can’t tell me which one.

That’s why I want to know the mandate.

Amit Patel made a useful distinction in a recent discussion around this subject:

Did the executive build the system?

Did they inherit it?

Did they fix it?

Or did they scale it?

Those are very different assignments.

Two executives can have remarkably similar resumes and have done very different work.

The company size gives me context.

The mandate starts telling me what the executive was actually responsible for changing. We’ve made a similar case when it comes to leadership assessment as a business scales — the results a leader produced don’t automatically confirm they’re the right person for what the company needs next.

Understand the decisions.

Knowing the mandate gets me closer.

The next question is what the executive actually did with it.

This is where some of the most useful evidence may never appear on a resume.

Several experienced operators raised versions of the same issue in that recent discussion:

What happened when the executive couldn’t have everything?

What didn’t they fund?

Who didn’t they hire?

What didn’t they build yet?

What imperfection did they knowingly tolerate because another problem mattered more?

Those choices don’t produce very good resume bullets.

They can produce very good evidence of judgment.

David Kaylor raised the question of what happens when adding people or capital isn’t the answer.

That’s where I want to understand not only what an executive decided, but how they reached the decision.

Did they get close enough to the work to understand the problem?

Did they talk with customers or the people doing the work?

Did they challenge the assumption everyone else had accepted?

Did they understand why something was happening before deciding how to fix it?

Most growing companies eventually have more priorities than money, people or time.

The systems and resources may be different in the next company.

The judgment behind those decisions is much more interesting to me. It’s part of why we’ve pushed back on hiring the cleanest resume in the room — the judgment behind a decision rarely shows up in a bullet point.

Look at what they built.

Results tell me what happened.

Mandate tells me what needed to change.

Decisions start showing me how the executive thinks.

But I still want evidence that the executive left something behind that wasn’t there before.

What capability did they create?

What became possible because they were there?

Did they develop leaders who became stronger?

Did they create a planning process the organization could actually use?

Did they establish an operating rhythm that improved decisions?

Did they build a system that reduced the company’s dependence on them?

Doug Hardesty asked a question that has stayed with me:

What did they build that still runs without them?

I’ve come to think durability may be some of the strongest evidence we have that an executive built capability rather than simply produced a result.

It’s not perfect evidence.

There isn’t any.

A successor can strengthen what someone built. Continued investment matters. Markets change. Sometimes organizations keep processes long after they should have disappeared.

Executive careers don’t give us controlled experiments.

But something important changes once the executive leaves.

They can no longer personally carry the result.

When something they created continues producing value without them, I pay attention.

That doesn’t prove the executive can reproduce it somewhere else.

But it tells me considerably more than the result alone.

Did the executive change too?

There’s another piece that I think gets missed.

Companies don’t stay at one stage.

The executive shouldn’t either.

Anthony Zannini made me think more carefully about this.

At an earlier-stage company, an executive may need to personally own work that would sit several levels below them in a larger organization.

That may be exactly what the company needs.

But as the business grows, the same executive has to institutionalize the work, build the team and eventually relinquish responsibilities they once needed to carry themselves.

Some executives are very good at building but remain at the center of everything they built.

Others are excellent inside sophisticated organizations but struggle when the infrastructure isn’t there yet.

The executives who interest me most can recognize what the organization needs from them now without prematurely building for a company that doesn’t exist yet.

And when the organization changes, they can change with it.

That matters because the next company probably won’t meet them at exactly the same stage as the last one.

The evidence isn’t equal

That’s the distinction I’ve been working toward.

A strong result is evidence.

But the result is still intertwined with everything happening around the executive.

The mandate gets us closer to understanding their contribution.

The decisions they made under constraint get us closer to their judgment.

What they actually built gives us evidence of capability rather than simply outcome.

What continued working without them matters differently, because the executive is no longer there to personally produce the result.

And an executive who repeatedly adjusted what they owned, built and eventually relinquished as the organization matured gives us evidence that their capability wasn’t dependent on one particular stage.

None of those answers guarantees that an executive will reproduce a result somewhere else.

That’s not the standard.

I’m trying to understand which parts of the record belong to capabilities the executive can carry into a different environment.

That is a much harder question than asking how large the last company was.

And I think it’s a much more useful one. Getting that weighting wrong is exactly how mis-hires happen at the executive level — not because the resume was weak, but because the wrong piece of it got treated as proof.

Then there is one last problem

Even after you’ve convinced yourself that the capability travels, you still aren’t finished.

Does the executive want to do it again?

Shannon Griffith made that point in the original discussion.

An executive may have already proven they can build without infrastructure.

They may have created teams from scratch, worked through cash constraints, integrated acquisitions and carried responsibilities well outside their title.

They can do it.

That doesn’t mean they want their next five years to look anything like it.

Experience doesn’t just build capability.

It also teaches executives what they’re willing to sign up for again.

That’s particularly important in founder-led, PE-backed and growing companies, where the mandate may require considerably more building than the title suggests.

So when you’re considering the executive whose track record looks almost exactly like what the business needs next, separate two questions:

How much of that success can they bring with them?

And:

Do they want to bring it here?