top of page

The Great Difference Between “We Treat Everyone the Same” and Actually Treating People Fairly

18 hours ago
9 min read

There is a phrase that sounds admirable in business:

“We treat everyone the same.”

At first, it sounds like equality.

  • No favoritism.

  • No special treatment.

  • No discrimination.

Everyone follows the same rules.

But there is a profound difference between treating everyone equally and forcing everyone through the exact same system regardless of their circumstances.

A company can say, “We treat everyone the same,” while simultaneously creating a process that is rigid, impersonal, automated, and largely outside its own control.

That is where the distinction becomes important.

Because sometimes “we treat everyone the same” actually means:

“We don't evaluate you as an individual. We put you through our process, send your information to a third party, accept the third party's decision, and tell you there is nothing we can do.”

That is not necessarily fairness.

It is standardization.

And standardization and fairness are not the same thing.


Equality Is Not Always Individual Fairness


Imagine two people applying for the same opportunity.

One person has an excellent financial history.

The other experienced a temporary financial crisis because of circumstances outside their control.

Both people may have demonstrated that they are responsible, capable, and trustworthy.

Yet the system may reduce their entire financial histories to a handful of numbers.

A credit report is pulled.

An automated screening system evaluates the information.

A third-party algorithm produces a recommendation.

The company receives the result.

And the applicant is told:

“We treat everyone the same.”

But what does that actually mean?

It may mean that the company has decided that the process is more important than the individual.

The applicant isn't necessarily being evaluated by a human being who understands the circumstances.

They are being evaluated by a system.


The Disappearing Decision Maker


This creates another fascinating problem.

When an organization makes its own decision, there is accountability.

You can ask:

  • Who made this decision?

  • Why did they make it?

  • What information did they consider?

  • Can they reconsider it?

  • Can I explain my circumstances?

  • Can someone with authority review my situation?

But increasingly, organizations outsource important decisions.

The company says:

“That's what the credit report says.”

Or:

“That's what the screening company returned.”

Or:

“Our system doesn't allow us to make exceptions.”

Or:

“The third party makes the determination.”

Suddenly, nobody appears to be responsible.

The organization isn't really saying:

“We evaluated you and decided no.”

It is saying:

“Our system evaluated you, and we accepted the result.”

That distinction matters enormously.


The Third-Party Decision Paradox


Outsourcing a decision can create the appearance of objectivity.

After all, a company might reason:

“If we use the same third party for everybody, then the process is fair.”

But consistency does not automatically equal fairness.

A consistently applied process can consistently produce inappropriate outcomes.

A computer can make the same calculation every time.

That does not mean the calculation captures the entire human reality of every person.

The third party may only see the information contained in its database.

It may not know:

  • what caused a financial hardship;

  • what changed recently;

  • whether the situation is temporary;

  • whether the applicant has recovered;

  • what assets or resources exist outside the report;

  • whether an unusual circumstance explains the result;

  • whether information is outdated;

  • whether the applicant has additional evidence;

  • or whether the individual deserves an opportunity to explain.

The system sees data.

The human being lives the story behind the data.


“We Treat Everyone the Same” Can Become a Shield


There is another problem.

Sometimes the phrase “we treat everyone the same” is used to end a conversation rather than begin one.

It sounds principled.

But it can become a shield against responsibility.

The organization doesn't have to think.

  • It doesn't have to investigate.

  • It doesn't have to exercise judgment.

  • It doesn't have to listen.

  • It doesn't have to make an exception.

  • It doesn't have to take ownership of the outcome.

  • It simply points toward the policy.

Policy → system → third party → decision.

And the organization stands at the end of the chain saying:

“Sorry. There is nothing we can do.”

But there is almost always a human decision somewhere in that chain.

  • Someone chose the policy.

  • Someone chose the third-party provider.

  • Someone chose the threshold.

  • Someone decided how much weight to give the report.

  • Someone decided whether exceptions would be permitted.

  • Someone decided whether human review would exist.

  • Someone decided whether an applicant could appeal.

