There is a point in most growing businesses where the way things have always been done starts to become harder to sustain.

When a team is very small, a lot can work informally. People know each other well, managers are close to the work, decisions are made quickly and information travels easily. You don't necessarily need a process for everything because the business itself provides the context.

As the team grows, that starts to change.

The same informal approach that once felt flexible can begin to feel inconsistent. One manager gives regular feedback while another only speaks to someone when something has gone wrong. One employee has a clear idea of what they need to do to progress, while another is left trying to work it out for themselves. New joiners have very different onboarding experiences depending on who happens to be available that week.

None of these issues necessarily mean that a business needs a large HR function or a stack of new policies.

But they are usually signs that it needs a little more structure.

Start with the problem, not the process

I think this is where smaller businesses can sometimes get HR wrong.

There is a temptation to look at what larger companies have in place and assume that growth means gradually recreating all of it: competency frameworks, detailed career architecture, multiple performance cycles, long policy documents, complicated approval processes.

That may eventually be appropriate. Often, it isn't yet.

A better question is: where is the lack of clarity currently creating a problem?

If employees do not understand how progression decisions are made, then you may need clearer expectations around levels and promotion.

If managers are avoiding performance conversations until issues become serious, then you probably need a simple performance process and better manager support.

If people are joining the company and spending their first two weeks trying to work out who does what, then onboarding needs attention.

The process should come after the problem has been identified, not before.

Consistency matters before complexity does

For me, one of the biggest reasons to introduce HR structure is not control. It is consistency.

Employees do not necessarily expect every decision to go their way, but they do expect to understand how decisions are made.

If two people doing similar roles are treated completely differently because they happen to have different managers, that eventually becomes a problem. The same is true for salary decisions, promotions, flexible working, performance expectations or development opportunities.

This doesn't mean every situation needs to be treated identically. People and circumstances are different.

It does mean there should be enough shared structure that decisions aren't entirely dependent on who is making them.

In a smaller business, you often don’t need a formal system. You need people to be clear on what good looks like, managers to work from the same basic principles, and key decisions to be made consistently.

It doesn't always need another policy.

Build for the company you have

Another mistake is designing HR for the company you imagine having in three years rather than the company you actually have today.

A 20-person company does not need the same performance system as a 2,000-person company.

It may need a quarterly conversation between employee and manager, a few clearly defined goals and a simple way to capture development priorities. That can be enough.

The same applies to career progression. You might not need an eight-level career framework. But employees should still know what being more senior actually means.

You might not need a sophisticated compensation model. But there should be enough logic behind salary decisions that they can be explained and defended.

The structure should match the maturity and complexity of the business.

So what should be structured first?

There isn't a universal order, but I would usually look first at the areas where inconsistency has the biggest impact on employees or managers:

• Joining the business: clear roles, expectations and a consistent onboarding experience.

• Managing performance: regular feedback, clear goals and a defined way of dealing with problems early.

• Progression and pay: enough clarity around levels, promotions and salary decisions to make them feel considered rather than arbitrary.

• Core people policies: the things employees and managers genuinely need to know, written clearly and proportionately.

• Manager capability: because even a very good HR process will fail if managers don't know how to use it.

Once those foundations are working, you can add more sophistication where there is a genuine need.

The test I would use

Before introducing a new HR process, I think it is worth asking three questions.

What problem are we trying to solve?

Will this make something clearer or easier for employees or managers?

Is this the simplest version that would actually work?

If the answer to the first two isn't clear, the business probably doesn't need the process yet.

And if the answer to the third is no, it may need a simpler one.

Good HR structure shouldn't make a small business feel more corporate.

It should make it easier to grow without losing clarity, fairness and common sense.