Companies scaling past a hundred employees usually have the building and not the foundation. Three things hold growth in place: defined decision rights and handoff ownership, managers actually trained to manage people, and people processes that are consistent and findable across every department and location.
When I work with a growing company, I show the leadership team a picture of a skyscraper. That is the company they are building, and they should be proud of it. Then I show them the Leaning Tower of Pisa. Then I show them the four to ten feet of foundation underneath a skyscraper, and we spend most of our time on that third picture.
No skyscraper stands without the infrastructure underground first. I show those three images in that order for a reason. This is where you are. This is where you are heading if you do not do this first.
Why fast growth hides the missing foundation
Organizations scale so quickly that they forget something has to hold the structure in place. The building goes up, and the infrastructure never catches up.
If you doubt that applies to you, run the small version of the test. Say you are going from ten employees to twenty-five. Do you have a handbook? Do people know what the policy expectations are? Have you set a time for them to start and stop each day? Are they hourly or salaried?
All of those things you assume will magically happen have to be built. Nobody builds them by accident.
What happens instead is chaos at the top of the building, because your employees are living in inconsistency. They are not sure what to do, and they are not sure where to go to get an answer. That is not a culture problem. That is a missing floor.
If you have already built the skyscraper too high, stop before you build any higher and start building below ground before you continue upward.
These are the three foundations I would put in first for a company preparing to grow from around a hundred employees to two hundred and fifty.
Foundation one: define who owns the work and who can decide
An updated org chart will not settle every question about responsibility. It shows reporting lines. It does not show decision rights.
Your managers need to know which decisions they can make on their own, what requires approval, and who takes over when work moves between departments. That third one is where most of the damage happens, because handoffs sit in the gaps between two org chart boxes.
Here is a test you can run this week. Ask two department heads who owns a recurring problem. If their answers differ, resolve that before another team inherits the confusion.
When decision rights are unclear, everything escalates, and escalation looks like engagement until it becomes the bottleneck. We work through that pattern in when every decision escalates, your people system is too fragile.
Foundation two: prepare your managers to manage people
The employee you promoted may know the work inside out and still struggle to address poor performance. Those are two different skills, and the promotion only tested one of them.
Have you taught them how to set expectations, give useful feedback, document a concern, and hold a difficult conversation? If not, you will get inconsistency, and the inconsistency is visible to everyone.
One manager addresses an issue immediately. Another lets the same issue continue for months. The employees picking up the extra work notice both. Eventually they stop believing leadership will do anything about it, and that belief is very expensive to rebuild.
This is the foundation companies skip most often, because manager training feels like something you do once the growth has settled. The growth is exactly what exposes it. More employees means more supervisors making decisions on behalf of your company, across more shifts, with more documentation.
Our piece on frontline leadership and retention covers what that layer needs to hold.
Foundation three: make people processes consistent and findable
Hiring, onboarding, timekeeping, policy questions, and performance reviews all need clear steps and someone responsible for keeping them current.
Employees should be able to find answers without tracking down the one person who remembers how something works. When your process lives in someone's head, you have not built a process. You have built a dependency, and that person eventually takes a holiday.
Each of those processes also needs a named owner and a review date. Without an owner, a procedure ages quietly until someone discovers it during an audit or a complaint. Without a review date, nobody ever decides whether it still reflects how the work is really done.
Accessibility matters as much as accuracy. If a supervisor on second shift cannot find the leave procedure at eight in the evening, the procedure effectively does not exist for half your workforce.
Check what actually happens across departments and locations, not what the folder says. A documented process does very little if every manager handles it differently. The gap between the written procedure and the practiced one is where your risk accumulates.
The infrastructure question buyers ask
There is a second reason to build this early, and it shows up at the least convenient moment.
I have worked with companies going through mergers and acquisitions. When the policies, procedures, benefits information, and reporting were already in place, the buyer had something solid to evaluate. They wanted the details, the reports, the factual information. When all of that exists, it is excellent collateral.
I have also worked with companies that did not have those pieces in place before they entered acquisition conversations, and it affected the value of the organization. People who do this work on the financial side have told me that missing infrastructure can drop the value of a company substantially.
Trying to pull it together after you have come to the table puts you in an awkward position. You are scrambling to answer questions that would have been much easier to work through beforehand, and the scrambling itself reads badly. It can look like you are hiding something.
We sometimes get called at HMP and asked to go through a company's materials and find what is missing before those conversations begin. That is a much better time to find out.
What to ask your leadership team before the next hiring round
Before you approve the next round of hiring, put three questions to your leadership team:
- Where do decisions keep getting stuck, and who is waiting on them?
- Which of our managers need support they are not currently getting?
- What are new employees being left to figure out for themselves?
Those answers tell you where to build. They are also uncomfortable questions, which is usually a sign they are the right ones.
I am a big believer in visuals, because sometimes that is the only way to get a leadership team to sit with a problem. The skyscraper works because everyone in the room already knows what happens to a tall building on a shallow foundation. They just have not applied it to the company they are standing in.
The signals that your foundation is already short
Leadership teams rarely come to me saying the infrastructure is missing. They come with symptoms, and the symptoms all sound like people problems.
The same question reaches three different managers and gets three different answers. A supervisor makes an exception because production is behind, and the exception quietly becomes the new rule on that shift. A new employee follows a practice that was replaced two years ago, because that is what the person training them still does. Someone leaves and takes a process with them that nobody had written down.
None of those look like a foundation issue in the moment. Each one looks like an individual making a judgement call. Put twenty of them together across two locations and you have an organization where policy is whatever the nearest manager believes it to be.
The tell is how often your answer to an operational question depends on who you ask. If it depends a lot, the structure above ground has outgrown what is underneath it.
Build below ground first
Growth does not break companies. Growth reveals what was never built.
If you are preparing to add headcount, locations, or a shift, the people infrastructure has to scale with it. Decision rights, prepared managers, and consistent processes are not administrative work you get to once the quarter calms down. They are the four to ten feet underground that lets you keep building upward.
Frequently Asked Questions
What breaks first when a company grows too fast?
Consistency. Employees end up unsure what to do and unsure where to get an answer, because policies, expectations, and processes were assumed rather than built. That shows up as a culture problem when it is actually missing infrastructure.
Is an updated org chart enough to fix decision-making?
No. An org chart shows reporting lines, not decision rights. Managers still need to know which decisions they can make alone, what needs approval, and who owns work when it moves between departments.
How do I test whether ownership is actually clear?
Ask two department heads who owns a recurring problem. If their answers differ, that gap needs resolving before another team inherits the confusion.
Why does promoting a strong employee into management often go wrong?
Knowing the work and leading people are different skills, and the promotion usually only tested the first. Without training in setting expectations, giving feedback, documenting concerns, and holding difficult conversations, managers handle the same issue inconsistently.
Does people infrastructure affect company valuation?
It can. When policies, procedures, benefits information, and reporting are already in place, a buyer has something solid to evaluate. Companies that enter acquisition conversations without them can see the value of the organization affected, and assembling it late tends to look like concealment.