What Built It Won’t Scale It
Some Problems Only Show Up After Success
There is a specific kind of company problem that only shows up after things are going well.
Not the early problems — scrambling for revenue, building credibility, finding the right people, figuring out whether the market actually wants what you have. Those problems are hard, but they have the clarity that comes with urgency. The path is obvious even when it is steep.
The harder problem arrives after those are solved.
The company is growing. The work is good. The reputation is real. And something is still wrong — not in any one place, but everywhere at once, in a way that is hard to name until the cracks are large enough to see.
Work is getting done, but no one has clean visibility into whether it’s getting done profitably. Decisions that used to take a five-minute conversation now take two weeks, three email threads, and an unscheduled call nobody was prepared for.
The best people are buried — not in the work they should be doing, but in the organizational weight that has quietly redistributed itself onto whoever is most trusted and available. Hiring is happening, but in response to pressure rather than strategy, which means the team is larger without being stronger in the ways that actually matter.
And the culture that used to hold everything together without anyone having to name it starts to feel thinner. It is still there. But it is not doing the same work it used to do, because the organization it is being asked to hold has changed shape.
When Instincts Stop Being Enough
The problems described above are not evidence that something went wrong. They are evidence that something went right.
Organizations that never hit this threshold never grow past a certain point. The scramble for visibility, the decision bottlenecks, the culture that used to hold everything together without any formal support — these are not signs of a broken company. They are signs of a company that built something real enough to outgrow its original infrastructure.
That distinction matters, because it shapes how leadership responds. If this moment looks like a problem to fix, the response is reactive: patch the most visible crack and get back to work. If it looks like a threshold to cross, it becomes a design question: what does this organization need to become to be ready for the growth we actually want — not just the growth that happens to us?
That shift in posture is the difference between managing what the company is and building what it needs to become. The instincts that built the company — respond fast, trust the people closest to the work, stay lean, keep things moving — were exactly right for as long as they worked. The problem is that those instincts are not a system.
They are a person, or a handful of people, functioning as a system through proximity, judgment, and accumulated trust. At a certain scale, that stops being enough. The company starts needing things it was never designed to have.
Most leaders can remember the moment when someone finally says what everyone has been circling: we can’t keep running this like a startup. The specific words change; the recognition is the same. What got us here will not get us to where we want to go.
What usually follows is some version of strategic planning. Not because someone had a bright idea in isolation, but because it is the most available vocabulary for the work the organization is now being asked to do: to stop operating from instinct alone and start deliberately designing what the next stage needs to become.
The word “strategic” is easy. The practice is not. The first time a team sits down to do real strategic planning, they discover they do not entirely agree on where the company is going, or why, or what they are willing to trade to get there. Those conversations are harder than the work was.
And the plan that comes out of them — if it stays honest — is not a document. It is a decision framework: a way of making choices the organization can act on without routing every question back through the same two people. Strategic planning, done seriously, does not make the hard decisions disappear. It creates the structure that lets you make them consistently, without starting from scratch every time.
Why Culture Is the Hardest Thing to Carry
Of everything that gets harder to carry through this transition, culture is the one that surprises leaders the most. Not because they didn’t value it. Because they never had to think about how it traveled.
In the early stages of a technical firm, culture is not a program. It is a presence. It lives in proximity — in who is in the room, on the job site, on the drive to the project. It runs through the founder or principal being close enough to the work that their standards, instincts, and way of handling hard situations are visible to everyone around them.
The team learns what quality looks like not because it was written down, but because they watched it happen. That is a remarkably effective system. It is also a system that was never designed to scale.
As the organization grows, the math changes. The people who have been there from the beginning carry the culture in their bones. The people who joined in the last two years often learned it secondhand, or not fully at all, because no one had time to be deliberate about transmission when the priority was getting them productive.
In industries like transportation infrastructure, firms live in a constant split between the office and the field. Crews, project sites, remote assignments, people who spend more time in a truck or on a job than at a desk — that is what the work requires, and the culture was built with that reality in mind.
The issue is not the structure. The issue is that the informal, presence-based system that carried culture worked only while the organization was small enough for senior people to stay close to most of it.
As the firm grows, that coverage thins. Not because the structure changed, but because the organization got larger than any informal system can reach.
The gaps that open up — between people who have been there long enough to carry the culture instinctively and those who joined recently, between crews who work close to leadership and those who don’t — are not caused by having field staff. They were always there. Growth just makes them visible.
Most leaders sense this before they can name it. Something feels different. The company they are running doesn’t feel quite like the company they built, and the instinct is to blame size — to treat growth itself as the problem.
But size is not the problem. The problem is that the system for carrying culture was personal, informal, and proximity-dependent, and the organization has grown beyond the reach of that system.
Beyond the Poster on the Wall
When culture starts to slip, most organizations respond by writing things down: core values, a mission statement, a set of principles meant to capture what the company has always stood for.
That work is necessary, but it is not sufficient. Culture is not what an organization says it values. Culture is what it consistently reinforces — and what it quietly tolerates. The distance between those two is the real measure of cultural health.
A firm can have a beautifully written set of values and a lived reality on job sites and in project offices that tells a different story. People inside the organization feel that gap long before leadership names it.
Closing that gap is not a communications problem. It is a leadership and accountability problem. The standards the firm intends to hold have to be visible in behavior — in how senior people respond when something goes wrong, in what gets addressed and what gets walked past.
In a distributed firm, where leadership cannot be in every room, behavior is the only carrier that reaches everywhere. Making culture operational means being willing to hold the standard even when it is inconvenient, and building enough structure around that commitment that it does not depend on one leader’s presence or energy on any given day.
What that work produces is not a nicer poster. It is an organization where the culture can travel — where crews three states away and remote staff who have never been to the main office still know what the firm stands for, because they see it in how the work gets done around them every day.
Four Questions Worth Sitting With
The questions below are not an assessment. They are the questions a good advisor would ask in the first honest conversation about culture — questions that are easy to answer in the abstract and much harder to answer about your specific firm, your specific people, right now.
If you asked someone who joined your firm in the last eighteen months — not a senior leader, someone closer to the field or the project work — what this company actually stands for, what would they say? How confident are you in that answer?
Where in your organization is the standard held most consistently?
Where does it get quietly walked past?
What is the real difference between those two places?
Who in your firm is protected by their technical performance in ways that allow them to avoid the cultural standard?
Is that a deliberate choice or something that simply accumulated over time?
What is your culture currently running through — which people, which relationships, which presence — and what happens to it when those people are not in the room?
Those questions are worth sitting with. And they do not stop at the organization. The same logic — the gap between what you say you stand for and what actually gets reinforced, the informal systems that stop scaling, the question of what got you here and whether it will take you where you want to go — applies to a career, to a leadership identity, to the person running the firm as much as to the firm itself.
If you do not protect and evolve your culture on purpose, it will drift to places that cannot hold what you are trying to grow. That is a conversation for another issue.
— Dr. James Bryant, P.E.
P.S. If you found this article useful, I’d love to hear from you — and please consider sharing it with a friend or colleague who might need it.