Same Market, Similar Talent, Very Different Outcomes

What actually separates the companies that scale from the ones that stall?

Spoiler alert: Culture isn’t the answer.

I want to start with a question.

How many decisions are sitting in your inbox right now that have nothing to do with your strategy?

You’re not alone, and by the end of this post, I want you to understand exactly why that is and what to do about it.

Two companies

I’ve spent my career inside the engine room of growing companies. Not on the org chart as a nice-to-have, but embedded in the moments where teams either figure out how to scale or quietly start to break.

Let me tell you about two companies.

Same industry. Similar headcount. Roughly the same product.

I worked with a founder a few years back. Let’s call her Sarah. Sarah ran a 60-person SaaS company. The company was growing fast. She had a smart team and a strong product. Around the same time, I was watching another company in the same space, similar stage, with similar funding. From the outside they looked almost identical.

Three years later, one of them had doubled headcount without doubling chaos. Managers were making decisions independently. New hires ramped in weeks, not months. The founder was finally working on the business instead of inside every conversation.

The other one? The founder was still the glue. He was still in every meeting and still the last word on decisions that had nothing to do with strategy. Half their senior team had turned over. The ones who stayed were tired.

Same market. Similar talent. Very different outcomes.

If you asked most people why, they’d say culture. But that’s not an answer. That’s a label.

The scene I’ve lived more than once

A founder is frustrated. They're not angry, just done.

“We’re growing. We have smart people. But everything feels harder than it should. Projects stall. Decisions get revisited. High performers are burning out. And I’m still the glue.”

Then they look at HR and say:

“Can you help? Maybe… culture? Engagement? Something like that?”

This is the test. And here’s what usually happens.

HR answers like a support function. Programs. Surveys. Values decks. Workshops. The founder nods. Nothing changes.

Because the real problem was never a lack of caring. It was a lack of design.

The real dividing line

Here’s what I’ve seen separate the companies that scale well from the ones that stall.

It’s not talent. It’s not funding. It’s not even strategy.

It’s whether HR is treated as a support function, or as the operating system.

Think about what an operating system actually does. It doesn’t run the product. It runs everything underneath the product. It’s how decisions get made, how accountability gets enforced, how performance gets signaled, and how leaders are expected to lead.

The companies that scale well aren’t the ones with the biggest HR teams. They’re the ones that built the minimum viable people system: the fewest, most essential structures that protect speed and soul as they grow.

The three levers

There are three levers that create that operating system. Over the next few weeks I’ll take each one apart. For now, here’s the shape of it:

1. Culture by design so your values don’t get written by whoever’s loudest.

2. Role clarity and decision rights so your people can move without asking.

3. Accountability loops so trust scales with your headcount.

Most companies have some version of all three. What they don’t have is a version that works when the founder isn’t in the room.

Back to Sarah

Sarah was the last word on decisions that had nothing to do with strategy for a long time.

The hard thing is, she was good at it. She was fast. She was right most of the time. The problem wasn’t her judgment. The problem was that her judgment had become the system.

The company that scaled without her in every room didn’t have better people. They had better architecture around their people. Culture that ran without her narrating it. Roles clear enough that decisions got made without her blessing.

Accountability loops that meant she heard about problems at the right time, not after they became fires.

The way you stay scrappy as you scale isn’t by avoiding systems. It’s by designing the fewest systems that protect the things that made you great in the first place: your speed, your soul, your ability to move.

The question I’ll leave you with

If your People/HR function disappeared for 90 days, what would break?

If the honest answer is not much, that’s your signal. Not that HR has failed you, but that it hasn’t been positioned as leverage yet. It’s still being used as a support function when it should be a true partnership.

That’s the work.

And it starts now.