Training Doesn't Happen in the Cracks Between Jobs

Construction business owners at $2-10M revenue complain about skill gaps while running the same crew assignments week after week with no intentional development built in. Here's the truth: training isn't something that happens — it's something you schedule or it doesn't exist.

---

TL;DR — What You Need to Know:

• "On the job training" is usually just hoping proximity to competence creates competence — it doesn't
• Training only exists if it's on the schedule with a specific person teaching a specific skill on a specific job
• You avoid scheduling training because it feels like slowing down when you're already behind
• What actually transfers without intentional training is the feeling that nobody knows what good looks like
• The fix: one conversation on Monday morning with names, skills, and a check-in date

---

Why does training happen in the cracks instead of on purpose?

You've built a company where training happens in the ten minutes before lunch when someone asks a question, in the moment of panic when the regular guy calls in sick, in the hurried explanation you give while someone's already mid-task and doing it wrong.

You call this "on the job training" because it sounds intentional. But it's just hoping that proximity to competence creates competence.

It doesn't.

You avoid scheduling real training because it feels like deliberately making the week harder. You're already behind. You're already short-handed. Taking your best carpenter off production to teach the newer guy how to run trim feels like choosing to lose money today for some vague future benefit.

And there's something deeper: scheduling training means admitting that the people you have aren't the people you need. That's uncomfortably close to admitting you didn't build what you thought you built.

What's actually happening when training lives in the cracks?

Here's what happens when you don't schedule training:

You run the same play every week. Put the best guy on the hardest work. Put the newer guy wherever he can't do too much damage. Hope that through some kind of osmosis the skills transfer.

They don't.

What transfers instead:

• The feeling that nobody really knows what good looks like
• The sense that everyone's just getting by
• The understanding that the standard is whatever the job tolerates
• The belief that certain jobs only work when certain people show up

You end up with the same mistakes happening over and over. Certain jobs only work when certain people show up. You can't trust anyone to run trim the way it needs to be run or lay out a foundation without you walking it twice.

The business doesn't grow skills — it accumulates people who can sort of do the work sort of right most of the time.

What does unscheduled training cost you?

Let's be specific about what this costs:

Operational costs:

• You lose your best people to constant firefighting instead of production
• Jobs take longer because the wrong skill level is assigned to the task
• Rework eats 5-15% of labor hours (industry standard per CFMA benchmarking data)
• You become the bottleneck because only you know how things should be done

Business value costs:

• Key person dependency scares off buyers — if Danny is the only person who can run footings, your business has Danny risk
• Labor efficiency stays stuck at whatever your top performers can personally produce
• You can't take on more complex work because you can't trust the execution
• Your adjusted EBITDA gets punished in valuation because the business doesn't run without you

Human costs:

• Your best people burn out from carrying everyone else
• Newer people feel set up to fail — because they are
• Frustration builds on both sides
• Nobody takes ownership because nobody was taught the standard

Why doesn't proximity to competence create competence?

You've watched it fail, but here's why:

Learning requires attention. When your lead carpenter is trying to frame a wall and answer questions from the helper at the same time, neither task gets full attention. The wall goes up crooked or the explanation is rushed. Usually both.

Competence is mostly invisible. What makes Danny great at setting grade isn't just the mechanics — it's the fifty micro-decisions he makes based on experience. The newer guy sees Danny working, but he doesn't see Danny thinking. Proximity shows him the actions, not the judgment.

Pressure kills learning. When training happens during a crisis — the regular guy called in sick, the inspector shows up early, the schedule just compressed — nobody's brain is in learning mode. They're in survival mode. The lesson that sticks is "figure it out and don't ask too many questions."

There's no feedback loop. In the cracks, nobody checks whether learning happened. The newer guy does the thing, it's probably fine, everyone moves on. Next week he does it wrong again because he never got confirmation that he understood it right.

How do you schedule training without destroying the week?

You don't need a training program. You need to admit that if it's not on the schedule with a name and a job attached, it's not happening.

