How I Hired Wrong, Then Right

First Bad Hire Lessons: How I Hired Wrong, Then Right

October 12, 2026•5 min read

The first person I ever hired lasted eleven weeks. I remember because I counted, the way you count anything that's actively costing you money and sleep.

I'm telling you this now because I just brought on my first in-person team members in about four years, and within the first week I caught myself doing the exact thing that got me into trouble the first time: not writing anything down. So I went back to the system I built myself after that first disaster, cleaned it up, and realized other people probably need this too. It's the same conversation I have on repeat with the business owners I consult with. How do I hire. What do I even hire for. And is this going to make me money or just feel like it should.

The Hire That Almost Broke Me

Here's the embarrassing part. I didn't hire them because I had a plan. I hired them because I was drowning, saw a pulse and a resume, and figured “close enough” was a hiring strategy. It is not. It has never been a hiring strategy for anyone, ever, and I'm sorry it took a bad hire to teach me that.

I needed help. Badly. So I wrote a job posting that was basically a to-do list of everything I personally hated doing, posted it, and hired the first person who seemed nice in the interview. Nice. That was my whole bar. Nice, and available to start Monday.

Three weeks in, I realized I'd never actually told them what the job was, because I didn't fully know either. I was managing them the way you manage a fire you started by accident: mostly by putting things out as they happened. By week eleven we both knew it was over, and I was right back where I started, minus a lot of money and any remaining confidence in my own judgment.

What I Was Actually Doing Wrong

Here's the pattern, once I stopped being mad at myself long enough to see it. I had no real job description, just a vibe. I had no idea what the role actually cost me month to month, hours or dollars. And I was hiring on urgency instead of a system, which is a nice way of saying I was hiring in a panic and calling it decisive.

So I Built Myself an HR Pal

I got tired of my own chaos, so I built a system in Airtable I call My HR Pal. It has three tabs, and each one fixes a specific way I used to screw this up.

Tasks

The first tab is Tasks. Every repeated thing in my business lives here, tagged by how often it actually happens: daily, weekly, monthly, quarterly, one-time. Cold email writing, lead generation, analytics reports, whatever it is. Each task gets assigned to a role. Once a role has enough tasks stacked under it, I drop the whole list into AI and it hands me back an actual job description, instead of the vibes-based posting I wrote the first time around.

Team

The second tab is Team. Every role I've filled or plan to fill, who's in it, their hours per week, their hourly rate. The sheet does the math I used to avoid doing, weekly budget, monthly budget, so I have a real payroll number instead of a guess I was scared to look at directly.

Applicants

The third tab is Applicants. Every person who's applied, what job they're applying for, their resume and portfolio, my notes on them. No more losing a great candidate in my email inbox because I got busy for four days.

Hiring Right the Second Time

The next time I hired, I already knew the role, the tasks, and the real cost before I posted anything. The interview wasn't a vibe check. It was a conversation about a job that actually existed on paper. That hire is still with me, which tells you everything.

Is This Actually Going to Make You Money

Here's the part people don't expect. Once you've got your tasks assigned to a role in My HR Pal, you can see exactly what's still sitting on your own plate that a new hire would take off it. That's your ROI, in plain sight, before you spend a dollar. Not a gut feeling about whether you're “ready” to hire. An actual list of what you're currently doing that you shouldn't be.

How You Know It's Actually Working

Not every hire ties to a sales number, and that's fine, but you still need a way to know if this was a good call. Before you post the job, write down two things. Why you're hiring them, specifically, not “I need help.” And what it'll look like when it's working.

That second one matters more than people think. Because six weeks in, when you're annoyed and about to have one of those conversations, you'll have something to compare against besides your mood that day. Is the thing you hired them to do actually getting done, or are you frustrated about something you never told them mattered? One of those is a real problem. The other one is on you.

I don't have this perfectly figured out either. But having something written down beats going purely off vibes, which is how I got into this mess in the first place.

A Few Things People Ask Me

What if I don't have my repeated tasks written down anywhere?

Start today. Write down everything you did this week that you'll also do next week. That list is the beginning of a job description.

Is this overkill if I'm only hiring one person?

No. One bad hire is exactly how expensive this lesson gets.

Can I use this before I've hired anyone?

That's the best time. Build the job description before the panic, not during it.

I'm not going to pretend a spreadsheet fixes everything. But it fixed the actual problem, which was me hiring blind. If you want to skip the eleven-week version of this lesson, [Grab the My HR Pal Template] and duplicate it into your own Airtable before your next hire, not after.


first bad hire lessons learnedsmall business hiring mistakeshow to hire your first employeejob description templateemployee hiring system
Back to Blog

Connect With Me