The Most Dangerous Employment Decisions Are the Ones Without a Default

Over the years—both in Big Law and in-house—I’ve reviewed hundreds of employment decisions after something had already gone wrong. Pay disputes. Promotion challenges. Performance terminations that suddenly looked far less defensible than anyone expected at the time.

What consistently stood out wasn’t incompetence. And it wasn’t always bad intent.

It was something quieter—and more systemic.

The decision had no default.

By “default,” I don’t mean a policy sitting in a handbook. I mean the shared starting point—the normal sequence of steps that happens before a manager or HR partner exercises discretion.

No shared starting point. No baseline expectation. No common answer to the question, “What do we normally do here?”

Instead, each manager exercised independent discretion. At the time, each decision felt reasonable. Taken together, they formed patterns no one ever designed.

That’s where risk quietly forms.

Why decisions without defaults create risk—even when no one means harm

In behavioral science, defaults matter because they anchor behavior. They reduce variance by giving people a shared starting point. When no default exists, people must decide not only what to do, but how to decide in the first place.

Organizations are no different.

When companies tell managers to exercise discretion without giving them a baseline, discretion fills the vacuum. That discretion may be guided by thoughtful judgment. It may also vary widely depending on experience, incentives, confidence, or context. And in some cases, it may be influenced by bias—whether conscious or unconscious.

Here’s the uncomfortable truth many organizations overlook:

The absence of a default doesn’t just create inconsistency—it creates room for bad intent to hide.

When outcomes differ significantly across managers or teams, it becomes harder to distinguish good-faith discretion from favoritism, business judgment from retaliation, or flexibility from discrimination. Defaults don’t eliminate bad intent. But they constrain it. They narrow the range of acceptable outcomes and make deviations visible.

That visibility enables organizations to manage risk proactively rather than explain outcomes after the fact.

The unmarked intersection problem

I often think about this like an unmarked intersection.

Most accidents don’t happen at stop signs. They happen where there are no signs at all.

Each driver slows down. Each believes they’re being careful. But without a shared rule, someone eventually assumes the right of way.

Defaults are the stop signs of organizations. When they’re missing, collisions aren’t a matter of if—they’re a matter of when.

Where this shows up most often in real organizations

Most companies already have policies. What they often lack are defaults—the expected sequence of steps that happens before anyone improvises.

This gap shows up in familiar places.

Off-cycle compensation decisions.
There is no default for when exceptions are appropriate. One manager adjusts pay aggressively to retain talent. Another refuses on principle. HR reviews requests, but without an anchor. Over time, disparities emerge that look intentional—even when they weren’t.

Promotions and title changes.
There is no shared default for readiness. Some managers promote based on tenure, others on performance, others on advocacy. Employees compare outcomes, not rationales. What felt like flexibility becomes perceived favoritism.

Performance management and terminations.
There is no default for when concerns move from coaching to formal discipline. Some managers document early. Others wait. Terminations that felt justified individually look uneven side by side.

In each case, the issue wasn’t the decision itself. It was the absence of a shared starting point.

Defaults as organizational infrastructure

Once you start seeing defaults this way, it becomes clear they do far more than guide individual decisions.

Defaults create institutional memory.
They preserve how decisions are supposed to be made even after managers, HRBPs, or leaders move on. Without them, organizations forget faster than they learn.

Defaults reduce internal power imbalances.
In their absence, outcomes tend to favor the most confident, senior, or well-connected voices. Defaults act as equalizers, ensuring decisions don’t quietly drift toward influence rather than principle.

Defaults protect managers.
Without a default, every decision feels personal. With one, managers aren’t inventing solutions—they’re applying a framework. That psychological safety matters, and it reduces over-escalation driven by fear.

Defaults allow organizations to learn.
You can’t evaluate a deviation unless you know what the baseline was. Defaults make post-mortems about systems, not individuals.

Policies declare intent. Defaults determine behavior. Risk emerges in the gap between the two.

What this changes for in-house employment teams

For many in-house employment lawyers, the job can feel like being on call for every organizational emergency.

A manager wants to terminate. HR isn’t sure how to handle a performance issue. Someone asks for an exception. Something feels “off,” but no one can quite say why. The common response is the same: “Let’s loop in Legal.”

Over time, Legal becomes the default—not because every issue truly requires legal judgment, but because uncertainty has nowhere else to go.

This is what organizations without defaults create. When there is no shared baseline for how common employment decisions are handled, uncertainty travels uphill. Managers escalate because they’re unsure. HR escalates because there’s no consistent starting point. Legal becomes the catch-all for questions that feel risky simply because no one knows what “normal” looks like.

Defaults change that dynamic.

When there is a clear, shared process for handling recurring employment issues, many questions resolve themselves before Legal ever needs to weigh in. Managers know what steps come first. HR can apply the default with confidence. Escalation becomes deliberate rather than reflexive.

That shift matters because high-impact in-house legal teams are not defined by how many decisions they touch. They’re defined by whether they are focused on the decisions that actually require legal judgment—those involving real ambiguity, tradeoffs, or enterprise-level risk.

Defaults act as a filter. They keep Legal from being pulled into improvisation and reserve Legal’s attention for true exceptions. In mature organizations, Legal isn’t where uncertainty goes to die. It’s where deviations go to be evaluated.

The question that changes everything

After years of seeing the same patterns repeat, I now start with a different question:

“What was the default—and did we know we were deviating from it?”

If the answer is unclear, that’s usually where the problem began.

Defaults don’t eliminate judgment. They discipline discretion. They turn improvisation into intention.

And in my experience, that single shift—away from inventing decisions and toward designing them—does more to create harmony, efficiency, and defensibility than almost anything else organizations try to do after the fact.

Disclaimer:
This article is for general informational purposes only and does not constitute legal advice. Legal outcomes depend on specific facts, procedural posture, and evolving case law. Employers should consult experienced counsel regarding their particular circumstances.