Good People Eventually Get Tired of Carrying Bad Systems

SBE FIELD NOTE · PEOPLE

A strong employee can make a weak business look healthier than it is. They remember what nobody documented, calm customers after preventable mistakes, train new people without being asked, and quietly translate the owner’s preferences for everyone else. From the outside, that looks like a successful hire. From the employee’s perspective, it can feel like carrying a business that refuses to learn. Good people will often compensate for disorder because they care. That generosity creates a dangerous illusion: the system appears to work, so the owner does not see the cost being transferred onto the team. Eventually the employee is no longer doing one role.

They are doing the role, interpreting the system, managing exceptions, protecting coworkers, and absorbing the consequences of unclear decisions.

Two minutes to see your business more clearly. Start now.

Begin Your Free People ClarityScan™

What This Problem Is Really Telling You

The first hiring decision exposes this problem early. Owners often advertise for relief rather than define an outcome. They want someone reliable, motivated, flexible, and willing to help. Those qualities sound reasonable, but they do not describe what success must look like. When the target is vague, resumes all look similar, interviews become personality contests, and onboarding becomes a stream of corrections. The employee is then evaluated against a standard the owner can feel but never clearly stated. That is not a fair test of talent. It is a definition problem disguised as a hiring problem.

Why Candidates Begin to Look the Same

You're staring at a stack of applications, and every one of them says almost the same thing. “Hard worker.” “Team player.” “Reliable.” By the fourth resume, you can't remember what made the third one different from the first. So you do what most owners end up doing: you pick whoever seemed nicest in the fifteen minutes you talked to them, cross your fingers, and hope “nicest” turns out to be the thing this job actually needed.

The Limits of Hiring by Instinct

The plan, if you can call it that, is usually: post the job, talk to a few people, go with your gut. Your gut's gotten you this far in business, so it feels safe to trust it here too. Except your gut was built for reading customers and suppliers, not for reading whether a stranger can actually do a job you've never once had to explain out loud before. Here's where that gut instinct quietly sets you up to fail, and it's not where you'd expect it to.

Define the Role Before Judging the Person

Ask yourself something simple: what, specifically, is this hire supposed to be able to do that you currently can't stop doing yourself? Not “help out.” Not “take some pressure off.” Specifically. If you can't answer that in one sentence, here's what's actually happening, and it happens to almost every first-time owner. You didn't design a role. You designed a feeling. The feeling of relief. And feelings don't show up on a job posting, so what you post instead is a vague list of duties that could describe half the people who apply. Every one of them looks roughly qualified, because you never defined what “qualified for this exact gap” even means.

So the interview quietly turns into a personality contest, because personality is the only thing you actually have left to go on. You ask “tell me about yourself.” You ask if they're a team player. Nobody ever says no to that question, so it never actually tells you anything you didn't already know. A lot of owners fall into a second trap right about here, too: without a real target, you start unconsciously hiring for whoever reminds you most of you. Same energy, same sense of humor, somebody you'd want to grab lunch with. That might make for a good coworker.

It says nothing about whether they can run the register alone during a Saturday rush. Then you hire someone likeable, and a few weeks in, you realize likeable was never the problem you were trying to solve. The problem was that Tuesday afternoons fall apart because nobody but you can run the register during the lunch rush. Nothing about “seemed nice in the interview” tells you whether someone can actually do that.

This is the part that quietly wrecks first hires: the job was never defined, so the hiring process couldn't select for it, so the interview couldn't test for it, and the new hire, through no fault of their own, was set up to miss a target nobody ever actually pointed at. Six weeks later, you're standing there wondering why you're still doing the exact same thing you hired someone to take off your plate. It's not because they're lazy. It's because “take some pressure off” was never a job. It was a wish, wearing a job title.

And when it doesn't work out, the story owners tell themselves is “I'm bad at hiring,” or “good help is hard to find around here.” Almost never true. The real story is simpler, and a lot more fixable: you interviewed for a feeling, not a function.

The Definition Problem

Here's the mechanism, and it changes how you look at every hire after this one. You don't have a hiring problem. You have a definition problem.

What First-Hire Experience Teaches

