How to Separate Facts from Myths in HR

How to Separate Facts from Myths in HR

In human resources, many decisions are made quickly, out of habit, or because “it worked last year.” The problem is that HR is one of the areas where facts, impressions, and long-standing myths are easily mixed together. If a company wants to hire better people, reduce turnover, and set fairer processes, it needs to know what is proven, what is just a convenient explanation, and what is only a guess.

The good news is that this does not require complex theory. In important HR decisions, it is enough to pause and switch from fast thinking to slower, more careful reasoning. Fast thinking helps in everyday situations, but in hiring, performance reviews, or benefit design, it often leads to shortcuts and stereotypes. Slow thinking is more useful when a decision affects the team, costs, and the company’s reputation.

Where facts and impressions are most often confused

Many HR myths exist because they sound logical. For example, the idea that the most confident candidate will automatically be the best employee. Or that motivation can be solved with one universal benefit. In practice, it does not work that way because people respond differently to work, management, and rewards.

Another common issue is when one successful case becomes a rule. A company hires someone through a referral and the result is good, so people start believing that referrals are always better than other hiring sources. But one success does not mean the system is reliable. Facts need repeatability, not just a good feeling.

Typical places where mistakes happen

  • Hiring: deciding based on first impressions instead of comparable criteria.
  • Performance reviews: confusing popularity with results.
  • Benefits: assuming that what works for managers will work for the whole team.
  • Turnover: oversimplifying the issue with statements like “people leave only for money.”

Fast and slow thinking in HR decisions

Fast thinking is useful for routine work. It helps when a simple request must be handled, a basic problem solved, or an operational decision made. In HR, however, it becomes risky when short mental shortcuts are used to evaluate people. The brain naturally looks for simple explanations and groups similar signals into one conclusion. That is practical, but not always accurate.

Slow thinking means asking a deliberate question: Do I really have evidence for this, or only an impression? In HR, that matters when selecting a candidate, designing pay policy, setting goals, or handling conflict. It does not mean deciding slowly all the time. It means pausing when a decision will have a long-term impact.

When it is worth slowing down

  • when deciding whether to hire or reject a candidate,
  • when setting performance criteria,
  • when changing compensation or benefits,
  • when turnover is high or engagement is falling,
  • when the same problem keeps appearing in a team, but the cause is unclear.

How to tell a fact from a false belief

The first step is to be clear about what you are actually looking at. A fact is a statement that can be checked in at least one reliable way. A false belief usually rests on impression, tradition, or one experience. Between those two is a third layer: a general recommendation that may be useful, but not necessarily true everywhere.

In HR, it helps to ask three questions: What exactly are we observing? What does that really mean? What else could have caused it? For example, if employee satisfaction rises after a new benefit is introduced, that does not automatically mean the benefit was the main reason. Team leadership may have improved at the same time, workloads may have dropped, or communication may have changed.

A practical process for the HR team

  1. Define the claim precisely. Instead of saying “our hiring does not work,” determine whether the issue is candidate quality, the length of the process, or the success of onboarding.
  2. Separate observation from interpretation. The fact that a candidate seemed confident does not mean they are a good fit for the role.
  3. Look for comparison. It is better to follow more than one case or more than one experience.
  4. Check alternative explanations. The problem may not be the people, but the process, the leadership, or unclear expectations.
  5. Test on a small scale. Instead of changing everything at once, try the adjustment in one team or for one role.

The most common HR myths and what is behind them

Some statements are repeated so often in HR that they start to sound like truth. It helps to look at them with a clear head.

“A strong CV means a strong team member”

A CV shows experience, but not how someone works with others, handles stress, or performs in a specific environment. It can be a useful first filter, but not the final proof of suitability.

“People leave only because of pay”

Pay matters, but turnover is often also linked to leadership, unclear roles, weak feedback, or the feeling that there is no room to grow. Salary may be a trigger, but it is not always the only cause.

“More benefits automatically improve satisfaction”

Benefits matter when they address a real employee need. If they are disconnected from reality, people often see them only as an extra feature. Sometimes better workload planning helps more than another minor benefit.

“The most honest candidate is always the best one”

Honesty is important, but it is not enough on its own. Selection also needs to consider experience, working style, and fit with the role. A confident presentation can be an advantage, but it can also hide a lack of depth.

What is worth tracking in practice

If you want to make HR decisions more accurately, focus on data that can be compared over time. A large analytics project is not always necessary. Sometimes simple indicators are enough: how many candidates move through each stage of hiring, how many people stay after probation, where misunderstandings appear most often, or which roles keep bringing back the same problems.

The key is not to draw quick conclusions from those numbers. If results worsen somewhere, that does not automatically mean the HR team made a mistake. It may be a shift in the market, leadership, or workload. This is exactly where fast and slow thinking differ: fast thinking looks for an immediate culprit, while slow thinking looks for the real cause.

What to watch out for when interpreting data

  • a one-time result does not necessarily mean a trend,
  • higher satisfaction does not automatically mean higher performance,
  • lower turnover is not always positive if people are simply afraid to change jobs,
  • success in one team cannot be transferred to another without adjustments.

How to build better HR decision-making

The most practical approach is to build a simple habit: before making any important conclusion, check whether it is a fact, a recommendation, or just an assumption. In hiring, that may mean asking the same questions of all candidates. In performance reviews, it may mean separating results from personal impressions. In benefits, it is better to first find out what people actually use and what only looks good in communication.

It also helps to involve more than one evaluator. One person will always notice something different and is less likely to fall into their own mental shortcut. This does not mean the group will always decide better, but it does reduce the risk that a single first impression will shape the outcome.

If a company does not have much data, it does not need to wait for a perfect system. It can start with small steps: record reasons for departures, compare hiring success by role, ask regularly about barriers at work, and check whether problems repeat. Even simple trend tracking is better than relying on feeling alone.

Conclusion

In HR, impressions can never be fully removed, but their influence can be reduced. If you slow down for important decisions, check the source of a claim, and look for alternative explanations, you increase the chance of acting on reality rather than myth. That is the difference between a quick estimate and a decision that creates longer-term value for the company.

What role does intuitive feeling play in your decision-making compared to facts?
Select an answer:
In a situation where someone is telling you something that seems interesting, but you don't have enough evidence, how do you react?
Select an answer:
How do you approach new information that contradicts your previous beliefs?
Select an answer:
How do you make decisions when you have several contradictory statements but no direct evidence to support any of them?
Select an answer:
How do you react to situations when someone makes decisions based on assumptions that seem obvious but are not backed by facts?
Select an answer:
How do you feel about information presented in an emotional tone, even when you don't have enough facts to verify it?
Select an answer:
If you find that you have made a decision based on unverified information, what is your next step?
Select an answer:
How do you recognize that something is more of an assumption than a fact?
Select an answer:
If you have two options to choose from, with one based on quick intuition and the other backed by facts, what do you do?
Select an answer:
How do you react when someone claims that something is true, but has no concrete evidence to support it?
Select an answer:

Your personal data will be processed in accordance with our privacy policy.

You might be interested in