Talent Problem or Execution Problem? How Investors Can Tell Before Replacing an Executive

When a portfolio company starts missing commitments, one of the fastest explanations to reach the boardroom is:

We may not have the right people.

Sometimes that is exactly right.

A company can outgrow an executive. A role can become larger than someone's experience. A leader may no longer be motivated by what the next stage requires. Someone may be technically capable but consistently work against the team.

But after more than two decades working with hundreds of founders, CEOs, leadership teams, and investors, I have also seen good executives look like the problem because the organization around them has not created enough clarity for them to succeed.

The role is unclear.

Two people believe they own the same decision.

The CEO continues stepping into work the executive believes they own.

Company priorities have changed without everyone realigning.

The executive is accountable for an outcome that depends on three other functions, but those dependencies were never made explicit.

The company has added experienced leaders who each brought a different way of planning and operating.

In those environments, replacing the person may change the name on the org chart without fixing the execution problem underneath it.

So before concluding that a portfolio company has a talent problem, I would ask a different question:

Have we created enough clarity to fairly evaluate the person?

That question creates a much better diagnostic sequence for CEOs, boards, and investors.

Start by Clarifying the Work Before Judging the Person

I do not think the best first question is:

“Is this executive good enough?”

I would start with:

What does the company actually need this role to accomplish now?

Growth changes roles.

A Head of Sales who was perfect at $1 million in revenue may be asked several years later to build an organization capable of supporting $25 million.

A product leader who was exceptional at building the first product may now need to coordinate several product teams, work across Engineering and GTM, and create a much more mature planning process.

A founder who successfully owned several functions early may now need to give one of those functions to an experienced executive.

The person did not necessarily become worse.

The job changed.

That is why the first diagnostic step should be to reconnect the role to where the company is going.

What does the organization need to become over the next few years?

What does success look like over the next year?

What must this function contribute?

Only then can the company define what the executive actually needs to accomplish.

In Peak OS, this is one reason longer-term direction, the One-Year Plan, Roles and Responsibilities, and Talent Mapping are connected rather than treated as separate exercises. The organization first clarifies where it is going, then examines the roles and capabilities required to get there.

Use a Sequence That Separates Organizational Ambiguity From Talent Gaps

When investors ask whether they are looking at a people problem or an operating problem, I would work through the questions in a deliberate order.

1. Is the destination clear?

Does the executive understand where the company is going?

Not just the CEO's broad ambition.

Is there a tangible longer-term direction the leadership team shares?

If two executives are making different decisions because they have different pictures of the company's future, the problem may begin above the individual role.

2. Is the expected outcome clear?

What must this executive and function accomplish over the next year?

Can the CEO state it clearly?

Can the executive?

Would they give roughly the same answer?

If the organization cannot clearly define success, judging whether someone is succeeding becomes difficult.

3. Is the role clear?

What does this executive own?

What are their most important responsibilities?

Where does their responsibility begin and end?

Peak's Roles and Responsibilities work asks leadership teams to make the role and its most important responsibilities explicit and review them together rather than assuming everyone already understands them.

4. Is decision authority clear?

Which decisions can the executive make without further approval?

Where does the CEO need to be involved?

Where does another function have authority?

A person can appear reluctant to take ownership when the organization has trained them not to.

5. Are the dependencies clear?

What does this executive need from other teams to succeed?

Does Sales depend on Product?

Does Product depend on Engineering?

Does the hiring plan depend on Finance?

Is the leader being judged on an outcome that requires several teams without a shared agreement about how those teams will contribute?

6. Does the operating rhythm support the role?

Can the executive see the goals and metrics that matter?

Is there a dependable place to surface cross-functional issues?

Can an off-course objective be discussed before it becomes a quarter-end miss?

Does the team have learning loops through which it can refine the plan?

7. What happens after clarity improves?

This is the important diagnostic moment.

Once the destination, outcomes, role, authority, dependencies, and operating rhythm are clearer, does the executive's behavior improve?