The organization may have outsourced the execution of the decision.

It has not necessarily outsourced its responsibility for designing the system.


The Credit Report Problem


Credit reporting illustrates this issue particularly well.

A credit report is a useful financial tool. It can provide information about someone's credit history and help organizations assess financial risk.

But a credit score is not a complete biography of a human being.

It is a measurement generated from particular data and methodologies.

And depending on the type of credit inquiry, accessing a credit report can have different effects; for example, certain hard inquiries can affect credit scores, while soft inquiries generally do not.

That makes the design of screening processes particularly important.

If an organization requires an applicant to undergo a credit-related screening, there should be transparency about:

  • What is being checked?

  • Why is it being checked?

  • Who receives the information?

  • Who makes the decision?

  • Does the organization review the result itself?

  • Is there an appeal process?

  • Can the applicant provide additional information?

  • What happens when the report does not accurately represent the person's current circumstances?

Those questions are far more meaningful than simply saying:

“Everyone goes through the same process.”

The Difference Between a Rule and a Judgment

A rule says:

“Everyone must do X.”

Judgment says:

“Here is the rule. Now let's understand the circumstances and determine whether the rule is accomplishing its purpose.”

Rules are necessary.

Organizations cannot operate entirely through individual discretion.

But rules should serve a purpose.

They should not become substitutes for thinking.

Consider two approaches.


Approach One: The Rigid System


Applicant → Application → Credit Report → Third Party → Automated Decision → Rejection

The organization says:

“We treat everybody the same.”

Approach Two: The Accountable System

Applicant → Application → Appropriate Screening → Human Review → Context → Decision → Explanation → Appeal/Review Where Appropriate

The second system may still reject the applicant.

The difference is that someone actually owns the decision.

That is the critical distinction.


Fairness Requires More Than Identical Treatment


Suppose three people are standing outside a building.

One person is six feet tall.

Another is five feet tall.

Another is four feet tall.

You give all three people the exact same two-foot platform and announce:

“We treat everyone equally.”

Technically, everyone received the same platform.

But if the objective is to allow everyone to see over the wall, identical treatment did not necessarily produce an equal opportunity to achieve the objective.

This is the classic distinction between equality and equity.

The lesson is not that organizations should create arbitrary exceptions for everyone.

It is that the purpose of a policy matters.

If the purpose is risk management, then the organization should ask whether its process is actually measuring the relevant risk.

If the purpose is protecting an asset, does the screening method actually measure the person's ability to meet that obligation?

If the purpose is selecting a qualified person, does the process actually measure qualifications?

If the process is producing a decision that does not accurately reflect the thing the organization is trying to measure, then the organization should be willing to examine the process itself.


Technology Should Assist Judgment—Not Eliminate It


Modern companies have extraordinary technological capabilities.

Algorithms can process enormous amounts of information.

Artificial intelligence can identify patterns.

Automated systems can make organizations faster.

Third-party platforms can reduce administrative costs.

All of this can be valuable.

But there is a danger in confusing automation with wisdom.

An automated decision is still a decision.

An algorithmic decision is still a decision.

A third-party decision accepted by a company is still a decision.

Technology can help answer:

“What does the data show?”

It cannot always answer:

“What should we do about this individual?”

That second question requires judgment.


Who Owns the Consequence?


This may be the most important question.

If a company rejects someone because of a third-party report, who owns the consequence?

The applicant experiences it.

The third party generated the report.

The organization's system processed it.

But the organization ultimately decided to use that process.

Therefore, responsibility cannot simply disappear into the technology.

A mature organization should be willing to say:

“We use this system because we believe it serves a legitimate purpose. We understand its limitations. We are responsible for the decisions we make using it.”

That is leadership.


