They Chose the Best Candidate

/null holding a coffee mug as a manager says, โ€œThey chose the best candidate,โ€ and /null replies, โ€œIโ€™m sure they did. Again.โ€

There are words that sound more objective than they really are.

โ€œThey chose the best candidate.โ€

Maybe they did.

But that raises a more interesting question.

Best according to what?

We tend to talk about hiring and promotion decisions as though there is a single scale somewhere measuring every candidate from worst to best.

There isnโ€™t.

There is a selection system.

That system decides what information matters, how that information is collected, which qualities are rewarded, who gets to make the decision, and ultimately what โ€œbestโ€ means.

Best Is a Measurement

Consider two candidates for the same position.

One may understand the work better.

Another may interview better.

One may have a stronger record of solving difficult problems.

Another may have more visibility with leadership.

One may challenge assumptions.

Another may feel like the safer choice.

None of those qualities automatically makes someone the right or wrong candidate.

But they are not the same qualities.

So when an organization says it selected the best candidate, what it really knows is that it selected the candidate who performed best against whatever criteria its process actually rewarded.

Those criteria may be deliberate.

They may also be largely invisible.

The Process Creates the Outcome

A hiring process is a system.

So is a promotion process.

Like any other system, the design influences the result.

If interviews dominate the process, people who interview well gain an advantage.

If previous visibility matters, people who have worked closely with decision-makers gain an advantage.

If credentials are heavily weighted, credentials gain value.

If managers are punished heavily for a bad selection, familiarity and predictability may become more attractive than uncertainty.

Again, none of those things necessarily means the process is unfair.

It means the process has incentives.

And incentives shape outcomes whether we acknowledge them or not.

What Are We Actually Measuring?

This is where the question becomes useful beyond hiring.

Whenever a system claims to identify the best person, product, idea, or solution, it is worth asking what the system actually measured.

  • What characteristics were considered?
  • Which characteristics were ignored?
  • How was the information collected?
  • Who decided what mattered?
  • What behavior did the process reward?
  • What assumptions were built into the decision?
  • What constraints affected the available choices?

Those questions do not prove the decision was wrong.

They tell us what the decision actually means.

Then Measure the Decision

There is another part of selection systems that interests me even more.

Organizations can spend enormous amounts of time evaluating people before making a decision.

Applications.

Interviews.

Panels.

References.

Assessments.

Scoring systems.

Then the decision gets made.

What happens next is more important.

Does anyone go back and determine whether the selection process actually predicted the outcome they wanted?

If the person succeeds, what did the process correctly identify?

If the person struggles, what did the process miss?

If the same kinds of candidates keep getting selected, do they consistently produce the desired results?

Without that feedback loop, an organization can repeat the same selection process for years without knowing whether it is particularly good at selecting people.

The process becomes proof of itself.

We chose the best candidate because our process chose them.

And we know the process works because it keeps choosing the best candidates.


Someone says:

โ€œThey chose the best candidate.โ€

/null considers the evidence.

โ€œIโ€™m sure they did. Again.โ€

The interesting part isnโ€™t whether he believes them.

Itโ€™s the word again.

Because repeated outcomes tell us something about a system.

The question is what.

Weโ€™re Like a Family Here.

/null holding a coffee mug as a coworker says, โ€œWeโ€™re like a family here,โ€ and /null replies, โ€œSo... nepotism or incest.โ€

There are phrases we hear so often that eventually we stop asking what they mean.

โ€œWeโ€™re like a family here.โ€

It sounds good.

Trust. Loyalty. People looking out for one another.

Then /null takes it literally.

โ€œSo… nepotism or incest.โ€

And suddenly the metaphor has a problem.

What Does โ€œFamilyโ€ Actually Mean?

The interesting part isnโ€™t whether the phrase is stupid.

The interesting part is why organizations use it.

Usually theyโ€™re trying to describe something positive. Trust. Commitment. Loyalty. Shared responsibility. People willing to help each other when things go sideways.

Those are good things.

But a workplace isnโ€™t a family.

A family relationship exists whether it is productive or not. A working relationship exists because two sides are exchanging value.

You provide time, judgment, knowledge, and effort.

The organization provides compensation, opportunity, resources, and an environment where you can hopefully do useful work.

That doesnโ€™t make the relationship cold.

It makes it honest.

Watch What the System Does

Iโ€™ve spent most of my career working with systems.

Technology. Security. Organizations. Processes. Teams.

One lesson transfers remarkably well between them: donโ€™t judge a system only by what it says it does.

Watch what it actually does.

A company can call itself a family.

Then the company has a bad quarter.

Budgets get cut.

Projects disappear.

Departments get reorganized.

People get laid off.

That doesnโ€™t automatically make the organization bad. Sometimes those decisions are necessary for the organization to survive.

But nobody announces at Thanksgiving that Grandma has been eliminated because her position no longer aligns with the familyโ€™s strategic priorities.

At least not at the better Thanksgivings.

So maybe โ€œfamilyโ€ isnโ€™t describing the system very well.

Ignore the Poster on the Wall

If you want to understand an organization, look at its incentives and behavior.

  • What behavior gets rewarded?
  • What behavior gets punished?
  • What happens when resources become scarce?
  • Who absorbs the cost when something fails?
  • What happens when someone delivers bad news?
  • Do the actions match the stated values?

A poster on the wall can say PEOPLE FIRST.

The operating system underneath it might say something completely different.

The operating system wins.

Every time.

Build the Relationship You Actually Want

None of this means people shouldnโ€™t care about the people they work with.

They should.

Some of the strongest relationships Iโ€™ve built came from working beside people through difficult problems.

Trust gets built when someone does what they said they would do. When they tell you they screwed up before you discover it yourself. When they share what they know. When they challenge you when youโ€™re wrong. When they show up when things go sideways.

None of that requires pretending weโ€™re related.

Maybe the better model is simpler.

We have a job to do.

We depend on one another.

We treat people fairly.

We disagree without destroying each other.

We share credit.

We take responsibility.

And when circumstances change, we tell people the truth.

That doesnโ€™t sound as warm as โ€œweโ€™re a family.โ€

But it describes something worth building.

Question the Abstraction

Language matters because language creates assumptions.

Once an assumption becomes familiar enough, we stop examining it.

Thatโ€™s where bad abstractions survive.

Sometimes the easiest way to test one is to strip away the comfortable meaning and ask what the words actually describe.

Organizations donโ€™t need to pretend employment is something it isnโ€™t.

They need to build relationships people donโ€™t have to pretend to believe in.


โ€œWeโ€™re like a family here.โ€

/null: โ€œSo… nepotism or incest.โ€