How Small Businesses Make Better Hiring Decisions

When a candidate interviews well, I try to separate presentation from proof by defining success before we ever start comparing people. A practice that consistently improves the decision is creating a simple “success profile” for the role: the top three outcomes the person must deliver in the first three to six months, plus the behaviors needed to get there. Then I run a structured behavioral interview where every finalist answers the same core questions tied to those outcomes. I ask for specific examples and listen for how they think, how they prioritize, and how they handle obstacles, not just what they accomplished. The signal I trust most is whether their process matches the day-to-day realities of the role, because that is where performance shows up after the first week. Finally, I have interviewers document what evidence they heard for each criterion, which reduces the tendency to hire the most polished communicator. This approach creates a clearer, fairer comparison and surfaces the candidates who are likely to execute when the work gets messy.

Small-business success is often visible in the gap between intention and follow-through. Interviews reward intention because candidates can describe what they would do. The better predictor is whether they close a loop when nobody is reminding them, especially after the conversation ends.

I ask candidates to send a follow-up within two days, not a thank-you note, but three observations about the role and one question they would investigate first. There is no penalty for a format. The signal is ownership. Strong people convert exposure to a business into momentum, while weaker candidates wait for instructions or produce praise. This practice exposes judgment about tone, speed, and what deserves attention.

We pay close attention to what happens after an interview. When a next step is agreed upon, we note whether the candidate confirms the details, keeps the commitment, and communicates any changes in advance. This is not about expecting perfection. It is a simple way to observe professional follow-through in everyday situations.

Polished candidates can talk about accountability, but reliable candidates show it through their actions. One applicant needed to reschedule a task because of an unexpected issue. They offered alternatives, explained the impact, and finished ahead of the revised deadline. That interaction revealed more than another round of questions, as we value people who keep commitments, communicate clearly, and respect colleagues' time.

A polished interview mostly shows that someone has practiced interviewing. In a small business, where everyone wears several hats and nobody has time to hand-hold, I look for signals that are harder to rehearse.

The first is the questions the candidate asks. At the end of an interview, most people ask about benefits or the next steps. The people who thrive in a small team ask about the work: what's broken right now, what a normal week looks like, what the last person in the role struggled with. That's how they'll behave once they join, too. At Enhancv, we expect new people to question things and make suggestions from the start, so curiosity in the interview is one of the best predictors I know.

The second is how they talk about past work. We see thousands of resumes, and the difference shows up there too. Some people describe their job: "responsible for customer support". Others describe what changed because they were there: "cut response times by rewriting our help articles." In an interview, I keep asking "what happened next?" until I hear which kind of person I'm talking to. People who think in outcomes keep going. People who think in duties run out of answers.

If you can, also give candidates a small piece of real work, something that takes an hour, not a weekend. You learn more from how someone handles a messy, real problem than from any answer about how they would handle one.

I decide by looking for how a candidate handles uncertainty before acting. In a small business, employees often make decisions that directly affect colleagues and clients, so confident answers are less useful than well-calibrated ones. I want to hear the candidate identify what they know, what they still need to learn, and which decisions fall within their role. A strong candidate asks focused questions, names reasonable assumptions, and knows when to involve a supervisor rather than guessing. They communicate appropriately without broadly sharing confidential information. In behavioral health, that distinction is especially important because initiative must stay within a person's training, scope, and established procedures. This signal can help separate genuine judgment from interview fluency. The strongest response is not instant certainty, but a careful path to a responsible decision.

One interview practice I've found useful is giving every finalist the same intentionally incomplete, simulated and nonconfidential role-specific scenario. I ask them not to solve it immediately, but to tell me what information is missing, where they would obtain it, what they could decide independently, and what would require escalation. I score those elements against job-related criteria set in advance. This keeps the exercise structured while showing how candidates think before they act. It also gives quieter candidates a fair opportunity to demonstrate sound judgment without rewarding presentation style alone.

