Why we built the People Operating System, and why it belongs alongside EOS rather than after it

If you are considering EOS, or you are three months into it, you have probably had the moment where it clicks. Someone draws the accountability chart, or walks you through the Vision/Traction Organiser, and you think: this is the structure I have been trying to build in my head for four years.

That reaction is warranted. EOS is a very good business operating system. It gives a founder-led business a rhythm, a scorecard, a way to fight about the right things on a Tuesday morning instead of at 11pm on a Sunday. We work with EOS businesses all the time and I am a genuine fan.

I want to talk about the part that is harder, and it is the part almost every business underestimates in the first two quarters.

EOS asks you to make a series of high-stakes people decisions very early. Who sits in each seat on the accountability chart. Whether each person gets it, wants it, and has the capacity to do it. Whether you need an Integrator, and if so, who. Whether the leadership team you have is the leadership team the plan requires.

Those are the right questions. But EOS is not designed to give you the data to answer them, and most businesses arrive at that moment with nothing but skills, tenure and gut feel to work with.

That is the gap. It is why we built the People Operating System.

What happens when the seats get filled with who is available

We were brought into a Brisbane engineering firm partway through their EOS implementation. They had done the accountability chart properly, which is not always the case. Real thinking about the seats the business needed, not the ones it happened to have.

Then names went into the boxes, and the names were chosen the way names almost always get chosen: who is here, who has roughly the right skills, who is willing.

It took a few months for the cracks to show. One seat needed someone who would get out and build relationships quickly, and the person in it needed a lot of certainty before making a move. Another required a level of diligence and follow-through that the incumbent found genuinely draining. A third needed someone who would start things without being asked.

None of these were performance problems in the ordinary sense. None were values problems. They were fit problems, and specifically behavioural fit problems, which are almost impossible to see in advance if you are only looking at capability and willingness.

There was turnover. Good people left seats they were never built for, which is a bad outcome for them and an expensive one for the business. We came in to redesign those roles alongside the EOS work: profiling each seat behaviourally and cognitively, then recruiting and reshaping against the profile.

It worked. It would have been a great deal cheaper eighteen months earlier.

What happens when you do it the other way around

The counterexample is one of my favourite pieces of work.

The CEO was, and I say this with affection, a textbook Visionary. Very open to risk, very fast, comfortable making decisions on a fraction of the information most people would want. The business had about forty staff, was national across Australia, and he was seriously looking at going international.

He knew he needed an Integrator. What made him unusual was that he also knew he could not assess one on instinct, because his instincts were tuned for people exactly like himself.

So we built the profile of the role before we went looking for anyone. Behaviourally, because the working relationship with him would make or break the appointment. Cognitively, because the business was complex and the job was going to be genuinely demanding to hold in one head, and we wanted to be honest about that rather than hopeful.

Then we recruited against that profile.

The pairing held. He went on to sell the business, and he now sends other founders our way more or less unprompted.

The difference between these two stories is not effort, intelligence or commitment. Both businesses had all three. The difference is that one of them had data about people before the decisions were made, and the other had it afterwards.

The five elements

The People Operating System is our answer to that. Five connected elements, because people problems almost never sit in only one of them.

Design. Who you are and how you are built. Your structure, your seats, what each one actually requires. This is where it meets the accountability chart most directly.

Attract. Getting the right people in. Predictable hiring against a defined profile rather than against a good interview.

Inspire. Keeping people and building high-performing teams. What actually drives each person, which is rarely what drives you.

Grow. Developing your people and your managers for what comes next. This is where our Leadership Odyssey program sits.

Measure. Knowing whether any of it is working, in numbers you could take to a board.

I will say plainly that the recruitment piece is the one people come for and the smallest part of the value. Right person, right seat is a hiring outcome. The bigger shift is systemic: leaders who understand how their people are wired, managers who can adapt rather than managing everyone the way they themselves like to be managed, and a business that stops relearning the same lessons every time someone leaves.

Why parallel, not sequential

The most common thing I hear is "let us get EOS bedded down first, then we will look at the people side."

I understand the instinct, and I think it is backwards, for one simple reason. The people decisions in EOS happen early. The accountability chart gets populated in the first quarter. The People Analyzer conversation happens not long after. The Integrator question surfaces almost immediately for a founder-led business.

By the time EOS is bedded down, those decisions are made, the seats are filled and the cost of changing them has gone up considerably. You are not adding people data to a fresh decision any more. You are unwinding a decision, in front of the person it affects.

Running them in parallel also means the people work borrows the EOS discipline. Quarterly cadence, clear accountability, metrics that get looked at. People strategy fails in most businesses because it has no rhythm. In an EOS business, the rhythm already exists.

Where to start

Before we recommend anything to anyone, we run the People Operating System Diagnostic. It is a three-week process: an intake questionnaire, a session with the CEO, a session with whoever owns people in your business, Predictive Index profiling for the leadership team, and a ninety-minute findings and roadmap session with the group.

What you get out of it is a score across the five elements, behavioural profiles for your leadership team, and a prioritised roadmap. What you get out of it that matters more is an honest picture of whether the people you have are the people your plan needs, before the plan asks them to prove it.

It suits businesses where people decisions carry real consequences, which in practice means somewhere north of about thirty people. If you are smaller than that, tell me anyway and we will point you somewhere more sensible.

You can read the detail and book it here: People Operating System Diagnostic

EOS will give your business an operating system. This is the one for the people who have to run it.