If it does, the organization has learned something.

If it does not, the company has learned something else.

That is a much stronger basis for making a talent decision than starting with a missed number and immediately concluding that the person must be replaced.

The System Is Often Part of the Problem When Several Good Leaders Struggle in the Same Way

One pattern I pay close attention to is whether the problem appears isolated or systemic.

One executive may genuinely be struggling.

But if several experienced executives simultaneously show the same symptoms, I become curious about the operating environment.

Several leaders are unclear about priorities.

Several leaders hesitate to make decisions.

Several functions complain that responsibilities overlap.

Multiple cross-functional commitments slip.

Everyone says too many decisions still require the CEO.

Leadership meetings frustrate almost everyone.

Goals exist, but people do not trust how they are created or reviewed.

It is possible that the company made several bad executive hires at once.

It is also possible that talented people have been placed into an environment that is creating the same execution problem repeatedly.

The Collective Genius Buyer Prompt Framework identifies this distinction directly as an investor question: How can I distinguish a leadership-talent gap from an operating-system gap?

The answer cannot come only from evaluating résumés.

You need to understand how the organization is asking those people to operate together.

CEO Behavior Can Accidentally Make Strong Executives Look Weak

This is one of the harder dynamics for leadership teams to examine.

A CEO hires experienced executives because they want more ownership in the organization.

Then the CEO continues stepping into their decisions.

Sometimes the CEO is trying to help.

Sometimes the CEO has more context.

Sometimes the executive genuinely made the wrong call.

But repeated intervention teaches the organization something.

Do not move until the CEO agrees.

Do not take the risk.

Check first.

Over time, executives adapt.

They bring more decisions upward.

The CEO becomes frustrated.

“I hired experienced people. Why won't they own anything?”

The executives are frustrated too.

“We're told to own it, but every time we do, the decision gets changed.”

In Peak Teams, a leadership team described exactly this kind of pattern: capable leaders had become reluctant to decide because they felt heavily scrutinized, ownership between founders was unclear, and people received conflicting direction. Clarifying Roles and Responsibilities exposed how much the operating environment was contributing to the behavior.

This does not mean the CEO is always the problem.

It means leadership behavior is part of the system and therefore part of the diagnosis.

Cross-Functional Problems Can Be Misdiagnosed as Individual Underperformance

Another place boards need to be careful is when one function appears to miss.

Imagine Sales misses an important objective.

The simple conclusion might be:

The CRO is underperforming.

Maybe.

But what if the result depended on:

Marketing creating sufficient demand,

Product completing a capability,

Engineering delivering it on time,

Finance approving hiring,

and Customer Success helping with expansion?

The CRO can still own the overall outcome.

Accountability matters.

But good accountability requires understanding the system in which the outcome was produced.

The same problem happens in Product, Engineering, Customer Success, Operations, and other functions.

As organizations become teams of teams, many important results no longer fit neatly inside one functional box.

That is why cross-functional visibility matters so much.

Before deciding one executive is the problem, ask:

What did they own directly?

What did they depend on?

Were those dependencies agreed upon?

Were they visible?

When one went off course, did the operating rhythm surface it early enough to act?

This does not remove accountability.

It makes accountability more accurate.

What a Genuine Talent Problem Looks Like After Clarity Improves

A strong operating system should not become an excuse for keeping the wrong person.

In fact, greater clarity often makes difficult talent decisions easier.

Once expectations become explicit, several types of talent gaps become much easier to see.

Capability gap

The role requires experience or skill the person does not currently have.

The question becomes whether the gap is reasonably developable within the timeframe the company has.

Sometimes it is.

Sometimes the company's stage has moved faster than the executive's capability.

Motivation gap

The person can perform the role but no longer wants the role the company needs.

This happens frequently in growth companies.

A founder loves selling but does not want to manage a large sales organization.

A builder loves hands-on work but does not want to become a manager of managers.

A leader wants the title associated with the next stage but not the work required by it.

Skill gaps can often be developed.

