How to think about your next hire

This is the first in a four-part series on building a team that actually scales. Not hiring faster. Not hiring cheaper. Hiring better.

---

Most hiring decisions start in the wrong place.

A founder gets busy. Something breaks, slows down, or falls through the cracks. A client complains. A deadline gets missed. The internal response is immediate and logical: we need someone for this. A job description gets written, a brief gets sent, and within a few weeks the business has a new hire doing exactly what the founder needed done three months ago.

Six months later, the business has moved on. The problem that triggered the hire has either resolved itself, changed shape, or spawned three new ones. And the person hired to fix the original problem is now, at best, underutilised, and at worst, actively in the way.

This is the founder's hiring trap: hiring for the problem you have today, and inheriting the constraint that creates tomorrow.

The question most founders skip

Before writing a job description, before briefing a recruiter, before even naming the role, the more useful question is this: what does this business need to be able to do in twelve months that it can't do now?

That question forces a different kind of thinking. It separates the immediate pain point from the actual capability gap. And it almost always produces a different answer to the one a founder would reach by starting with today's problem.

A business under pressure to keep up with customer queries doesn't necessarily need a customer support hire. It might need someone who can build a system that handles volume without constant intervention. Those are different roles, different skills, and different long-term value to the business.

A founder drowning in admin doesn't necessarily need an assistant. They might need an operations manager who can create the structure that makes the admin disappear. Again, a different hire, a different brief, a different outcome.

Getting this distinction right before the process starts is the difference between a hire that creates capacity and one that creates dependency.

Why urgency is the enemy of good hiring

The problem with hiring under pressure is that urgency narrows thinking. When something needs fixing now, the instinct is to find someone who can fix it now. Speed becomes the primary filter. The brief gets written around the immediate need rather than the long-term role. Shortcuts get taken in screening. The first person who looks capable enough gets the job.

According to ManpowerGroup's 2026 Talent Shortage Survey, 72% of UK employers still report difficulty finding skilled talent they need. But the talent shortage is rarely the core problem for the businesses that struggle most with hiring. The core problem is a brief that wasn't specific enough, written under conditions that weren't calm enough, for a role that wasn't thought through carefully enough.

In a market where every hire costs more, a wrong hire is more expensive than it's ever been. The salary, the NI contributions, the onboarding time, the management overhead during underperformance, and then the cost of starting again. Growth Lending's 2026 SME analysis put it directly: businesses in 2026 will be disproportionately punished for execution mistakes, and poor hiring choices sit at the top of that list.

Urgency is understandable. It's rarely a good filter for a decision with a twelve-month cost tail.

The difference between a role and a task

Here's a reframe that's worth sitting with. Most founders, when they're busy and stretched, think in tasks. There's too much to do. Someone needs to help do it. They hire someone to help do it. The business gets busier. There's still too much to do. The cycle repeats.

The businesses that scale well think in roles, not tasks. A role has an owner. An owner has accountability. Accountability means the work gets done without the founder having to think about it. Tasks pile up. Roles clear the decks.

The distinction matters enormously when it comes to a brief. "I need someone to handle our social media" is a task. "I need someone who owns our content and community presence and can build a function that doesn't need me in it" is a role. The second brief attracts better people, produces a better outcome, and creates something the business can build on.

This is true across every function. Finance, operations, customer support, marketing. The businesses that hire well tend to write briefs that describe what someone will own, not just what they'll do. The shift from task to role is often the most valuable thing a founder can do before a hire happens.

Immediate need vs long-term capability: how to tell the difference

Not every hire needs to be strategic. Some roles genuinely are immediate and contained, and the right response is to fill them quickly and move on. The question is knowing which kind of hire you're actually making.

A few questions worth asking before opening a role:

Will this problem still exist in twelve months? If the answer is probably not, a permanent hire is likely the wrong solution. A contractor, a fractional professional, or a short-term flexible arrangement will serve the business better without locking in a fixed cost that outlasts the problem.

Does this role need to grow with the business? Some roles are foundational, they need to absorb complexity as the business scales, and the right hire now will still be the right hire in three years. Others are support functions that a capable person can handle within defined parameters. Knowing which category a role falls into changes who you're looking for.

Am I hiring for my problem or for the business's capability? This is the hardest question, because the honest answer is often "both." But the moment a founder can separate their personal pressure from the business's structural need, the brief becomes considerably clearer and the hire considerably better.

What does this role stop me from having to do? The answer to this question defines the value of the hire. If the answer is a long, specific list, the role has real leverage. If the answer is vague, the brief probably is too.

What this series covers

This is the first of four posts on building a team that scales. The next three go into: the framework for sequencing hires as the business grows, the four variables every hiring decision actually involves, and how to decide whether remote hiring belongs in your team-building strategy.

Each post is designed to be useful on its own. Together, they build a complete picture of what thoughtful team-building looks like for a UK founder in 2026, where costs are higher, employment risk is real, and the margin for a hiring mistake is narrower than it's been for a long time.

If you're already at the point where a hire is imminent and you want to understand what the process looks like when someone else handles the employment side, the Outsourcery hiring guide is worth reading before you brief anyone.

---

FAQ

Why do founders make bad hiring decisions? The most common cause is hiring to solve today's problem rather than tomorrow's capability gap. Urgency narrows thinking, briefs get written around immediate pain points rather than long-term roles, and the result is a hire that solves one problem while creating another. The fix is asking what the business needs to be able to do in twelve months before writing a single line of a job description.

What's the difference between hiring for a role and hiring for a task? A task is something that needs doing. A role is something that needs owning. Hiring for a task fills a gap temporarily. Hiring for a role creates accountability, removes the founder from a function, and builds something the business can grow on top of. The distinction changes what you're looking for, who you attract, and what the hire is worth long-term.

How do you know if a hire should be permanent or flexible? Ask whether the problem will still exist in twelve months. If not, a permanent hire is likely the wrong structure. A fractional or flexible arrangement gives the business the capacity it needs without locking in a fixed cost that outlasts the need.

What should a good hiring brief include? A good brief describes what someone will own, not just what they'll do. It defines what success looks like in the first 90 days, what the role should make redundant for the founder, and how the role is expected to grow. If you can't answer those questions, the brief isn't ready yet.

---

Sources:

• ManpowerGroup, "2026 Talent Shortage Survey"
• Growth Lending, "Building to Last: How UK SMEs Should Approach Funding and Growth in 2026," January 2026
• Startups Magazine, "The Hiring Advantage Startups Are Overlooking in 2026," April 2026
• HR Heads, "Why Is There Still a Talent Shortage in 2026?," April 2026