top of page

FIELD NOTE | 

August 17, 2026

Scale Is Not More of the Same

Scale changes the problem. More customers, people, data, and revenue do not simply create a larger version of the company you already had.

When organizations talk about scaling, they often imagine more.

More customers. More employees. More transactions. More products. More markets.

The assumption is that the organization will need to do what it already does, only at greater volume.

Sometimes that's true.

But scale also changes the nature of the system.

Ten people can coordinate through familiarity. They know who understands what, who needs to be involved, and which decisions can be made without much discussion.

At a hundred people, those assumptions become less reliable.

People who need to work together may never have met. Information that once traveled through proximity needs another way to move. Decisions that were obvious to a founder become questions for someone who doesn't share the founder's history.

The work hasn't simply multiplied.

The relationships required to accomplish it have changed.

The conditions that made the old system work

I think we sometimes judge early-stage systems unfairly.

A spreadsheet isn't necessarily a bad system. Neither is a Slack channel, a weekly meeting, or a founder remembering which customers have unusual agreements.

Under the right conditions, those can be sensible solutions.

They are inexpensive, flexible, and easy to change.

And they often depend on something we don't count: shared context.

When a small group works closely together, a great deal of information doesn't need to be formally represented. People remember conversations, recognize exceptions, and understand what someone means without requiring every definition to be documented.

That can be an advantage.

But as the organization grows, the conditions supporting that advantage begin to change.

The person who remembers every exception can't participate in every decision.

The informal agreement between two teams doesn't automatically extend to twenty.

The same term can acquire different meanings in different parts of the organization.

What worked before may still be working exactly as designed.

It just isn't operating under the same conditions anymore.

Growth changes the cost of coordination

One of the things I look for is the point where an informal arrangement becomes a dependency.

A person becomes a queue.

An exception becomes a recurring category of work.

A question that used to be answered once gets answered separately by five teams.

A decision that once took minutes now requires several meetings because nobody has enough shared context to make it alone.

These aren't necessarily signs that people have become less capable.

They may be evidence that the relationships between the work have changed.

And adding more people doesn't automatically resolve the problem.

Sometimes it creates more interfaces, more possible misunderstandings, and more decisions about who needs to know what.

The organization can have more total capacity while becoming less capable of acting coherently.

That's an interesting problem because the usual response to growth is to add resources.

More headcount. More tools. More process.

But the constraint may not be the amount of work any individual can perform.

It may be the amount of coordination the existing structure can support.

Structure has a cost, too

I don't think the answer is to formalize everything as early as possible.

Structure creates its own obligations.

Someone has to maintain it. People have to learn it. Definitions have to be agreed upon. Exceptions have to be handled. Decisions become harder to reverse once they're embedded in systems that other people depend on.

Formalization can also preserve assumptions long after the conditions that justified them have disappeared.

There's a reason informal systems are attractive.

They allow people to move quickly while they're still learning what the work requires.

The design question isn't whether informality or structure is better.

It's when the cost of continuing informally exceeds the cost of building and maintaining something more explicit.

And which parts of the work have become stable enough to formalize without making the organization less capable of learning.

Not every growing organization crosses those thresholds at the same size.

The relevant question is what has changed about the work and the relationships required to accomplish it.

Scale needs circulation

I've described communication as the circulatory system of scale.

I keep returning to that idea because growth changes how far information has to travel.

In a small organization, someone may understand a customer problem because they were in the meeting where it first appeared.

Later, that information might pass through Support, Product, Engineering, Finance, and several management layers before reaching someone who can change the underlying condition.

At every boundary, something is selected, summarized, translated, or omitted.

That's not necessarily a failure. People need information they can use, not every detail of everything that happened.

But it means the organization needs ways to preserve the information that matters as it moves.

Especially information that contradicts what people already believe.

The farther someone is from the original event, the easier it becomes to receive a coherent explanation that is missing something important.

And scale can make that distance greater without anyone intending it.

The answer isn't for leaders to participate in every decision or demand more reporting.

It's to design ways for information to travel accurately enough that people can act without needing to reconstruct the entire organization around every problem.

A growing organization needs better ways to sense what's happening, not only better ways to direct what happens next.

Becoming something different

I think this is where organizations can get into trouble with the language of scaling.

It suggests that success means preserving the existing model while increasing its output. But sometimes growth changes the organization enough that preserving the model becomes the constraint.

A structure that once supported autonomy may begin to create confusion.

A decision process that once protected quality may become a bottleneck.

A shared understanding that once held the organization together may no longer be shared.

Those changes don't necessarily mean the original design was wrong.

They mean it was designed for different conditions.

I don't think scaling is simply the process of making an organization bigger.

It's recognizing when the organization has become something different—and being willing to redesign the relationships that allow it to work.

The difficult part is knowing what should change and what should remain.

Not every informal arrangement needs replacing. Not every new layer creates value. Not every increase in complexity requires a more complicated system.

But growth changes what people can know, what they can coordinate, and what they can reasonably hold.

Eventually, doing more of the same thing stops producing more of the same result.

Scale isn't only a question of how much the system can handle. It's a question of what kind of system the work now requires.

bottom of page