You’re Measuring the Wrong Thing (And It’s Costing You Everything)

Here’s the question that reveals whether your leadership creates excellence or exhaustion: Do you value productivity over capability? If you’re measuring how fast people work instead of how well they’re developing, you’re optimizing for the wrong outcome. And that mistake is costing you ten times the productivity you could achieve by building capability first.

Think about how most construction leaders approach performance. Someone’s working slowly. Production is behind. The schedule is slipping. So what do we do? We push harder. Work faster. Add hours. Put pressure on. Scream and yell. And somehow we expect that forcing urgency without developing capability will magically create better results. It doesn’t. It creates burnout, turnover, mistakes, and a workforce that never develops the skills to actually improve.

Adam Hootz, who grew up in construction with a senior superintendent father and started as a plumber’s helper, puts it bluntly: “When you develop capability, productivity will come tenfold.” Not a little bit better. Tenfold. Because when people know what they’re doing, when they’ve been trained properly, when they understand the process and have the skills to execute it well, they don’t need to be pushed. They flow. They produce at levels that brute force could never achieve.

The Pain of Pushing People Who Aren’t Ready

You’ve seen this pattern destroy good workers. Someone’s struggling with a task. They’re slow, making mistakes, or just not getting it. And instead of stopping to figure out why and developing their capability, you push them to go faster. Work harder. Catch up. And you watch them spiral. The mistakes multiply. The frustration builds. They either burn out and quit, or they settle into barely acceptable performance that you tolerate because you’re too busy chasing the next deadline to actually fix the problem.

That’s what happens when you value productivity over capability. You create a cycle where people never develop the skills to perform well, so you’re constantly compensating for their lack of capability by adding pressure, hours, or additional bodies. And none of that actually solves the underlying problem, which is that you never invested in building their ability to do the work correctly.

Adam shares an accountability meter that shows how this should work instead. Start with awareness. Make people aware of what needs to happen without telling them exactly how to do it, because they might have a better way. If they’re not performing, educate them on your expectations and tighten the guardrails a bit. If they’re still not getting it after education, coach them to figure out why. And here’s the critical step most leaders skip: if coaching isn’t working, stop looking at the person and look at your process. Is what you’re teaching making sense? Are other people succeeding with the same process? Maybe the problem isn’t the person. Maybe it’s how you’re developing capability.

The System Optimizes for Speed Over Development

Here’s what I want you to understand. The construction industry systematically optimizes for immediate productivity instead of long-term capability development. We promote people who can push work through quickly today, even if they’re not building teams that will perform better tomorrow. We reward fire-fighting and heroics instead of systematic training and development. And we create cultures where taking time to teach feels like a luxury we can’t afford because we’re always behind schedule.

But that’s backwards. When you chase productivity without building capability, you guarantee that you’ll always be behind. Because people who don’t develop skills can’t improve performance. They can only work harder at the same level of effectiveness, which creates diminishing returns as fatigue, mistakes, and turnover compound. The schedule pressure that prevents you from training is the direct result of not having trained people in the past.

Adam talks about how his company switched from productivity-first to capability-first thinking. They stopped measuring just output and started measuring development. They created dedicated time for training that wasn’t optional or dependent on schedule slack. They built systems where developing people’s skills was as important as hitting daily production targets. And productivity increased tenfold. Not through pushing harder but through people becoming more capable.

Think about the implications. If you could get ten times the productivity by investing in capability development instead of just demanding faster work, every hour spent training would return massive value. But most companies won’t make that investment because they’re trapped in the cycle of chasing today’s productivity at the expense of tomorrow’s capability.

The feedback loop matters enormously here. Adam mentions that the last to discover water is fish. If you’re working in an environment and you think you’re doing things right because nobody’s telling you different, how are you supposed to know you’re not meeting expectations? Feedback is critical for capability development. Does this person know the expectation? Are they performing to that expectation? If not, why not? And most importantly, are you giving them the feedback, coaching, and training they need to close that gap?

Building Capability That Drives Real Productivity

Let me walk you through how capability-first thinking transforms performance. First, you have to accept that developing capability takes time. Not leftover time when the schedule allows. Dedicated, protected time that’s built into how you operate. Adam talks about how they schedule training the same way they schedule concrete pours. It’s not optional. It’s how the work gets done properly.

Second, you have to stop overburdening people. When someone is working at 110 percent capacity just to keep up with today’s demands, they have zero capacity to learn, improve, or develop new skills. You’re extracting productivity at the expense of capability development. And that works for a while until that person burns out, makes a critical mistake, or leaves for a company that actually invests in their growth.