The Human Being Should Not Become the Data Point


  • A person can have a bad year.

  • A person can experience unemployment.

  • A person can experience divorce.

  • A business can fail.

  • A family can experience a financial emergency.

  • A medical emergency can create enormous expenses.

  • A temporary crisis can damage financial indicators.

None of this automatically tells us who the person is today.

The danger of highly standardized systems is that the historical record can become more important than the current human being.

The database says:

Score: X.

The system says:

Risk category: Y.

The organization says:

Application denied.

And the conversation ends.

But perhaps the better question is:

“What happened, what is the person's current situation, and what evidence do we have today?”

That does not mean ignoring risk.

It means understanding risk.


A Better Corporate Philosophy


A more mature philosophy might be:

“We apply consistent standards, but we do not surrender human judgment.”

That statement is fundamentally different from:

“Everyone goes through the same process, and the third party decides.”

The first approach says:

We have standards.

The second can say:

We have a system.

There is a difference.

Standards require accountability.

Systems can sometimes become excuses.


The GAWK Perspective


This distinction aligns closely with the employment philosophy GAWK seeks to establish.

GAWK's approach is not:

“Everyone gets exactly the same treatment regardless of circumstances.”

It is:

“Everyone deserves the same fundamental respect, dignity, consideration, and accountability.”

Those are different concepts.

Treating people fairly does not mean pretending everyone has identical circumstances.

It means establishing principled standards while retaining enough human judgment to understand reality.

That requires leadership.

It requires people who are willing to ask:

Does this policy actually accomplish its purpose?

Does this process measure what we think it measures?

What happens when the data is wrong?

What happens when the circumstances are extraordinary?

Can someone explain the decision?

Who owns the decision?

Can the decision be reviewed?

Those questions should never be considered inconvenient.

They are evidence of a functioning organization.


The Real Meaning of “We Treat Everyone the Same”


There are two very different meanings of that sentence.

The first is:

“We do not discriminate. We apply our legitimate standards consistently, and we treat every person with dignity.”

That is a powerful principle.

The second is:

“We will not consider your individual circumstances because our process does not allow us to.”

That is something entirely different.

The first creates fairness through principled consistency.

The second creates uniformity through inflexibility.

And when a third party makes the final determination, the organization can create an additional layer of distance between itself and the person affected.


The Ultimate Question


The real test of an organization's fairness is not whether everyone was pushed through the same door.

The real test is whether the organization is willing to stand behind the decision that comes out the other side.

If the answer is:

“The third party decided.”

Then ask:

Who selected the third party?

Who designed the process?

Who established the criteria?

Who decided there would be no flexibility?

Who decided there would be no meaningful human review?

Eventually, the chain leads back to the organization.

And that is where accountability belongs.


From “Same Treatment” to “Responsible Treatment”


A truly human organization does not have to abandon standards.

It does not have to eliminate credit checks.

It does not have to ignore risk.

It does not have to give everyone what they want.

It does not have to create unlimited exceptions.

What it should avoid is pretending that a rigid process automatically makes a decision fair.

Fairness requires consistency.

But it can also require context.

It requires transparency.

It requires accountability.

And, in appropriate circumstances, it requires the courage to say:

“The system gave us an answer. Now let's determine whether that answer makes sense.”

That is the difference between following a process and taking responsibility.

And perhaps that is the deeper lesson:

Treating everyone the same is not necessarily the same as treating everyone fairly.

A company can standardize its procedures.

It can automate its processes.

It can outsource its analysis.

But it should never outsource its responsibility to think.

People are not merely applications.Credit reports are not people.Algorithms are not judgment.Third-party decisions do not eliminate corporate responsibility.

The best organizations understand the difference.

They build systems that provide consistency without eliminating humanity.

And when a consequential decision affects a person's life, they are willing to put a human being back into the process and ask the most important question of all:

“Is this really the right decision?”

Available next action: Create a downloadable DOCX file here in this chat containing the editable prose above


Leonardo Mora

CEO of Vision

GAWK Corporation

Comments


bottom of page