Loading
HRIN

Free preview · Lesson 6 of 47

Foundations of HR judgment

From HR 101 | Fundamentals

What You'll Learn

  • A simple, repeatable way to think through everyday HR situations
  • Why policy alone rarely settles a real case on its own
  • How to weigh competing legitimate interests without freezing or picking a side too early
  • The thinking habit that underlies every other lesson in this course

Why This Matters

You've already seen HR judgment in action without naming it. Lesson 3 asked whose decision something really is. Lesson 5 asked how to stay confidential and objective when no one's watching. Both were really asking the same underlying question in different clothes: given the facts, the rules and the people involved, what's the sound thing to do?

This lesson gives you the actual thinking model behind that question, one you'll reuse in nearly every lesson from here on.

The Situation

A Simple Working Framework

When a real HR situation lands on your desk, it rarely comes with a clean answer attached. A useful way to work through it is to move through six questions, in order, before deciding anything:

What actually happened? → What does policy say, and not say? → What's missing? → Who's affected? → What would be fair and consistent? → Am I the right person to decide this?

  • What actually happened? Not the summary you were given, the actual facts. A manager saying "he's always late" is a characterization, not a fact. "Late five times in the last three weeks" is a fact.
  • What does policy say, and not say? Policy often covers the general case clearly but goes quiet exactly where the real complexity is. Knowing what it doesn't address is as useful as knowing what it does.
  • What's missing? What information would change your view of this situation if you had it? If you can name what's missing, go find it before deciding.
  • Who's affected? Beyond the obvious person, who else has a legitimate stake, a manager, a team, a customer, the organization's own consistency across similar cases?
  • What would be fair and consistent? Not what feels kindest in this one instance, but what you could defend applying the same way to a similar case next month.
  • Am I the right person to decide this? As Lesson 4 covered, decision rights don't automatically follow whoever is closest to a situation. Working through the first five questions doesn't mean you're also the one who should make the final call, sometimes the right next step is to hand a well-informed recommendation to whoever actually owns the decision.
Policy provides a framework. It doesn't eliminate professional judgment. If it could, HR wouldn't need practitioners, only a rulebook.

Working Through a Case

Kabir has been late five times in the past three weeks at a 60-person logistics firm. His manager wants HR to issue a written warning today, citing the attendance policy, which allows one after three unexplained late arrivals in a month.

Run it through the framework before agreeing:

  • What actually happened? Five late arrivals, confirmed by the swipe log, not disputed.
  • What does policy say? A warning is permitted after three. Technically, the threshold is met.
  • What's missing? Whether Kabir's lateness has a reason his manager hasn't asked about, and whether anyone has actually told Kabir this was becoming a problem.
  • Who's affected? Kabir, his manager, the rest of the team who show up on time and may notice if nothing happens, and the organization's consistency if this same pattern shows up again with someone else.
  • What would be fair and consistent? Depends entirely on what's still missing. That's the point, you don't know yet.
  • Am I the right person to decide this? Whether to issue a warning sits with Kabir's manager, not HR, HR's role here is to make sure the manager has the full picture before deciding, not to decide on the manager's behalf.

What Could Go Wrong

If HR skips straight to "policy allows a warning, so issue one," here's what the framework would have caught: Kabir's team switched to a new shift start time two weeks ago, communicated only in a team chat message he missed while on leave. He's been arriving on time for his old schedule, which is now fifteen minutes late for the new one. No one told him directly.

A warning issued without asking "what's missing?" would have penalized Kabir for a communication failure that wasn't his. It would also have gone unnoticed that at least one other team member has the same excuse and wasn't flagged, an inconsistency that surfaces only if someone asks who else this affects.

This is what "policy allows it" quietly hides: policy tells you what you're permitted to do, not whether you have enough information to know it's the right thing to do yet.

Practitioner Lens

The framework isn't about being lenient, and it isn't about slowing everything down into a legal review. Most situations move through these six questions in minutes, sometimes just a few follow-up questions before you act. The goal is diligence before action, not paralysis instead of action.

A useful gut check: if you can't currently answer "what's missing" and "who's affected" with any confidence, you're not ready to decide yet, you're ready to ask a few more questions. That's not indecision. That's the judgment working correctly.

Common Mistakes

  • Treating "policy allows it" as the same as "it's the right call." Policy sets a boundary of what's permitted. It rarely tells you whether now, in this specific case, is the right moment to use it.
  • Accepting a summary as if it were a fact. "He's always late," "she's difficult," "the team doesn't respect him," these are characterizations. Get the specific, checkable facts underneath them before deciding anything.
  • Skipping "who's affected" because the obvious person seems like the only one involved. Consistency across similar cases is often the stakeholder that gets forgotten, until someone else asks why two similar situations were handled differently.
  • Freezing because judgment feels subjective. The framework exists precisely so judgment isn't guesswork. If you've worked through all six questions, you're equipped to decide, even without total certainty.
  • Applying the framework inconsistently. Running through it carefully for a sympathetic case and skipping it for an unsympathetic one is its own form of unfairness.

Key Takeaways

  • A simple six-question framework, facts, policy, what's missing, who's affected, what's fair and consistent, and whether you're the right person to decide, can carry you through most everyday HR situations.
  • Policy provides a framework. It doesn't eliminate professional judgment.
  • "Policy allows it" and "it's the right call right now" are different questions. Confusing them is one of the most common judgment errors in HR.
  • Working through the facts carefully doesn't automatically mean you're also the one who should decide. Knowing when to hand a well-informed recommendation to the actual decision-owner is part of sound judgment, not a step short of it.
  • Judgment isn't about slowing everything down or avoiding a decision. It's about knowing enough, and knowing whose call it is, to make the decision well.

What comes next

  • Understanding the employee lifecycle
  • Defining work and writing effective job descriptions
  • Attracting and sourcing talent

And 43 more. See the full outline

That was one lesson of 47.

$25

One payment, inclusive of all taxes. Yours permanently, with every correction and addition we make later.

17 people looked at this in the last month

Create an account to enrol

Already have one? Log in. Buying a course is not an application to join HRIN.

PricingCancellation & RefundsDeliveryTermsPrivacyContact

HRIN is operated by ClanHQ Private Limited.