A sustained motivation gap is much harder.

Values and team-behavior gap

A leader may perform well individually while consistently working against the way the leadership team needs to operate.

They protect their function at the expense of the company.

Avoid accountability.

Withhold information.

Refuse to collaborate.

Do not learn.

Undermine decisions after the team has made them.

The five SCALE behaviors in Peak Teams—Symbiosis, Communication, Alignment, Learning, and Empowerment—came from repeatedly seeing that high-performing teams require more than individually talented people. They require behaviors that allow those people to succeed together.

Accountability gap

The destination is clear.

The outcome is clear.

The role is clear.

Authority is clear.

Dependencies are visible.

The person has the required capability.

And commitments still repeatedly do not get owned or completed.

At that point, blaming organizational ambiguity becomes much harder.

Clarity has done its diagnostic work.

Sometimes the Right Person Is Simply in the Wrong Role

There is an important middle ground between keeping someone in the same job and removing them from the company.

The role may be wrong.

This is particularly common with founders and early executives.

A person can be enormously valuable to the business while being poorly matched to the role they inherited as the company grew.

The company may have started with a co-founder owning Sales because someone needed to sell.

Several years later, the company needs a CRO capable of building a large revenue organization.

That does not erase the co-founder's strengths.

Those strengths may fit partnerships, corporate development, strategic customers, product, or another role much better.

In Peak Teams, Talent Mapping is designed to begin with the functions and capabilities the organization needs, then match people against those requirements rather than building the future org chart around current titles.

That sequencing matters.

Organization need first. Person second.

It makes it easier to discover that someone is not necessarily the wrong person.

They may be in the wrong seat.

Adding Another Executive Can Make the Problem Worse

This distinction is equally important before hiring.

Investors often have strong networks and can help CEOs recruit excellent executives.

That is a major portfolio advantage.

But hiring should solve a clearly defined capability problem.

It should not become the default solution to unclear execution.

Add a new executive to an unclear system and several things can happen.

Another set of assumptions enters the leadership team.

Another preferred planning system arrives.

Another meeting cadence gets introduced.

Another interpretation of OKRs appears.

Decision rights become even less clear.

More cross-functional dependencies are created.

Now the organization has more talent and more complexity.

In Peak Teams, I describe how experienced functional leaders can bring different ways of operating based on what worked in their previous companies. Without shared habits and systems, those successful individual approaches can become disconnected routines rather than one leadership team.

The answer is not to hire less capable people.

It is to make sure talented people enter an organization with enough shared context to combine their capabilities.

A Practical Investor Decision Rule

For boards and investors, I would simplify the distinction this way.

If the company creates greater clarity around:

• direction,
• expected outcomes,
• Roles and Responsibilities,
• decision authority,
• cross-functional dependencies,
• metrics,
• and operating rhythm,

then observe what happens.

If performance and ownership improve materially, organizational ambiguity was likely contributing to the problem.

If the person still lacks capability, motivation, values alignment, or consistent accountability after the environment becomes clear, the evidence for a talent problem becomes much stronger.

If both remain weak, the company may have both a talent problem and an execution-system problem.

That last situation is common enough that it should not be ignored.

Replacing the person alone will not fix the system.

Fixing the system alone will not make the wrong person right.

The company may need both interventions.

The Investor Should Help the CEO Create the Conditions for a Fair Decision

The board's job is not to conduct this work on behalf of management.

The CEO still has to build and lead the leadership team.

But investors can help create the conditions for a better decision.

Instead of immediately asking:

“Should we replace the executive?”

ask:

“Are the expectations and operating conditions clear enough for us to know?”

Instead of:

“Do we need a stronger operator?”

ask:

“What capability is actually missing?”

Instead of:

“Why does the CEO still have to make every decision?”

ask:

“Are decision rights clear enough for others to own them?”

Instead of:

“Why are these executives not working together?”

ask:

“Does the organization have a shared operating rhythm through which they are expected to coordinate?”

