HR Department Structure by Growth Stage — Add Capability, Not Just Administrators

Most growing companies build their HR function the same way: by adding whatever administrative need is loudest at the time. First someone to handle payroll and contracts, then a recruiter, then someone for government compliance, then an HR system and a person to run it. Each addition is reasonable. By three hundred people the company has a capable administrative back office and nobody working on the questions that decide whether it scales well: structure, roles, capability, leadership and culture. The order in which HR grows matters more than its size, and the rule we suggest is simple. At each stage, add the capability that addresses the biggest people risk of that stage, not the loudest transaction.

This is also the question behind a remark we make about our own platform, that it is the wrong purchase for an HR team whose remit stops at compliance and payroll, a point we explain in who Green Apple is built for. This piece is the constructive side of that remark: what an HR function that goes beyond administration looks like, and when each part should arrive.

"We built a very good back office"

The chief executive of a services company in Riyadh asked us to look at their HR function when the company reached about three hundred and fifty people. It had grown the classic way. A generalist had been hired at forty people, then a recruiter, then a government-relations officer to handle Saudization targets, GOSI registrations and wage-protection submissions, then payroll moved in-house with two specialists, then an HR system administrator.

The team was good at everything it had been hired for. Contracts were right, payroll was on time, the Saudization numbers were managed carefully. But the company's actual problems were elsewhere. Three restructurings in two years had left roles overlapping, a wave of first-time managers had been promoted with no support, and the leadership team could not say which capabilities the next year's strategy required. Nobody in HR had been hired to work on any of it. The CEO summarised it kindly: "We built a very good back office. We never built the part that works on the organization."

The HR Build Sequence

We use a four-stage sequence with growing companies. The headcount ranges are rough guides rather than rules; the stage is defined by the risk, and companies move through them at different sizes depending on complexity, number of entities and pace of growth.

The foundation stage is about not getting the basics wrong, and in Saudi Arabia and the wider Gulf those basics include a significant compliance load, from Saudization or nationalisation targets to social insurance and wage-protection systems. Much of this can be outsourced early. The hiring-engine stage is where most companies feel HR's value first, because hiring becomes continuous and the first managers are appointed. The organization-building stage is the one most companies skip, and it is where our story took place.

The role most companies hire too late

The third stage's key addition is a person or small team whose job is the organization itself rather than the employment relationship: structure and roles, capability planning, performance and leadership development, and culture. The title varies, from organizational development lead to head of talent. What matters is that it is a design role, not a transaction role, and that it reports close enough to the leadership team to work on the company's real decisions. Our introduction to what organization development is describes that work in more detail.

Here's the contrarian part

Hire the capability role earlier than feels natural, and certainly before the second recruiter. The case for another recruiter is always easy to make, because the open roles are visible and the cost of an empty seat is obvious. The case for an organizational development role is harder, because the problems it solves are diffuse: overlapping roles, managers without support, a strategy the structure cannot carry. Those problems are also far more expensive, and they compound. A company that adds the capability role at around one hundred and fifty people usually avoids at least one restructuring that it would otherwise have needed at three hundred.

The second point concerns the business partner model. Many companies adopt it as soon as they have read about it, relabelling HR generalists as business partners and attaching them to leaders. Without real expertise behind them, the partners become order-takers who pass requests to an administrative team, and the leaders conclude that HR partnership is a new name for the same service. The model works only when the centres of expertise exist, which is why it belongs to the scale stage rather than the start.

Why it works

Larry Greiner's 1972 article on how organizations grow described a sequence of phases, each ending in a predictable crisis: a crisis of leadership when the founders can no longer run everything personally, then of autonomy, of control and of red tape. His central point was that each phase's solution creates the next phase's problem, which is why the right HR structure changes as a company grows rather than simply expanding. The HR Build Sequence maps the capabilities HR should add onto those crises.

Dave Ulrich's work, beginning with Human Resource Champions in the late 1990s, gave HR the vocabulary of strategic partner, change agent, administrative expert and employee champion, and later popularised the three-part structure of business partners, centres of expertise and shared services. Ulrich has repeatedly stressed that the structure was never the point, and that what HR delivers to the business matters more than how HR is organized. The common failure of adopting the structure without the capability is exactly the gap he warned about.

In our own work, the pattern is consistent with both. The companies whose HR functions grow well treat HR as part of the company's operating system, a view we set out in people strategy is a business model. The ones that struggle treat it as an overhead to be kept as lean as possible, and then discover that the leanness was in the part they most needed.

A practical checklist

• Name your current stage by its biggest people risk, not by headcount.
• List what HR currently does and mark each activity as foundation, hiring, organization building or scale.
• Outsource the foundation work that can be outsourced, including much of payroll and routine compliance, so internal roles can move up the sequence.
• Add the capability role at the organization-building stage, reporting close to the leadership team.
• Support first-time managers before adding more recruiters, since poorly supported managers undo good hiring.
• Delay the full business partner model until centres of expertise exist to back it.
• Review the HR structure whenever the company changes stage, for example after crossing a size threshold, adding an entity or changing strategy, as described in the real challenges of scaling a startup.

Ask yourself

• Which of our HR roles work on the organization itself, and which on the employment relationship?
• What is the biggest people risk we face in the next eighteen months, and who in HR is working on it?
• If we added one HR role tomorrow, would it be the loudest need or the biggest risk?
• Do our managers get more support from HR than our candidates do?
• If we called our HR generalists business partners, would anything change for the leaders they support?

The takeaway

HR should grow by stage, not by accumulation. At each stage, add the capability that answers that stage's biggest people risk: reliable basics first, then a hiring engine and manager support, then an organizational development capability, and only at scale the full business partner model. Most companies hire the capability role too late, which is how a very good back office ends up supporting an organization nobody is designing, and why a flat structure that outgrew its founders is so often HR's first real design problem.