I look for integrity under pressure because small-business employees often have visible influence on customers, coworkers and the company's reputation. A polished candidate can describe the right values. The better signal is whether their account of a difficult decision includes a meaningful tradeoff rather than an easy answer. I listen for three things: whether they recognized the ethical issue without being prompted, whether they raised it through the appropriate channel, and whether they accepted accountability for their own part. I also ask what they would do differently now. Strong answers are specific about the decision and its consequences without disclosing confidential information or blaming other people. They show that the candidate can use judgment when the convenient choice conflicts with the responsible one. That matters especially in behavioral health, where trust, boundaries and sound decisions are central to the work.

The interview practice that has helped me is asking candidates for a nonconfidential example of a difficult ethical or judgment call in a previous position, with an explicit instruction not to share patient, client, employee or other identifying information. I follow with the same neutral questions for each candidate: What options did you consider? Who needed to be involved? What action did you take? What happened afterward? I'm not looking for a dramatic story or a perfect outcome. I'm looking for a clear decision process, respect for established procedures and evidence that the person can be candid about uncertainty. That gives me more useful information than broad claims about integrity.

The thing I started doing was handing candidates a small piece of real work and paying them for it. Not a case study or a hypothetical. An actual task from my queue that week, with instructions I deliberately left incomplete.

What I watch is what happens in the gap. Some people sit on it and deliver something half-finished at the deadline. Some write back within a day with two or three sharp questions about the part that was missing, make a call on the rest, and tell me which assumption they made. In a company my size, nobody is going to hand that second group a complete brief ever again, and they work out.

The polished interview answer tells me they can describe competence. The paid task tells me how they behave when the person who assigned the work is unavailable, which is most of the time in a business this size.

I also pay attention to how they handle feedback on that task. I send one round of blunt notes. If the revision comes back addressing the notes and nothing else, that is a different worker than the one who quietly fixes three other things they noticed along the way.

Two days of real work has sorted more candidates for me than any hour of conversation.

I use a reversal question near the end of the conversation. I ask the candidate what they think would be hardest about succeeding in this role during the first 90 days. It moves the discussion away from rehearsed strengths and toward their ability to observe a real operating environment. Strong candidates do not pretend every challenge has an easy answer. They identify trade-offs and explain how they would learn quickly.

This also shows whether someone can enter a small team with humility. The most promising candidates are curious about priorities, decision-making habits, and the standards people use when no one is watching. Their questions show they are evaluating how to contribute, not simply how to impress. That distinction has repeatedly led to better hiring choices.

In a small business, the person you hire usually has to own more than their job title suggests, so a polished interview only tells me so much. What I care about is whether they can take something from start to finish without waiting to be told every step. Someone can interview well and still struggle once the work gets messy and nobody is there to hand them the next task.

The practice that helps me most is giving candidates a small, realistic piece of the actual work. For a sales or support role, that might mean walking through how they would respond to a customer with a tight deadline and an unclear request. I am less interested in a perfect answer than in whether they ask good questions, think about the customer's side, and explain a clear next step. That shows me how they work far better than talking about their strengths.

I also pay attention to the small signals around the interview, like how quickly they follow up, whether they did any homework on what we make, and how they communicate in writing. In a small team, those habits show up every day with customers.

If someone is coming from a big organization and moving to a small business, that can be a culture shock. In a smaller organization, you might have to wear a lot of hats, figure things out on your own, and work with much less structure and support. So one thing I'd look at is whether they've worked in a smaller organization before, because at least they have an idea of what they're getting into.

I'd also ask questions about how they handle situations where there's no one to guide them, or when they need to take on something outside their job description. Are they comfortable figuring things out on their own? Can they take initiative when there's no clear process in place? But I also think it's a two-way thing. The person hiring needs to be honest about what working in a small business actually looks like. You don't want someone joining with completely different expectations and then realizing this isn't what they signed up for. So it's not just about whether they're capable of doing the job. It's also about whether they understand the environment they're entering and whether it's right for them.

Running a lawn care company for over 30 years means I've hired people who interviewed great and quit by week three when the July heat hit. The interview room tells you almost nothing about how someone handles a full route day when equipment breaks down and a customer is calling.

