You Don't Have a Hiring Problem—You Have a Role Design Problem

Construction business owners at $2-10M revenue keep telling themselves they'll hire better next time. But here's the truth: you don't have a hiring problem—you have a role design problem. That project manager position that's turned over three times in two years isn't failing because you picked wrong. It's failing because the job itself is set up to burn people out or bore them to death.

---

TL;DR — What You Need to Know:

• You're hiring from the same talent pool as everyone else, offering the same compensation, and expecting different results
• The role keeps turning over because you haven't defined what decisions the person can make without you
• Good people leave when they're expected to read your mind while doing excellent work for average money in a poorly defined role
• You think you need better screening—you need clarity about authority, scope, and success metrics
• The common denominator in three failed hires isn't the market. It's you.

---

Why does the same role keep failing no matter who you hire?

Because you're treating a design problem like a selection problem.

You've refined the job posting. You've added interview questions. You've started checking references more carefully. And you genuinely believe that this time, with better screening, you'll find the person who makes it work.

But the guys who can do what you need—the ones with judgment and initiative, who don't need their hand held—they're already working somewhere. Probably for someone who pays better or treats them better or at minimum doesn't make them guess what success looks like every day.

The role you're trying to fill has structural problems that no amount of interview refinement will solve. You've built a job that requires a unicorn: someone who'll accept average money to do excellent work in a poorly defined role while reading your mind. Then you're frustrated that unicorns aren't applying.

What does unclear authority actually cost you?

More than you think. And it's not just the cost of rehiring.

When you haven't defined what decisions your project manager can make without you, one of two things happens:

Option 1: They guess. They make a call on a change order, a schedule adjustment, or a supplier switch. Sometimes they guess right. Sometimes they guess wrong and you get mad. They learn that initiative is punished, so they stop taking it.

Option 2: They check with you on everything. Every decision flows through you. Your phone never stops. You complain they're not taking initiative, but you've never told them what initiative looks like. They feel micromanaged. You feel buried.

Either way, they leave.

Then you hire again. Same job description. Same compensation. Same lack of clarity about authority. And the cycle repeats.

The actual cost isn't just the $15,000-$25,000 to recruit and onboard a replacement. It's the project delays while the role sits empty. It's the client relationships that suffer during transition. It's the knowledge that walks out the door. It's your time spent interviewing instead of running the business.

But the biggest cost? You stay the bottleneck. The business can't grow past your personal capacity because no one else is empowered to make decisions.

What does a properly designed role actually look like?

It starts with three things most owners never define clearly:

1. Decision Authority

Not a vague "use your judgment" instruction. Specific boundaries:

• Which purchase orders can they approve without your sign-off? ($500? $2,000? $5,000?)
• Which schedule changes can they make unilaterally?
• Which client requests require your involvement versus theirs?
• When do they need to loop you in versus just inform you after?

If you can't answer these questions specifically, you haven't designed a role. You've created a guessing game.

2. Success Metrics

What does good performance look like? Not "do a good job" or "keep clients happy." Measurable outcomes:

• Jobs completed within X% of estimated hours?
• Client satisfaction score above Y?
• Rework below Z%?
• Forecast accuracy within a specific range?

Your project manager shouldn't have to guess whether they're succeeding. Neither should you.

3. Scope Boundaries

You've got a project manager reporting to you and three foremen, doing all the estimating, handling client calls, and somehow also managing the schedule. That's not a role. That's three roles crammed into one salary.

No wonder they burn out.

A properly designed role has clear boundaries about what's in scope and what's not. If the role genuinely requires all those responsibilities, it needs to be compensated accordingly. If it doesn't, stop expecting one person to do the work of three.

Why do you keep rebuilding the same broken role?

Because admitting the role is broken means admitting you designed it wrong.

And that's uncomfortable.

It's easier to blame the hire. "They weren't the right fit." "They didn't have enough initiative." "They couldn't handle the pace."

But if three consecutive hires have failed in the same role, the common denominator isn't them. It's you.

Here's what's happening: you've designed the role around your own gaps and preferences rather than around what the business needs. The PM role becomes a catch-all for everything you don't want to do or don't have time for. It's defined by subtraction (your workload minus this role) rather than by intention.

That's not role design. That's delegation theater.

And the people you hire can feel it. They know they're being set up to absorb chaos rather than create order. The good ones leave before they burn out. The mediocre ones stay and require constant management. Either way, you lose.

How do you fix a role that's designed to fail?

You stop hiring and start designing.

Before you post that job description again, do this:

Step 1: Audit the last person who left.

• What did they spend their time doing? (Not what the job description said—what really happened.)
• Which parts of the role did they handle well?
• Where did they consistently need your involvement?
• What decisions did they make that you later overruled?

This audit will show you where the role design broke down.

Step 2: Define decision authority in writing. Create a simple document:

• Decisions they own completely
• Decisions that require your approval
• Decisions where they recommend and you decide
• Dollar thresholds for each category

If you're not willing to put this in writing, you're not willing to empower someone. And if you're not willing to empower someone, you're hiring an assistant, not a project manager. Pay and position accordingly.

Step 3: Remove responsibilities that don't belong. If the role requires estimating, project management, client relations, and schedule management, you're hiring for four jobs. Either:

• Split the role into two positions
• Increase compensation to match scope
• Remove responsibilities until the role is doable

You can't have premium output at average cost with unclear expectations. Pick two.

Step 4: Set measurable success criteria. Within the first 30 days of the next hire, sit down and agree on:

• Three metrics that define success in this role
• How often you'll review them
• What "good" looks like for each

This isn't corporate performance review theater. This is clarity. If you can't measure whether someone is succeeding, you can't fairly evaluate them. And they can't win.

What will stop you from actually doing this?

The same thing that's stopped you the last three times: the belief that the next hire will just figure it out.

You'll tell yourself you don't have time to design the role properly. You need someone in the seat now. You'll hire fast, define loosely, and hope for the best.

Then six months later, you'll be hiring again.

The other thing that will stop you: admitting you're the constraint. If you define decision authority clearly and the person still has to check with you constantly, the problem isn't them. It's your inability to let go.

Role design forces you to confront whether you want to empower someone or whether you want to stay the center of every decision. Both are valid choices. But only one scales.

Bring This to Your Leadership Meeting

The Question: "What's the one role in this company that we keep hiring for but never fix?"

The Prompt: "Let's list every responsibility in that role as it actually exists today—not the job description, but reality. Then let's identify which responsibilities require skills or authority we've never clearly defined. What are we expecting someone to figure out that we should have designed?"

The Action: By Friday, [specific owner or operator name] will create a written decision authority document for the problem role: what decisions the person can make without approval, what requires sign-off, and specific dollar thresholds. Share it with one trusted peer outside the company for feedback before the next hire.

---

You don't need a better hiring process. You need a better role.

The next person you hire isn't going to magically fix what the last three couldn't. Not because they're not talented. Because the job itself is broken.

Fix the role. Then hire for it.

Clarity beats screening every single time.