6 min de lectura
Scaling Teams Isn't Multiplying Headcount
Many organizations still manage talent with the same spreadsheets they started with, even after multiplying headcount tenfold. Toni Macías explains why scaling people also means scaling the data infrastructure that supports them.
Toni Macías
CEO · 16 Sept 2026
Índice de contenidos
Scaling is not multiplying heads
When an organization or club grows fast in headcount, it almost always invests in attracting talent and rarely invests in the infrastructure that should support it. Here is what we typically find:
- The spreadsheet that worked for thirty people becomes a serious problem at three hundred.
- Scaling headcount without scaling people data systems multiplies noise, not insight.
- The more people join, the more it costs not to know, in real time, what is happening with talent.
More people, same bottlenecks
It is common to find organizations that have grown remarkably in recent years yet still manage key people information, performance, training, internal moves, climate, in loose documents, spreadsheets with unclear names, or systems that never got integrated with each other. The same happens in clubs that went from managing a single first team to managing several categories or sections with far higher volumes of sporting and personal data.
The problem is not just about tidiness. Important decisions, who to promote, where the risk of losing talent is highest, which area has a recurring climate problem, get made with incomplete, outdated information scattered among people who never talk to each other. The organization grows, but its ability to see clearly what is happening with its people does not grow at the same pace.
- People information scattered across documents only their creator understands.
- Talent decisions that arrive late because nobody had the data on hand at the right moment.
- Different systems, in different areas, that never talk to each other.
System capacity before headcount
Our read is that scaling teams requires scaling, at the same pace, how information about those people is organized and accessed. Skipping that does not save money, it just postpones the cost.
“You cannot lead with judgment what you cannot see clearly.”
— Toni Macías
CEO at People & Play
This does not mean buying the most expensive system on the market. It means deciding, with the same seriousness applied to a hiring plan, which information about people is critical, who needs to see it, and how often. Technology, after that, is just the vehicle.
How to grow without breaking rhythm
Preparing the people infrastructure for growth can be tackled progressively, without needing a massive project.
- Identify which talent decisions are made blind today
- Review recent important decisions and ask what information was missing or arrived too late.
- That list usually points exactly to where to invest first.
- Unify the minimum sources before adding more tools
- Consolidate scattered information into a single reference point, even a simple one.
- Adding sophisticated technology on top of messy data only multiplies the mess.
- Assign owners to keep the data alive, not just to create it
- A people information system decays if nobody updates it with discipline.
- Define who reviews and cleans that information on a regular basis.
Questions before opening another seat
Before continuing to grow headcount, it is worth asking:
- Could you say, right now, where the highest risk of losing talent lies in your organization?
- How many different documents do you need to check to get a full picture of one key person?
- Has any recent talent decision been made without all the necessary information because it was not on hand?
- Has your people data infrastructure grown at the same pace as your headcount?
- Who is responsible for keeping that information up to date, beyond whoever enters it?
Let's design real capacity, not just headcount
You do not need to stop growing to put this in order. In fact, the sooner it is addressed, the less painful it becomes later.
If you notice the information about your people is starting to fall short of your organization's size, let's talk. A first mapping of what you know, and what you don't know, about your talent is usually a good place to start.