The best signal I've found is giving candidates a real scenario before they ever start: I describe an actual service situation, like a customer in Cuyahoga Falls complaining their lawn still has weeds after three treatments, and ask them to walk me through exactly what they'd do next. I'm not looking for the right answer. I'm watching whether they ask clarifying questions or just jump to conclusions.

The candidates who slow down, ask about soil conditions or recent rainfall, and think out loud about a customized fix are the ones who last. The ones who immediately promise the customer a free re-treatment without understanding the problem are usually the ones who create more issues than they solve in the field.

Small business doesn't have the cushion to carry someone through a learning curve while they're facing customers directly. One bad service call can cost you a neighborhood's worth of referrals, so I'd rather spend an extra hour stress-testing how someone thinks than regret a fast hire two months later.

A polished interview mostly tells you who practices interviewing. To see how someone works day to day, I give them a small paid task from the actual job. For a marketing hire that might be a rough outline for a local landing page, or a reply to a messy lead inquiry. It takes an hour or two, and I pay for the time.

Then I watch the small stuff. Do they ask a clarifying question before they start, or guess? Do they hit the deadline they set themselves? When I send back a note, do they fix what I flagged or defend it? Those habits are the job in a small business, because nobody is standing over you.

After that I do a short call where they walk me through their choices and what they'd change with more time. People who really did the work can explain it in plain words. People who got lots of help or rushed it go vague fast.

I also pay attention to how they treat the instructions. Someone who follows a simple brief exactly and flags the one thing that looked off is usually someone I can hand work to and stop thinking about. In a small team that matters more than a great resume, since one slow hire costs everyone else their week.

An interview only shows you so much. I want to see how someone approaches the everyday work, especially when things don't go as planned. That matters in a small company, where a lot of the job involves handling the less glamorous tasks well.

Having helped lead two CEO searches for a credit union board and built a team of about 22 at Pledge It, I look for two things: coachability and ownership. Coachability shows when you challenge someone's answer and see how they respond. Strong candidates stay curious and consider other perspectives. Ownership comes through when you ask about a failure. Do they explain what they did next, or focus on who was to blame?

One approach I recommend is a short, paid working session based on a real task, such as rewriting a campaign email or organizing a messy sponsor list. Follow it with a conversation about their decisions. You get to see how they ask questions, handle uncertainty, and respond to feedback.

At Pledge It, we want people to feel safe making mistakes and learning from them. I look for people who can acknowledge a mistake, take responsibility, and adjust quickly. Those are often the people others learn to trust with bigger responsibilities.

In a smaller business, you feel the difference between a good hire and a bad one very quickly. There are fewer layers to absorb the impact, and someone's ability to work independently, exercise judgement and adapt when things don't go to plan can matter just as much as their technical expertise. In executive recruiting, I've learned that a polished interview tells you how someone presents themselves under favourable conditions. It tells you rather less about how they'll behave when those conditions disappear.

One practice I've found useful is moving away from hypothetical questions and asking candidates to walk me through a real decision they've made. What information did they have? What did they get wrong? Who did they involve, and what happened when their original approach didn't work? I'm interested in the reasoning, not just the outcome. Most senior candidates can tell a convincing story about a success. It's more revealing to understand how they think when the answer isn't obvious.

The signal I pay particular attention to is how candid someone can be about their own contribution to a difficult situation. That doesn't mean looking for a perfect answer or expecting someone to confess to some enormous failure. It means seeing whether they can distinguish what they controlled from what they didn't, recognise where their judgement could have been better, and explain what they changed as a result. In a small business, where people have to take ownership without always having a playbook to follow, that kind of self-awareness is often more useful than another impressive credential.

I judge a candidate by how they finish a piece of work, not by how well they talk about it. A polished interview can't show whether someone closes the loop or leaves loose ends, so I'd rather watch them handle real work than hear them describe it.

At QuickIntell, which builds AI agents for healthcare revenue-cycle work, our interviews include a work sample: candidates review something an AI produced and tell us what's wrong and what should happen next. Not long ago, the same exercise would have had them do the task from scratch; now the job is judging work that is already done.

