The Complete Guide to Hiring and Managing Your First Team

Most first hires fail somewhere other than the hire itself. The interview went fine, the person was capable, and it still didn't work — because the role was never defined, the first month was improvised, and nobody said anything specific until month five.

This is the sequence that prevents that. Each stage produces what the next one needs.

The sequence

| Stage | What it produces | Skipped when | |---|---|---| | 1. Define the outcomes | Something to hire against | You're busy and just need help | | 2. Structure the interview | Comparable candidates | You trust your read | | 3. Plan ninety days | A hire who contributes by month three | The offer felt like the finish line | | 4. Run one-on-ones | Problems surfaced while small | The week got full | | 5. Give feedback continuously | Behaviour that actually changes | It felt awkward |

Note that four of the five happen after the decision to hire. The decision itself — whether you can afford it and whether the signals are real — is a separate question, and it comes first.

Define outcomes before you write an ad

Three to five outcomes, not a list of responsibilities.

Day 30 — Running the weekly reconciliation independently, queries raised rather than guessed. Day 60 — Owning month-end close, with me reviewing rather than doing. Day 90 — Close within three working days without my involvement.

Responsibilities describe activity. Outcomes describe success — and a candidate can tell in seconds whether they've done this before.

If the outcomes don't come easily, the role isn't defined. That's a finding worth having before you post, not after someone starts.

Then write the ad to filter as much as to attract. Publish the range — withholding it filters hardest against candidates who have options. List three to five genuine disqualifiers, label everything else a preference, and describe the actual conditions honestly: small team, no existing process, you will build it. That paragraph loses you candidates who were going to leave in four months.

Full structure: how to write a job description that filters.

Interview against the outcomes, not on instinct

Unstructured interviews are well documented as unreliable. They mostly measure how comfortable the conversation was, and comfort correlates with similarity.

Three changes fix most of it:

Same questions, same order, every candidate. Otherwise you're comparing impressions rather than people.

Ask about the past, not the hypothetical. "Tell me about the last difficult client" beats "how would you handle a difficult client." Hypotheticals measure how well someone talks about work.

Score independently before anyone discusses. The first opinion spoken aloud anchors the room. Each interviewer fills in the scorecard alone, with an evidence column — a score without evidence is an impression wearing a number.

And use a paid work sample. It tells you more than any conversation. Pay for anything over an hour at your contractor rate; unpaid multi-hour exercises filter out exactly the candidates who have other options.

Full method: how to interview when you've never hired before.

Plan ninety days before you make the offer

The offer is not the finish line. The next ninety days decide whether this works.

Week one should end with something real shipped — a reconciled account, a published page, three customer emails answered. Nothing builds confidence like having already contributed, and nothing wastes a first week like five days of shadowing.

Have them document as they learn. As you teach each process, they write the SOP. You get documentation you didn't have, they learn actively, and you find out how clearly you actually explain things.

Expect a real ramp — limited output in month one, partial in month two, approaching full by month three. Add the hire to your cash flow forecast at full cost from day one, because payroll is fully loaded whatever the output.

And put the 30, 60 and 90 day conversations in the calendar before day one. The ones scheduled later get postponed, and the ones postponed are the ones where something was wrong.

Full plan: the first 90 days.

Run one-on-ones that aren't status updates

If the meeting is a list of what they worked on, you've built a report you could have read.

It's their meeting. They bring the agenda; status goes in writing beforehand. That frees the conversation for what's blocked, what they're unsure about, and what they think is going wrong that you haven't noticed.

Four questions, most weeks. The two that earn their place:

What's getting in your way? What should I know that I probably don't?

The second explicitly invites bad news, which most people won't volunteer otherwise.

Then remove one blocker every meeting. That single habit turns the meeting from something tolerated into something prepared for.

And never cancel it. Cancelling teaches people their meeting is the first thing to go.

Full agenda: how to run a one-on-one.

Give feedback within days

Two useless kinds: too vague to act on, and saved up for a review.

Three parts: observation, impact, request. Miss the observation and it's vague; miss the impact and it sounds arbitrary; miss the request and nothing changes.

Separate observation from interpretation. "The last two drafts came in without the data section" can be discussed. "You don't seem invested" can only be defended against — and you may be wrong about the cause. Ask for it rather than assuming.

Drop the sandwich. It either cushions the message until it's missed or teaches people that praise precedes bad news. Give praise on its own, and make it as specific as the criticism.

If the same feedback lands three times without changing anything, the delivery isn't the problem — it's capability, expectations, or fit, and each needs a different conversation.

Full structure: how to give feedback that changes something.

Competing when you can't pay top of market

Small businesses rarely win on salary, and trying to is a losing position. What they can compete on is real, and most owners undersell it because it feels like an excuse.

Be honest about the number, then be specific about everything else. The things that genuinely move candidates who have options:

• Scope. In a five-person business someone owns whole processes rather than a slice of one. For the right person that is the offer, and it is unavailable at a larger employer.
• Proximity to the outcome. They see the effect of their work on the actual business, weekly, rather than through three layers of reporting.
• Flexibility that's real. Not a policy on a careers page — actual control over hours and location, which a small team can give and a large one usually can't.
• Speed. A suggestion made on Tuesday can be in place by Friday. That is genuinely rare and worth naming.

What doesn't work: equity offered vaguely, "we're like a family," or promises about future compensation that depend on a good year. Candidates have heard all three and discount them appropriately.

Where you should not compromise is the range being honest. Advertising a number you intend to negotiate down poisons the relationship before day one, and the person finds out.

One structural option worth considering before a full-time hire: part-time or fractional. It lets you access more senior capability than the salary budget would otherwise reach, and it is reversible in a way a full-time hire is not.

What this doesn't cover

Deliberately: anything governed by employment law. Contracts, worker classification, termination, statutory entitlements and discrimination law vary enormously by jurisdiction, and getting them wrong is expensive in a way that no article can protect you from.

Where a decision touches any of those, take advice from someone qualified in your jurisdiction before acting. That's not a disclaimer for its own sake — classification and termination in particular are where small businesses most reliably create expensive problems by improvising.

The mistakes, collected

1. Hiring before defining outcomes. Both of you guess for a month.
2. Unstructured interviews. You've collected impressions, not comparisons.
3. Unpaid multi-hour work samples. Filters out the strongest candidates.
4. No ninety-day plan. The offer treated as the finish line.
5. A week of shadowing. Passive, and it teaches nothing.
6. Cancelling the one-on-one when busy. Teaches people it's optional.
7. Saving feedback for a review. Too late to act on, too much to absorb.

Where to start this week

Write the three monthly outcomes for the role — even if the hire is months away. It takes twenty minutes, and if they don't come easily you've learned something more valuable than any interview would have told you.