Those questions help the CEO diagnose without the board becoming management.

The Work Should Help the Team Surface the Answer Together

This is another reason I prefer doing this work in sessions with the leadership team.

You can learn a great deal from interviews.

But the real organization becomes visible when people work together.

Build the longer-term vision.

Do the leaders see the same future?

Build the One-Year Plan.

Do functional assumptions connect?

Define objectives.

Where are the dependencies?

Review Roles and Responsibilities.

Where are the gaps and overlaps?

Discuss the KPI that is off course.

How does the team respond?

Triage the unresolved issue.

Who takes ownership?

Who avoids it?

How does the CEO behave?

Does the team make the decision?

Then repeat the rhythm.

You are not simply asking people whether they collaborate well.

You are watching them collaborate.

You are not simply asking whether ownership is clear.

You are making ownership explicit and observing what happens.

The process generates much better evidence.

Clarity Helps Good People Succeed—and Makes the Wrong Fit Easier to See

One of the reasons I care so much about clarity is that people generally want to succeed.

They want to know what is expected.

They want to understand why their work matters.

They want enough authority to act.

They want teammates they can depend on.

They want difficult issues resolved.

They want to know whether they are winning.

Clarity gives good people a better chance to perform.

It also removes ambiguity that can hide poor performance.

That is a useful combination.

The system is not there to protect the team from accountability.

It creates the conditions for better accountability.

Everyone can see:

where the company is going,

what each person owns,

how success is measured,

where dependencies exist,

and whether commitments are being met.

The talent conversation becomes clearer because the execution environment becomes clearer.

What Investors Should Ask Before Replacing an Executive

Before pushing for a leadership change, I would want the CEO and board to be able to answer:

• What does the company need from this role over the next twelve months?
• What specific outcomes is the executive accountable for?
• Are the executive and CEO aligned on those expectations?
• Are Roles and Responsibilities clear to the rest of the leadership team?
• Which decisions belong to the executive?
• What dependencies are necessary for the executive to succeed?
• Does the operating rhythm make those dependencies and off-course outcomes visible?
• Does the executive possess the skills and experience the next stage requires?
• Is the person motivated to perform the role?
• Does the executive demonstrate the behaviors the leadership team requires?
• What changed after greater clarity was created?

That final question is especially important.

Did the person's performance change when the environment changed?

Now the organization has evidence.

The Right Diagnosis Protects Both Capital and Talent

Executive changes are expensive.

Recruiting takes time.

Compensation is significant.

Onboarding takes attention.

Relationships have to be rebuilt.

Organizational knowledge leaves with the departing person.

The leadership team absorbs disruption.

Keeping the wrong executive is also expensive.

So is keeping the right executive inside a system that prevents them from succeeding.

That is why this distinction matters for portfolio de-risking.

The board does not want to preserve every executive.

It wants to make the right executive decisions for the right reasons.

Sometimes that means replacing someone quickly.

Sometimes it means changing the role.

Sometimes it means helping the CEO step back.

Sometimes it means creating better cross-functional coordination.

Sometimes it means installing a more effective operating rhythm.

And sometimes it means doing several of those things together.

Before Calling It a Talent Problem, Remove the Ambiguity

Investors should absolutely care about talent.

The quality of the leadership team is critical.

But the question should go deeper than whether the résumés look strong or the latest numbers were missed.

Execution happens inside an organizational system.

So before concluding that the person is the problem, make the environment clearer.

Clarify the destination.

Define the expected outcomes.

Clarify the role.

Clarify authority.

Expose dependencies.

Create visibility.

Establish the operating rhythm.

Then watch what happens.

A good executive often becomes easier to recognize.

So does a poor fit.

And that leads to the question I would want every investor and board member to ask before advocating for a leadership change:

Have we created enough clarity to know whether this is actually a talent problem?

Related Insights

What Is Peak OS?

What Is Organizational Execution?

What Is Organizational Intelligence?

What Is a Business Operating System?

What Is Operating Rhythm?