Any small business can borrow the idea. Picture a sample like this: an AI-drafted reply to a customer that promises a refund, with nothing showing that anyone approved it. A weak answer says someone ought to look at it. A stronger one, in my view, says the promise has no approval behind it, the reply should be held, and whoever owns refunds should decide before it goes out. The first spots a problem. The second gives it to someone who can act.

Years in a role aren't a safe stand-in either. Our most experienced staff are sometimes the ones who struggle most, while the people who treat checking the work as the work itself thrive. That's why I'd caution against using years of experience as a proxy in an interview. I think the gap costs more in a small team, where there is often no one downstream to catch a half-finished handoff. It's the same bar we hold our own exceptions to: each one needs a stated reason and an owner by name.

My advice: take a recent piece of real work, ideally one with a flaw, remove anything confidential, and ask the candidate to critique it and name the next step. Then listen to the last sentence of their answer, not the first.

I run a trial law firm, which means I hire people who have to perform under pressure with real stakes -- not just look good in a conference room. That experience has taught me more about hiring signals than any HR playbook.

The most useful thing I ever started doing was assigning a small, real task before the offer -- a short memo, a research question, something that mirrors actual work. How someone structures their thinking when no one is coaching them tells you everything a polished answer never will.

I also watch how candidates handle being wrong. In depositions, I've seen witnesses collapse the moment they're challenged on a detail. I look for the same thing in hiring -- push back gently on something they said and see if they defend it thoughtfully or fold immediately. That reaction is hard to rehearse.

Small businesses can't absorb a bad hire the way a large firm can. The clearest signal I've found is whether someone asks questions that show they've thought about the actual problems your business faces -- not just questions designed to make them look curious.

Having served in the Army and later as an executive at two Inc. Magazine fastest-growing companies before founding Honorable Marketing, I've seen that rehearsed interview answers rarely predict day-to-day discipline.

To see how someone actually operates, I give candidates a real-world scenario--like diagnosing why a local firm's search presence is falling behind--and ask them to walk me through their exact troubleshooting process live.

I pay close attention to how they navigate uncertainty and whether they acknowledge what they don't know. In a small business, a candidate who chooses honest problem-solving over trying to sound flawless will always succeed when real challenges hit.

I run GHOSTUD, where a small-business hire may touch product pages, dealer questions, install instructions, and contractor feedback in the same week. A polished interview matters less than whether they can turn messy product reality into a clear next action.

My favorite practice is a short, role-specific work sample. For a marketing or customer role, I'll hand them our GS1/GS2 info -- GS1 up to 250 lb, GS2 up to 1,000 lb, no-stud install, recycled plastic -- and ask them to write a dealer counter pitch or rewrite a confusing FAQ answer.

The signal I watch for is not perfect wording; it's whether they notice constraints. Do they catch that GHOSTUD cannot be installed into a stud, that GS1 and GS2 use different hole saw sizes, and that heavy-load claims need careful, accurate language?

In a small business, I hire the person who asks practical questions, documents their assumptions, and leaves me with something usable. The best candidates reduce drag the same day; the risky ones need a perfect system before they can move.

As COO at DFW Movers & Erectors, I evaluate operational candidates based on real-world adaptability and a willingness to understand the business from the ground up. Polished interview answers rarely reveal whether someone will actually roll up their sleeves when daily challenges hit the floor.

My favorite practice is asking candidates to explain how they handle tasks far outside their core job description. For instance, our top estimator Michael Tucker succeeded because he built foundational credibility by starting as an apprentice rigger on complex moves before transitioning into sales.

I also look for an innate drive toward problem-solving and mentoring others, much like our veteran fabricator Santiago Nunez, who consistently steps up to build custom rigging solutions and train younger crew members. Candidates who show genuine curiosity about hands-on execution and safety accountability always outperform those focused solely on high-level talk.

I run a practice where the team handles everything from remote-anchorage full-arch cases to oncology clearances with Texas Oncology and MD Anderson. When interviewing, I ask candidates to walk through how they would explain options to a patient who was told elsewhere they have no bone for implants.

