One of the quickest ways I learned to distinguish a strong functional leader from a business leader was to watch what happened when they didn’t get what they wanted.

As a CPO, I saw it all the time in promotion discussions.

A leader would come in with a strong case. Their person had delivered. The scope had grown. They were already operating at the next level. The retention risk was real.

Sometimes I agreed with every word.

But there was still another question to answer:

Did the business actually need the bigger role?

That was where I learned a lot about the leader making the case.

Some kept pushing, treating every concern as another objection they needed to overcome.

Others could hear the concerns from around the table, weigh them against what they knew about their person and their function, and come out with a different recommendation than the one they had walked in with.

Those leaders got my attention.

Because I knew they weren’t going to recommend something simply because it was good for their person or their function.

And that mattered the next time they came in pushing hard.

The job changes before everyone realizes it has changed

For much of your career, strong advocacy is rewarded.

You fight for resources. You make sure good people are recognized. You push when your team is stretched. You don’t let your priorities get ignored.

You get good at making the case.

And that helps you advance.

Then you get more senior and the job changes, often without anyone explicitly telling you it has.

You are still expected to advocate for your function. Of course you are.

But now people are also paying attention to whether you can distinguish what would be good for your team from what you believe the company should actually do.

I’m not sure leaders always realize how much they are being evaluated on that.

I see it with leaders I coach now. They know the business comes first. That isn’t the issue.

The harder part is that many of them built successful careers by being excellent advocates. They learned to push, make the stronger argument and get their teams what they needed.

At a senior level, there is another test:

Once I knew a leader could hear an argument that challenged their own, take it seriously, and change their recommendation because of it, I trusted their judgment differently.

And when that same leader came back six months later and said, “No, we really need this,” I listened differently too.

They had already shown me they wouldn’t always argue for their own side.

Promotions make this especially visible

This is what I kept thinking about after writing my latest BioSpace article on missed promotions.

In promotion discussions, two very different questions get collapsed all the time:

Is this person ready for the next level?

and

Does the business need the next-level role?

Someone can be excellent. Their judgment can be stronger, their influence broader and their contribution well beyond what it was when they took the job.

Their leader may be completely right that they are ready.

That still doesn’t tell you whether the company should change the organization.

One question cut through a lot of these discussions for me:

If this person resigned tomorrow, what job would we open to replace them?

Would we recruit at the higher level?

Or would we go right back to market for the job we already have?

If we would hire at the higher level, great. Now there is probably a case for the role as well as the person.

If we wouldn’t, that tells us something too.

Maybe we have a retention issue. Maybe compensation needs attention. Maybe we simply have someone whose career has moved faster than the company’s need for their role.

Those are real issues.

But “she deserves it” and “we might lose her” are both considerations. Neither creates organizational need.

When more evidence won’t change the answer

This was the part I saw leaders struggle with.

They still believed they could win the argument.

If the case wasn’t strong enough this cycle, they would make it stronger for the next one.

Give her another cross-functional assignment. Expand the scope. Get more exposure to the board. Demonstrate more strategic thinking. Come back next cycle with even more evidence.

From the leader’s perspective, this could feel completely rational: Surely if she proves enough, everyone else will eventually see what I see.

But what if everyone already sees it?

What if nobody is questioning whether she is capable of the next level?

What if the company simply does not need another level in that function?

Now you have someone spending another year trying to prove an answer that is already yes.

And you may be starting to look like the leader who doesn’t get it.

If you are being told the issue is the role and you keep coming back with more evidence about the person, eventually that starts to raise questions about your judgment.

That is when the question has to change from:

What else can she do to strengthen the case?

to:

What would actually have to change in the business for this role to make sense?

Maybe it is growth. A new program. A commercial build. Genuinely broader scope.

Maybe nothing on the horizon would justify it.

And once you accept that, the leadership task changes too.

You stop asking the employee to prove more and start being honest about what the company can actually offer:

I think you’re ready. I don’t think the business needs that role here right now.

That may mean she eventually decides she needs to go somewhere that does.

If that is a real possibility, then you better be developing the person behind her. Not because you want her to leave, but because creating a bigger job is not the only way to manage retention risk.

Think like the owner

Owning a business has made all of this much more visceral for me.

Every role I add is mine to fund. Every choice about where to invest shows up somewhere else as a choice not to invest. If I create a job the business does not need, I live directly with the consequences.

But I don’t think that is fundamentally different from how a senior leader inside a company should think.

At some point, you have to start making decisions as though you own the whole business.

Not just your function.

If I hire someone exceptional and they eventually grow beyond the job I hired them to do, I will want to keep them.

But their growth alone cannot determine what role I create next.

I still have to ask:

Would I build the company this way if this person weren’t here?

That is the owner’s question.

And it is one of the most useful questions a senior leader can learn to ask.

Try this: Change the question

The next time you are making the case for something significant for your function — a promotion, a hire, more budget, a new capability — make the strongest case you can.

Then ask yourself:

If this weren’t my function, would I still recommend it?

For a promotion: If this person left tomorrow, would I refill the job at this level?

For an investment: If I could put this resource anywhere in the company, would I still put it here?

The point isn’t to become less forceful on behalf of your people.

It is to notice whether your answer changes once you stop treating their interests, your function’s interests and the company’s interests as though they are automatically the same.

Sometimes they are. Sometimes they aren’t.

The leaders I trusted most knew the difference. They fought hard for their people and their functions.

But they could also look across the table and say:

“This would be good for us. But I don’t think it is what the company should do.”

That is when I knew I was talking to a business leader.