The Undefined Role

The org chart you drew at twenty people does not work at eighty. The roles blurred in motion, the workarounds became the system, and the people who absorbed the gap are now the first ones running the math on how much longer they can sustain it.

A company that was twenty people eighteen months ago is eighty now. Someone asks who owns a particular function and gets three different answers from three different people, each one reasonably confident.

The org chart drawn at twenty doesn't work at eighty. The processes built for a team that fit in one room don't hold when half the company joined in the last six months and learned the norms from people who'd only been there four months longer. The infrastructure is running a version behind the organization, and the gap widens every week.

How It Happens

The Undefined Role is a success problem. That's the frustrating part.

The organization is growing because something is working. The product, the market fit, the team: something is genuinely good. The growth is real. The momentum is real. And the natural response to real momentum is to run faster, hire faster, ship faster.

Nobody stops to ask whether the systems can handle the pace. Because stopping feels like losing. Because the market won't wait. Because the investors are expecting the next milestone and the next one after that. Because everyone is so busy executing that there's no time to examine whether the thing they're executing against was built for an organization half this size.

The roles that made sense at twenty start to blur at forty and completely dissolve at eighty. The person who was "doing a bit of everything" is now theoretically responsible for seventeen things and actually doing three of them while the other fourteen fall through cracks nobody has time to notice. The meeting that was "the place where we align" is now either a mob of thirty people where nothing gets decided or a relic that half the org doesn't know exists.

And the workarounds, God, the workarounds. People are building shadow processes to route around the ones that don't work anymore. There's a Slack DM network that's more effective than any official channel. Someone, somewhere, is maintaining a spreadsheet that should be a system, and everyone knows it, and nobody has the bandwidth to fix it.

The People Who Absorb It

There's a profile of person who ends up carrying The Undefined Role on their back. Usually someone who was there early. Someone who "knows where the bodies are buried": which really means they know which processes are fake and which ones actually matter, who to ask to get things done versus who to ask if you want the official answer.

These people are exhausted. They became the human glue holding the organization together while the formal systems failed to keep pace. They answer the same questions seventeen times a day because there's no documentation. They patch the same holes because there's no process. They mentor the same new hires because onboarding is whatever they have time to make up between meetings.

They're also, usually, too busy to tell anyone how bad it is. Or they've told people and nothing changed and now they've stopped expecting anything to change. They're running the math on how much longer they can sustain this pace before something breaks: their output, their patience, their willingness to keep showing up.

These are exactly the people you can't afford to lose. And they're exactly the people most likely to leave if the infrastructure doesn't catch up.

What It's Costing

The Undefined Role has a financial signature, but it's not where most organizations look.

It's in decision latency. The question that should have taken a day to answer takes a week because nobody knows who owns it, or three people think they own it and can't agree, or the person who used to own it left and nobody updated anything.

It's in coordination overhead. The meeting about the meeting about the other meeting. The check-ins to make sure everyone's aligned because the systems don't create alignment automatically. The time people spend figuring out what's going on instead of doing the thing.

It's in talent cost. The senior hire who joined expecting infrastructure and found chaos. The early employee who was energized by the scrappiness and is now just tired. The backfill for the backfill for the role that was never scoped properly in the first place.

Add it up and it's real money. But more than money, it's momentum. The whole point of running this fast was to capitalize on a window. If half the organization's energy is going into navigating the dysfunction instead of shipping, you're losing the race you thought you were winning.

The Tells

The Undefined Role isn't subtle. The symptoms are everywhere once you know what you're looking at.

Role ambiguity is the norm. If you asked three people who owns a given function, you'd get three different answers. If you asked the people supposedly in those roles, they'd add a fourth. Nobody did this on purpose. The roles just expanded faster than they got redefined.

Onboarding is a hazing ritual. New hires figure it out or they don't. The ones who make it through are the ones who were resourceful enough to build their own map. The ones who needed structure quietly struggled and either adapted, burned out, or left. Everyone knows the onboarding is bad. Nobody has time to fix it.

The early employees are burning out. The people who built this thing are hitting a wall. They're too senior to do the work they used to do and too embedded to build the systems that would let other people do it. They feel responsible for everything and in control of nothing.

The culture is becoming "whatever we're doing right now." The values that were real when the team was small have thinned out as they got transmitted through layers of people who weren't there when those values were formed. What remains is a vague sense that things used to be different, and a creeping suspicion that they're not going to be again.

Why It Doesn't Slow Down on Its Own

This is the trap of The Undefined Role: the pace is the problem, but the pace also feels mandatory.

The market pressure is real. The investor expectations are real. The competition isn't going to pause while you get your house in order. And so the organization keeps running, faster and faster, accumulating infrastructure debt with every hire and every launch and every "we'll fix it later."

"Later" doesn't come. There's always another sprint, another quarter, another thing that needs to happen before there's time to build the systems that should have been built six months ago. The deficit compounds. The workarounds become the system. The chaos becomes "just how we do things."

The people who could slow things down, the founders, the leadership team, are usually the ones most attached to the pace. They remember when the scrappiness was a feature. They built an identity around moving fast. Admitting that the speed has become a liability feels like admitting they broke something by succeeding.

What Actually Fixes It

The Undefined Role resolves when someone decides that building infrastructure is as important as building product.

That's a leadership decision. It requires accepting that the organization won't ship quite as fast for a quarter while it rebuilds the systems that will let it ship faster for years. It requires naming, out loud, that the current pace is not sustainable and that sustainability matters.

The work itself is usually straightforward once the space is carved out. Map the roles and actually define them. Build the communication channels that should exist. Create the documentation that everyone's been routing around. Design the onboarding that lets new people contribute instead of just survive.

What's hard is creating the permission to do that work. Because it means slowing down. It means admitting the machine isn't as well-built as the pitch deck suggests. It means the people who've been saying "this is fine" have to acknowledge that it isn't.

If the pace has been getting faster while the infrastructure falls further behind, that gap doesn't close on its own. It has to become as much of a priority as the product it's supporting.