That single exchange shows whether someone will treat the whole person without judgment, the way we do every day for patients who drive in from the DFW area or farther.

I also watch how they respond when I describe an in-house lab workflow that turns a scan into healing teeth the next morning. People who immediately connect that speed to the patient's daily life rather than the technology itself tend to fit the small-team reality of keeping every step judgment-free and coordinated.

As a co-owner at a family-owned roofing company in DFW, I'm hiring for people who can protect the standard when nobody is watching. A smooth interview matters less to me than how they think through a real homeowner situation.

One practice I like is a field-style walkthrough: I'll show them a roof or gutter scenario and ask them to explain the next steps to a customer in plain English. I'm watching for curiosity, honesty, safety awareness, and whether they notice details without trying to bluff.

A good example is cedar roofing in Texas. If a candidate only tries to "sell the upgrade," that's a red flag; I want someone who will tell the homeowner cedar takes real maintenance and suggest composite shake if that better fits their life.

The best signal is how they handle tradeoffs. In a small business, the right hire is usually the person who can be clear, calm, and honest when the answer is not the most profitable one.

Ran Mackey Services for over 30 years, so I've hired people who looked great on paper and fell apart the moment a real customer opened the door frustrated about a hot upstairs bedroom.

The signal I trust most now is how a candidate describes their last difficult customer interaction -- not a technical problem, a people problem. Anyone can memorize a checklist. What I need to know is whether they'll sit down with a homeowner, actually listen about which rooms feel stuffy, and explain options in plain language without making the customer feel stupid.

So I stopped asking hypotheticals and started asking candidates to walk me through a real conversation they had where the customer pushed back. The ones who talk about listening first before defending their diagnosis are almost always the ones who last. The ones who jump straight to their technical answer -- even if it's correct -- tend to struggle with the relationship side that keeps customers coming back.

Small business lives and dies on repeat trust, not one-time fixes. A polished interview tells you someone prepared for an interview. A story about how they handled a frustrated person tells you how they'll represent your name on someone's doorstep.

I worked for Labatt Breweries as campus activation before I built anything. That position was primarily recruiting and handling student ambassadors. Turnover is high and there's lots of enthusiasm. However, half of those who talk the talk don't walk the walk.

I became very adept at spotting the difference. Not from interviews, but from observing who appeared, who did the little things and who did what they said they would without having to be reminded.

To this day, it's how I function. If someone does a good interview, I don't trust the interview. I check to see if they've done what they said they would, somewhere else, for long enough that it wasn't an accident. A position they had for three years. A project that they completed. A person who can share with me a story of a difficult situation they have dealt with.

The most reliable signal is incredibly straightforward. Have they been successful in the past in doing what they say? If yes, the interview is pretty much irrelevant. If not, then a great interview is simply a good performance.

Don't go around your own process because you need someone fast. When an owner brings in a person they found themselves, problems very often follow. Not because the person is bad: their onboarding gets squashed, and the owner's expectations and the team's expectations don't match. The signal I trust is the recruiting system itself. It checks hard skills and soft skills, and also how complementary this person will be for the team. Let the team be part of the filter, because from the top we often don't see what the team down below needs. With that process in place, we hired A-players in about a month.

In a small business, the interview is the part candidates prepare for most, so it tells you the least about an ordinary working day. What has helped us at Flowmingo is giving people a small piece of the real job before we meet them. For a growth role, that meant a short recorded answer to a situation our team had actually dealt with that month, with enough background that they could respond in a few minutes. We weren't looking for a correct answer. Mostly we listened for small things. Did they ask what the goal was? Did they say what they'd look at before touching anything? Could they explain it in plain words? Honestly, that's most of the job on a normal day.

The other habit: check the claim the role really depends on with your own eyes, not from a summary. While we were sourcing for that same role, an automated research note put a candidate's audience at around 6,800 followers. When I opened the profile, it was over 42,000, which changed whether the person was a fit at all. It takes a few minutes per finalist, and for a small team a wrong hire costs far more than those minutes.