Your Cart
Loading

What I'd Fix First If I Took Over HR at Your Company

What I’d Fix First If I Took Over HR at Your Company

Where Stability, Structure, and Scale Actually Begin

When I walk into a new company, I can usually tell within 30 minutes whether they have an HR problem.

Not because of what is written.

Because of what is not.

The hesitation when explaining how pay decisions are made.

The inconsistent answers about time off.

The manager who says, “We handled that situation,” but cannot explain how.

Most HR problems are not dramatic.

They are cumulative.

If I took over HR at your company tomorrow, here is exactly what I would fix first.

And no, it would not start with culture statements.

 

Phase One: Stabilize the Risk

Weeks 1 through 3 are about exposure.

Before I build anything, I audit for instability:

  • Undocumented performance conversations
  • Inconsistent discipline patterns across departments
  • Compensation decisions made without rationale
  • Contractor classifications that feel convenient
  • Overtime practices that have not been reviewed in years
  • Benefits eligibility inconsistencies
  • Managers improvising policy under pressure

This is where companies get surprised.

Not because they meant harm.

Because they lacked structure.

You cannot build engagement on top of legal fragility.

Stability comes first. Always.

 

Phase Two: Fix the Middle

This is where most companies underestimate the work.

Most organizations do not have an HR department problem.

They have a manager capability problem.

Between weeks 3 and 6, I focus almost entirely on the middle layer.

Are managers aligned on:

  • How to document performance
  • What progressive discipline actually means
  • When to escalate
  • How to approve pay adjustments
  • What “good” performance looks like
  • What they are not authorized to promise

When managers operate without guardrails, variance appears.

Variance creates inequity.

Inequity creates liability.

This is where quiet turnover begins.

This is where employees start comparing notes.

This is where the phrase “HR is inconsistent” gets whispered.

So I install structure:

Clear documentation standards.

Defined decision pathways.

Training that is practical, not theoretical.

Accountability for inconsistency.

Fix the middle and the noise level drops immediately.

 

Phase Three: Build the Architecture to Scale

Weeks 6 through 12 are about design.

Once risk is stabilized and managers are calibrated, I turn to infrastructure.

This is where HR stops reacting and starts leading.

I evaluate:

  • Compensation philosophy, not just pay rates
  • Performance management systems, not just annual reviews
  • Succession planning, not just emergency backfills
  • Workforce planning aligned to growth projections
  • Leadership alignment on standards
  • Metrics that actually matter

If your company doubled tomorrow, would your people systems hold?

Growth does not create cracks.

It exposes them.

 

The Questions I Would Ask Your Executive Team

If I joined your leadership meeting next week, here is what I would ask:

  • Can every manager explain how they make pay decisions?
  • Do we discipline consistently across departments?
  • Do we have documentation for every termination in the last 12 months?
  • Can we defend every independent contractor classification?
  • Who owns manager training?
  • If a lawsuit landed tomorrow, are we confident or hopeful?
  • If we grow by 30 percent next year, what breaks first?

The answers tell me everything.

 

What I Would Not Fix First

I would not start with a culture refresh.

I would not start with new HR tech.

I would not start with perks.

And I would not start by trying to make everyone happy.

Clarity beats popularity.

Consistency beats creativity.

Structure beats vibes.

Every time.

 

Why This Matters

Over the last twelve weeks, we have covered the patterns that quietly destabilize organizations:

Undocumented decisions.

Improvised policies.

Compliance blind spots.

Manager inconsistency.

Compensation ambiguity.

Red flags ignored until they are expensive.

They are rarely explosive in the beginning.

They are slow leaks.

There is a difference between knowing what to fix and knowing how to architect it correctly.

Awareness is helpful.

Architecture is leadership.

In the coming weeks, I will be going deeper for those who want more than theory.

More structure.

More decision frameworks.

More operational clarity.

Because if you are responsible for growth, people, or risk, stability is not optional.

It is engineered.