The People Operating System: What Growing Companies Need Beyond HR

Ask a company of 120 people what People systems it has and you will usually get a list: an annual review, a hiring process, an onboarding checklist, a handbook, a set of values on the wall. Each was built at a different time, by a different person, to solve a different problem. Individually most of them are reasonable. Collectively they do not add up to anything.

That gap between a list of processes and a working system is what an operating system describes. It is not a piece of software and it is not a bigger HR department. It is the set of connections that make one component usable by the next.

What "connected" actually means

A concrete example. A manager has to explain why someone was rated "meets expectations" rather than "exceeds", and why the pay increase is 3% rather than 8%. To answer that without improvising, four things must already exist and agree with each other:

1. A role definition that says what this person owns.
2. A level framework that says what is expected at their level, in terms of scope and complexity.
3. A performance framework that assesses against those expectations with evidence.
4. A pay structure where the rating maps to a defined range of outcomes.

Remove any one and the manager is left justifying a judgement rather than explaining a decision. That is why performance conversations feel so much harder in some companies than in others: the difficulty is rarely the manager, it is the missing link upstream.

The eleven components

A useful way to audit a growing organisation is to walk the same eleven components every time. Not because every company needs all of them at full maturity, but because it makes the gaps visible.

• Organisation structure — how work is grouped and where authority sits.
• Roles and decision rights — what each role owns and can decide alone.
• Hiring and onboarding — who enters, and how fast they can contribute.
• Goals and performance — what good looks like and how it is assessed.
• Feedback and development — the short loop, between annual cycles.
• Management routines — where the system is actually operated.
• Career frameworks — what progression means and requires.
• Compensation — how pay decisions are made and explained.
• Culture and communication — the decisions people can predict.
• People policies — the boundaries within which managers decide.
• People data and metrics — where the system is failing.

The People Diagnostic looks at how these components depend on each other. The short version: structure determines roles, roles set expectations, expectations drive performance, performance connects to progression, progression to pay. Managers operate the whole thing, culture shapes how, and data shows you where it is breaking.

Three questions per component

Maturity models tend to produce a score nobody acts on. Three questions, asked in order, are more useful because each one only matters if the previous answer was yes.

Most growing organisations pass the first question comfortably, fail the second in two or three places, and fail the third almost everywhere. The third failure is the expensive one, because it is invisible until a decision has to be defended.

Why HR alone rarely closes the gap

This is not a criticism of People teams. It is a structural observation. Most People functions in growing companies are one or two people carrying a service load: contracts, onboarding, questions, tooling, the annual cycle. That load is real and it is continuous, and it leaves very little room for the design work that connecting components requires.

The other reason is scope. Several of the eleven components are not owned by HR at all. Structure and decision rights are leadership decisions. Management routines belong to managers. People data usually sits between Finance and Operations. Anyone trying to connect the system from inside a single function will run out of authority before they run out of ideas.

The components that fail are rarely the ones a People team controls. They are the ones between functions, where nobody has been asked to own the interface.

Where to start if this is you

Do not start by building the missing components. Start by identifying which one, if it existed, would make the next three easier.

In practice that is almost always roles and decision rights. It is the cheapest component to define, it requires no new tooling, and it is an input to performance, hiring, career levels and management routines. Companies that skip it and start with a performance framework usually rebuild the performance framework within two years, because the expectations it assesses were never defined.

If you want an external read on which components are missing and in what order to build them, that is what the People Diagnostic is for.