# How to Spot (and Fix) the One Hiring Mistake That Costs Northern Colorado Owners the Most Time in Year Two
You hire someone. They're competent. They do the work. So why are you still in the weeds six months later?
The mistake isn't usually the hire itself. It's what you *don't do* after you hire them.
I've watched this play out enough times to recognize the pattern. An owner brings on a person—often a second or third employee—and assumes that person will figure out what "good" looks like by watching, or asking questions, or just knowing the industry. Then Year Two hits. You've grown. You're busier. And suddenly you realize your person is doing things the way they think is right, which isn't the way you'd do it, and now you're spending hours fixing work or redoing tasks that should be done by now.
That's the hidden tax of a hiring mistake that doesn't look like one. The hire was never bad. The onboarding was.
Here's what I mean by onboarding, because I don't mean a packet and a password:
The trigger is usually the second location, the second team member in a role, or the moment you realize you can't be in two places. That's when you suddenly need someone who doesn't just do the job—they need to do it *your* way, without you there.
If you haven't written down how you want critical stuff done—not everything, just the core work that touches customers, compliance, or money—your new person is flying on instinct. They're solving problems in real time. And then you have to unsee what they did and redo it your way. That compounds fast.
What this actually looks like:
A contractor brings on a project coordinator. Month one, the coordinator starts scheduling site visits and communicating with clients. By month six, you notice the coordinator's emails sound nothing like yours, promises are being made that don't match your capacity, and you're spending 30 minutes a week rewriting communication before it goes out. You hired for intelligence and reliability, but you never showed them what your standard for client interaction actually is.
Or a services owner adds a second technician. Both are competent. But one follows a diagnostic checklist, the other uses shortcuts you taught them but never documented. Now your quality is uneven, you're the tiebreaker when clients complain, and you can't scale because you're still the quality control.
The fix isn't complicated. It's boring.
Before or immediately after someone starts, spend time on the jobs that matter most:
- Write down the three to five things your best customers or projects have in common. What does "done right" mean for that work? - Walk through one real example with them. Not a manual. A real thing you've actually done. - Watch them do it. Correct it. Have them do it again. - Check in at week two, week four, week eight. Not a formal review—just "how's this piece going? Any gaps?"
This takes maybe four to six hours, spread across the first month.
The alternative is spending 15 minutes a week for the next 18 months second-guessing what they're doing, or redoing work they completed, or watching them make the same mistake twice because you never actually showed them the standard.
I've seen owners avoid this because it feels like micromanagement. It's not. It's the difference between hiring someone to do a job and hiring someone to *do your job while you do the next thing.*
If you've got someone in Year Two who's still creating work for you instead of taking it off your plate, this is almost always why. Not because they can't do it. Because you skipped the part where you showed them how you do it.
It's fixable. Late. But fixable.