Is it really a people problem – or an operating setup problem?

Two managers keep escalating decisions that should not need to reach the top.

From the outside, the problem looks identical.

Neither manager appears to be taking enough ownership.

But underneath, the situations are completely different.

The first manager has clear authority, understands the outcome, and has repeatedly been told to make the call. They still avoid the decision because they lack the judgment or confidence the role requires.

The second manager is held accountable for the result but knows that important decisions are regularly questioned, reversed, or informally reserved for someone above them.

One person may be wrong for the role.

The other may be behaving rationally inside a weak setup.

If you diagnose both situations as a people problem, you may replace someone who could have performed well in a stronger setup.

If you diagnose both as a setup problem, you may continue protecting someone who is simply not strong enough for the role.

That is what makes these situations difficult.

The visible behavior is real. But it is not yet the diagnosis.

The person is the easiest part to see

A manager misses a deadline. A senior leader avoids a difficult conversation. A team lead escalates too early. An executive gives an update without making a recommendation.

The person is visible. The behavior is visible. The consequence is visible.

So the natural conclusion is:

They are not taking enough ownership.

Sometimes that conclusion is correct.

But ownership does not exist inside a person alone. It also depends on what the role is expected to produce, what authority comes with it, how priorities are resolved, and what happens when the person makes a difficult call.

Before judging the person, it helps to separate three possibilities.

Sometimes the person really is the problem

Not every performance issue is caused by structure.

Some people are not able or willing to carry what the role now requires.

The role may have grown beyond their capability. They may be strong technically but weak in judgment. They may work hard but avoid conflict. They may understand the expectation but still fail to follow through consistently.

Typical evidence includes:

• The expected outcome is clear, but performance repeatedly falls short.
• The person has enough authority but continues to avoid decisions.
• The same issue remains after direct feedback and reasonable support.
• They manage activity but do not take responsibility for the result.
• They avoid the difficult parts of the role, especially conflict, trade-offs, and consequences.
• Other capable people succeed under the same operating conditions.

In these situations, redesigning the organization will not solve the core problem.

The person may need support, a narrower role, or more time to develop. But the possibility that they are simply not right for the position has to remain on the table.

Sometimes the role is the problem

A capable person can still underperform inside a role that has never been defined properly.

This happens frequently as companies grow.

The role begins with one clear purpose. Then new responsibilities accumulate around it.

A customer issue lands there. A project needs an owner. Another function needs support. A founder or CEO asks the person to take care of something temporarily.

Temporary responsibilities become permanent, but the role is never redesigned.

Eventually, the person is expected to carry too many different outcomes with no clear order of priority.

Typical evidence includes:

• The role contains several competing purposes.
• Success is described through activities rather than outcomes.
• Multiple leaders expect different things from the same person.
• The scope has expanded without removing older responsibilities.
• The person is accountable for an area but not for a clearly defined result.
• The role was designed for an earlier version of the company.

In that situation, asking the person to take more ownership may only increase pressure.

They do not need a louder instruction. They need a cleaner role.

Sometimes the operating setup is the problem

The person may be capable. The role may appear clear on paper. But the surrounding operating setup still makes ownership difficult to exercise.

Responsibility may sit in one place while authority sits somewhere else.

A leader may own delivery but be unable to challenge sales commitments. An executive may be accountable for performance while shareholders continue intervening in operating decisions. A project owner may carry the deadline while every meaningful trade-off requires approval from the top.

The title says one thing. The actual flow of authority says another.

Typical evidence includes:

• Decisions are regularly reopened after they have been made.
• People are accountable for outcomes they cannot fully influence.
• Functions can block one another without a clear way to resolve the issue.
• Priorities change without explicit trade-offs.
• Important decisions are still informally reserved for the founder, CEO, board, or shareholders.
• People learn that acting independently creates more risk than escalating upward.

In this setup, hesitation can be rational.

The organization may say that it wants ownership while repeatedly teaching people that real authority still sits somewhere else.

Strong people can start behaving smaller than they are

When capable people enter an unclear operating environment, they usually test its boundaries.

They make a decision and see whether it holds. They challenge another function and see whether leadership backs them. They enforce a standard and see whether it is later softened or overridden.

If the organization supports the role, confidence and ownership tend to grow.

If decisions are repeatedly reversed, priorities remain fluid, or leadership intervenes unpredictably, the person learns to protect themselves.

They ask for approval more often. They escalate sooner. They present options instead of recommendations. They wait for consensus before making a difficult call.

From the top, this looks like weak leadership.

From their position, it may be learned caution.

This does not mean the behavior should be accepted indefinitely.

It means the company has to determine what is producing it before deciding how to act.

The pattern matters more than the isolated incident

One missed decision tells you very little.

A repeated pattern tells you more.

Look at where the same behavior appears.

• Is one person struggling while others perform well in similar conditions?
• Do several people become hesitant around the same decisions?
• Has the same role disappointed under more than one person?
• Do capable new hires gradually start escalating more than they did when they arrived?
• Does ownership weaken whenever the issue crosses functions?
• Do decisions repeatedly return to the same person at the top?

If the weakness follows one individual, the person deserves close examination.

If the weakness follows the role, the role may be badly designed.

If it appears across several roles and people, the operating setup is probably producing the behavior.

A cleaner way to test the situation

Before replacing someone or lowering your expectations, make the operating conditions explicit.

Choose one important outcome the person is expected to carry.

Then clarify:

• The result they are accountable for
• The decisions they can make independently
• The boundaries they must respect
• The support they can expect from other functions
• The issues that should be escalated
• The consequences if the outcome continues to drift

Then watch what happens.

Do they make decisions more confidently once authority is clear?

Do they resolve difficult issues instead of returning them upward?

Do they use the authority, or continue avoiding the weight of the role?

Does another function respect the mandate, or does the organization continue undermining it?

This does not require months of observation.

In many situations, the pattern becomes visible quickly once ambiguity is removed.

The two expensive mistakes

The first mistake is replacing the person without fixing the setup.

A new hire arrives with energy and confidence. For a while, the situation improves.

Then they encounter the same unclear authority, competing expectations, unresolved boundaries, and intervention from above.

Six months later, the company has a new person producing a familiar problem.

The second mistake is using the setup to protect someone who cannot carry the role.

Leadership keeps refining expectations, adding support, changing reporting lines, and giving more time.

Meanwhile, the person continues avoiding the judgment, conflict, or accountability the role requires.

The organization works around them. Standards weaken. Other people see that the gap has no consequence.

Both mistakes are costly.

One loses capable people because the company misdiagnoses its own operating friction.

The other allows weak performance to remain because the company is reluctant to make a hard call.

Make the diagnosis before making the judgment

The objective is not to become softer on people.

It is to become more accurate.

Strong organizations do not explain every performance problem through structure. They also do not blame every operating weakness on the nearest person.

They separate the evidence.

• Is the person capable of carrying the role?
• Is the role clear enough to carry?
• Does responsibility come with real authority?
• Does the wider organization support or undermine that authority?
• Has the person improved when ambiguity and constraints were removed?

The answer may still be that the person needs to leave the role.

But when that decision is made after the setup has been examined, it becomes a cleaner decision.

And if the person is capable, the company has a chance to recover performance without losing someone it should have enabled more effectively.

The Operating Friction Reset is designed for situations where performance, roles, authority, and leadership behavior have become too mixed to diagnose cleanly from inside the company.