I see this constantly, and it's not about industry. Trades, retail, food service, doesn't matter. Good owners, good people skills, and the first hire still goes sideways, for this exact reason, more often than not. When I hired my first employee at the donut shop, I posted “counter help, reliable, morning hours.” That's it. Four words on a job board, tops. I interviewed four people, liked two of them, and hired the one who seemed most awake at 6am, figuring that was as good a filter as any I had.

Three weeks in, I realized the actual problem I needed solved wasn't “someone standing at the counter.” It was “someone who could handle a rush alone without me hovering, so I could actually get the next day's prep done in the back.” I'd never once said that out loud, not to myself, not in the job posting, not in the interview. So of course the person I hired had no way of knowing that's what success actually looked like, because I hadn't decided what it looked like either.

The second time I hired, I wrote one sentence before I posted anything: “needs to run the front alone during the 7 to 9 rush by week three.” That single sentence changed everything, who I looked for, what I actually asked in the interview, even how fast I could tell if it was working. Instead of “tell me about yourself,” I asked what they'd do if the line was ten deep and the card reader jammed. Same job title on paper as the first time. Completely different hire underneath it, and this one was still there two years later.

Test the Outcome Before Writing the Advertisement

Here's something to try. Costs nothing. Takes five minutes. Think about the next role you'd hire for, real or hypothetical. Finish this sentence: this person needs to be able to do a specific thing, without me, by a specific point in time. Not a duty. Not a vibe. An outcome, with a deadline attached to it. If you're hiring to fix a specific Tuesday-afternoon problem, name the Tuesday-afternoon problem, out loud, in one sentence. If you can't finish that sentence specifically, that's not a failure on your part, that's exactly the gap the interview process has been quietly failing to catch this whole time. Write the sentence down.

Not “a good fit.” The actual outcome, in your own words, the way you'd say it out loud if someone asked you point-blank what this job is really for.

Name the Target

Print your SBE People Gauge worksheet, or fill it out online, whichever's easier. Today, just write that one sentence down. That's it. Don't write the job posting yet. Don't write the interview questions yet. Just name the actual target first.

What a Strong People System Changes

There are other gauges on this panel, and we'll get to all of them. For today, just find out what your People Gauge is telling you about the role you're about to fill. Once the target is written down instead of felt, hiring stops being a guess you're hoping pays off, and starts being something you can actually evaluate against.

A Practical Starting Sequence

  1. Describe the operational problem the role must solve in one sentence.
  2. Turn that problem into an observable outcome with a reasonable date or proficiency point.
  3. Write interview questions around realistic situations instead of asking candidates to describe flattering traits.
  4. Explain what good performance looks like before the employee must guess under pressure.
  5. Track whether the system supports the person: information, authority, training, tools, feedback, and a clear route for exceptions.

The Mistake That Keeps the Problem in Place

The common mistake is hiring someone who feels like the owner. Similar energy and conversation style can produce immediate comfort, but comfort is not evidence that the person can deliver the required outcome. The opposite mistake is demanding a mythical employee who needs no structure. If a role requires someone exceptional merely to survive normal operations, the system is charging employees for its weaknesses. Design work that a capable, properly trained person can perform consistently. Exceptional people should elevate the business, not spend all their energy holding it together.

Questions Owners Commonly Ask

How specific should a role outcome be?

Specific enough that two reasonable people could observe the same result and agree whether it occurred. “Help with customers” is vague. “Handle the front counter independently during the 7-to-9 rush by the end of week three” creates a target that can shape recruiting, interviewing, training, and feedback.

Does structure drive creative employees away?

Bad bureaucracy does. Useful structure removes avoidable ambiguity while preserving room for judgment. Good employees usually appreciate knowing what they own, what success means, and which decisions they can make without seeking permission.

What if I already hired someone into a vague role?

Reset the conversation without blaming the employee. Explain the business outcome the role must produce, ask what obstacles make that difficult, agree on boundaries and measures, and schedule a review. Clearer expectations can repair many situations that initially look like poor performance.

Take the Next Useful Step

Good people deserve a business that gets smarter from their effort. Their experience should improve the role, strengthen the process, and reduce repeated friction—not become an invisible substitute for design. Define the outcome, make the operating conditions visible, and let capable people contribute without asking them to carry every weakness personally.

Take the People ClarityScan™

Continue exploring the SBE System, visit SBE Resources, or watch the complete SBE ClarityScans playlist.

Scroll to Top