Draft
How to train a lead man to run jobs the way you do
You cannot train a lead man by talking at him. Here is how to make the way you run a job visible enough that he can learn it and run one himself.
You picked him because he is good with his hands and the crew already listens to him. Now you want him running his own jobs so you can stop being the answer to every question. So you take him for a ride-along, you talk his ear off about how you like things done, and you send him out. Two weeks later a job comes back half-right: wrong trim ordered, a customer change nobody wrote down, a bathroom called done that was not done. None of it was in your speech, because your speech was never the training. It just felt like it.
The problem is not that he is slow. The problem is that the way you run a job lives in your head, and a head is a hard thing to copy. You make forty small calls a day without naming any of them: which change is worth a phone call, what “clean” means on this customer, when done is really done. He cannot watch you make those calls, because you make most of them alone in the truck. Training him means getting those calls out of your head and into a place he can study. That is the whole promise of the foreman school guides: making the judgment on a job something a second man can see and learn.
Talking is not training
Think about how you actually learned the trade. Not from a lecture. You watched somebody good, you did it wrong, somebody corrected you, and you did it again until it stuck. The correction was the lesson, and it landed because it was tied to a real thing you had just done, not a rule read off a list.
A ride-along feels like that but is not, because a ride-along is one day and the job is a hundred days. He sees you handle one customer, one change, one inspection. He does not see the fifty judgment calls that make up a month, and by the time he runs his own job the ride-along is a blur. Talking gives him the words. It does not give him the reps.
The trades already know this, which is why the good ones pair a green man with a lead and let him watch for a season. What follows is the same idea, made faster, by using the record of how you run jobs as the thing he watches. Most of the job is moving information and making calls, as what a foreman actually does all day lays out, and you can only teach a call the lead can see.
Make the way you run a job visible
You cannot hand someone your judgment. You can hand him the trail your judgment leaves. Every job you run leaves one, if you are running it in a place that keeps a record: the address at the top, the change you approved on Tuesday, the photo you asked for before the drywall went up, the note where you told the crew the customer wants the gate latched every time.
Read your own last three jobs back like a stranger would. That record is a textbook on how you run work, written by you without meaning to. The lead cannot see inside your head, but he can read that. Every decision is sitting there with the reason next to it, and he can study it on a rainy Tuesday instead of shadowing you for a month to catch the same thing once.
That is the whole trick. You do not teach him by talking more. You teach him by making the way you run jobs something he can open and read.
The four-week plan
Here is a plan that turns your job record into a curriculum. It moves him from reading how you run jobs to running one himself with you watching.
Week one, he reads. Give him three or four of your closed jobs and have him read every one end to end. Not the highlights. The whole thread, in order, the way it happened. Then sit down for twenty minutes and have him tell you why you made three calls he saw: why the customer had to put that change in writing, why you held the sign-off until the photo came in, why you moved the crew when the inspector slipped. If he can explain your reasons, he has the standard. If he cannot, you found the gap before it cost you a job.
Week two, he shadows a live one. Now he watches a job in progress, but he watches the record, not just the site. When you approve a change, you tell him why in one line where he can see it. When you send a task back because the photo was not good enough, he sees the send-back and the reason. He is watching you make the calls in real time, with the reasons attached, which a ride-along could never give him.
Week three, he runs one under watch. Hand him a small job, one he can carry, and let him run it. You stay on the thread but you keep your mouth shut on site. When he makes a call, you let it ride if it is close enough, and you fix it in the record if it is not, in writing, calm, the way you would want to be corrected. Those correction notes are the actual lesson. They are tied to a real thing he just did, which is the only kind of correction that sticks.
Week four, he runs one and you review after. Same as week three, except you do not touch it during the day. You read the whole job at night and give him your notes the next morning: here is what you nailed, here are the two calls I would have made differently and why. By now the notes are short, because most of it he already did.
Four weeks does not make him you. It makes him someone who runs a job to your standard and knows why the standard is what it is. The knowing is what lets him handle the situation you never trained him for, because he is matching a reason, not a rule.
Your review comments are the curriculum
The part that does the teaching is not the plan. It is what you write when you correct him. “Redo it” teaches nothing. “This got marked done but there is no photo of the finished valve, and this customer disputes everything, so on his jobs the photo is what finished looks like” teaches him a rule and the reason behind it in one breath. Write those notes like you mean them to be reread, because they will be. The next lead you train can read the same ones.
This is also how a lead learns to hand a job across to another crew without dropping anything. Once he sees how you keep the details in the record, the handoff is just reading it, which is the whole point of handing a job between crews without losing the details. And once he understands who gets to call a job finished, he stops calling his own work done and runs it up to you, the plainer version of done, approved, signed off.
A lead you trained this way scales and a lead you lectured does not. The lectured one calls you every time something is not in the speech. The trained one has read a hundred of your calls and made twenty of his own under watch, so when the odd thing comes up he knows how you would think about it. That is the difference between a second man and a second you.
Crewmigo is built so this training happens without extra work. Every job is its own thread that remembers, so the record you would hand a lead to study is just there, made as you ran the work. Your corrections live on the tasks, the photo proof sits on the task that needed it, and the Mark done, Approve, sign-off order shows him who calls a job finished and who checks it. We are new, so put one job on it and run it the way you already do. When it closes, read it back and see whether a good man could learn your standard from it. That readable job is the training document you never had to sit down and write.
Crewmigo runs every job in a thread your crew already knows how to use, with the photo that proves it and a sign-off that closes it. One plan, one price a head. Subs ride free.
Start a job