Third, you need systems for developing capability, not just good intentions. The accountability meter Adam describes is a system. Awareness, education, coaching, process evaluation, role reassignment if needed. It’s not just “try harder” or “figure it out.” It’s a structured approach to building capability systematically so people actually develop instead of just surviving.

Here’s what capability-first development looks like in practice:

• Protected time for training that’s scheduled and non-negotiable, not dependent on having slack in the schedule • Accountability systems that progress from awareness to education to coaching before considering performance issues • Feedback loops that tell people clearly whether they’re meeting expectations and what specific gaps exist • Process evaluation that questions whether the teaching method works, not just whether the person is trying hard enough • Respect for people that includes getting them in roles where they can develop capability and succeed

These aren’t nice-to-have extras when you have time. These are the foundations that create ten times the productivity by building people who actually know what they’re doing.

Why Capability Compounds and Pressure Doesn’t

If your project needs superintendent coaching, project support, or leadership development, Elevate Construction can help your field teams stabilize, schedule, and flow. We work with builders who understand that chasing productivity without building capability creates exhaustion and mediocrity, while developing capability first creates sustainable excellence that compounds over time.

Think about the difference in outcomes. When you push for productivity without capability, you get temporary gains followed by plateaus, burnout, mistakes, and turnover. You’re constantly replacing people who couldn’t develop under pressure, which means you’re always training beginners instead of building experienced teams. The productivity you squeeze out today gets lost tomorrow when people leave or make costly errors.

When you build capability first, productivity compounds. People who develop skills can teach others. They can solve problems independently. They can improve processes. They can take on more responsibility. And the productivity gains don’t disappear when pressure eases. They’re permanent improvements in how effectively work gets done. That’s the tenfold return Adam talks about. Not from working harder but from being more capable.

The challenge most companies face is breaking the cycle. You’re behind schedule, so you can’t take time to train. But you’re behind schedule because you didn’t train people in the past. And you’ll stay behind schedule until you make the decision to invest in capability even when it feels like you can’t afford to. Because that investment is the only thing that breaks the cycle of always being behind.

The Challenge: Measure Capability This Week

So here’s my challenge to you. This week, pause and reflect. Adam says we continue working without pausing to reflect, which prevents us from seeing patterns. So stop and ask: How much time do you spend developing capabilities? Does your company have systems to develop capability? Do you make intentional time for it, or do you value productivity more? Is it more important that concrete gets poured today or that people evaluate the process by which concrete gets poured so it improves over time?

Start measuring capability development alongside productivity. Track how many people you’re coaching. How much training time you’re protecting. How well your feedback systems work. Whether your accountability processes focus on building capability or just demanding results. And watch what happens to productivity when you prioritize the development that drives sustainable performance.

Stop looking at the person first and look at your process. Are you teaching well? Are you giving feedback clearly? Are you building capability systematically? Or are you just pushing harder and wondering why productivity doesn’t improve? The system either develops people or depletes them. Choose development.

As W. Edwards Deming said, “Learning is not compulsory. Neither is survival.” If you want to survive and thrive in construction, develop capability relentlessly. The productivity will follow tenfold.

On we go.

Frequently Asked Questions

How do I find time to develop capability when we’re already behind schedule?

You’re behind schedule because you didn’t develop capability in the past. Breaking the cycle requires making time even when it feels impossible. Schedule training like you schedule concrete pours—as non-negotiable work that must happen. The productivity gains will more than recover the time invested.

What if people leave after I invest in training them?

Some will leave. But the alternative is worse: never developing anyone, which guarantees you’ll always have inexperienced teams producing mediocre results. Train people well, treat them with respect, and most will stay. Those who leave take skills into the industry that raise everyone’s capability.

How do I know if the problem is the person or my training process?

Use the accountability meter. If one person struggles after awareness, education, and coaching, but others succeed with the same process, it might be fit for the role. If multiple people struggle, examine your teaching method first before concluding people are the problem.

Isn’t this capability-first approach too slow for construction schedules?

Short-term thinking says yes. Long-term reality says building capability creates tenfold productivity gains that make schedules easier, not harder. The “slow” investment in capability compounds into speed that pushing for productivity could never achieve. You’re choosing between temporary speed now or sustainable speed forever.

What’s the first step to shifting from productivity-first to capability-first?

Protect one hour per week for capability development. Make it non-negotiable. Use it for training, coaching, feedback, or process improvement. Track capability metrics alongside productivity metrics. Show the team that development matters as much as output. Build from there as results demonstrate value.