Here's the whole thing:

Monday morning, you say this: "This week, on the Martinez job, Danny is going to teach Chris how to set grade, and I'm going to check their work Wednesday afternoon."

That's it. That's training.

What makes it real:

• Specific skill: "Set grade" not "learn formwork" — too broad to verify
• Specific teacher: Danny, not "whoever's around" — Danny now owns the outcome
• Specific job: Martinez job, not "next time it comes up" — it's on the schedule
• Specific check-in: Wednesday afternoon, not "eventually" — you're verifying transfer happened

What you're scheduling:

• 2-3 hours of Danny's time to teach instead of produce
• Chris shadowing Danny for one complete task cycle
• 30 minutes of your time Wednesday to verify Chris can explain it back and demonstrate setup

What you're not doing:

• Creating a training manual
• Pulling people off jobs for classroom time
• Building a competency matrix
• Implementing a formal apprenticeship program

Those might come later. Right now, you need one guy teaching one skill on one job with one check-in.

What will stop you from doing this?

You'll tell yourself you can't afford to slow down. Danny produces $800 in billable work per day. Taking him off production for three hours to teach feels like lighting $300 on fire.

But here's what you're already paying:

• Rework from Chris doing it wrong: 4 hours at $65/hour = $260
• Your time fixing it or walking him through it again: 1 hour at your actual hourly value
• The opportunity cost of never being able to assign Chris to grade work

You're already paying for training — you're just paying for the expensive, chaotic version.

You'll skip the check-in. Wednesday will come, something urgent will happen, and you'll tell yourself "Chris seemed to get it, Danny would have said something if there was a problem."

This is where training dies. The check-in is the only thing that verifies transfer. Without it, you're back to hoping.

You'll try to train too much at once. You'll get excited and schedule Danny to teach Chris three things this week. By Wednesday, none of them will have stuck because Chris's brain couldn't hold it all.

One skill. One week. Verify transfer. Move on.

What changes when training is scheduled instead of hoped for?

Here's what happens when you schedule training like it matters:

Immediate changes:

• People know what good looks like because someone showed them
• Your best people feel like teachers, not just firefighters
• Mistakes decrease because the standard was demonstrated, not implied
• You can assign work based on verified skills, not guesses

Longer-term changes:

• Jobs run without you because more people can do them right
• Your labor capacity increases without hiring because existing people can do more
• Key person dependency drops — the business isn't held hostage by Danny's availability
• The business becomes more valuable because it's less chaotic and less dependent on specific people

The human change:

• People take ownership because they were set up to succeed
• Your frustration drops because you're not confused about why the same mistakes keep happening — you know whether training happened or didn't
• Competence becomes the culture instead of "getting by"

What does scheduled training look like after six months?

Six months from now, if you do this every week:

• You'll have 24 documented skill transfers (one per week)
• Chris can now run grade, frame walls, set trusses, and manage his own punch list
• Danny has become a teacher, which means he's thinking about his work at a higher level
• You have a pipeline of people who can take on complexity instead of a crew that can only do what they already know
• Your schedule flexibility increases because you're not locked into "only Danny can do this job"

You don't need a training program. You need to stop pretending that training is happening when it's not.

Bring This to Your Leadership Meeting

The Question:

"Who on our crew right now is stuck at their current skill level because we've never actually scheduled time to teach them the next thing?"

The Prompt:

"Name one person and one skill they should learn in the next 30 days. Who's teaching it, what job will it happen on, and when will we verify they learned it?"

The Action:

By Monday morning, [Owner/Operations Manager Name] will schedule one skill transfer for this week: the person learning, the person teaching, the specific skill, the specific job, and the day you'll check their work. Put it on the weekly crew schedule so everyone sees it's real.

---

Let's slow the noise down. Training isn't a cultural value or a commitment to development. It's a conversation on Monday morning where you attach a name, a skill, and a check-in date. If it's not on the schedule, it's not happening. And right now, it's not happening.