Organizational Design: The Quiet Reason Growing Teams Stop Growing

Every organization I’ve ever consulted with has hit the same wall at roughly the same point in its growth. The wall isn’t market saturation. It isn’t product. It isn’t capital. It’s organizational design — and most leaders never name it as the actual problem because the symptoms point everywhere else.

The symptoms look like this. Decisions slow down. Cross-functional projects stall. Good people start leaving. Meetings multiply. The founder feels like they’re working harder than ever and seeing less progress than before. Some part of the organization is constantly on fire, and putting out one fire just lets two more start somewhere else.

What’s actually happening

What’s actually happening is that the structure that worked at five people stopped working at fifteen, and nobody redesigned it. The roles that made sense when everyone could see each other every day stopped making sense when half the team is remote. The decision-making process that was “ask the founder” stopped scaling when the founder couldn’t be in every conversation. The accountability structures that didn’t exist when everyone was a generalist became chaos when specialists came onto the team.

The organization grew. The design didn’t. The gap between what the organization is and how it’s structured is where the dysfunction lives.

The categories that matter

Healthy organizational design covers a small number of categories that almost always need explicit attention as a team grows past ten people:

• Decision rights. Who decides what, with what input, and in what timeline? The absence of clear decision rights is the single most common driver of organizational paralysis.
• Reporting structure. Not just who reports to whom — but how the reporting actually works. What does a one-on-one cover? What gets escalated and how?
• Communication cadence. Standing meetings versus async updates. Weekly versus monthly rhythms. Who attends what, who doesn’t, and why.
• Performance and accountability. How do people know whether they’re succeeding? What happens when they aren’t? Most teams have wishes here, not systems.
• Onboarding and offboarding. The processes that determine whether new hires become contributors in 60 days or 180 days. The processes that determine whether departures cost you institutional knowledge or preserve it.

What I bring to this work

I’ve led teams inside higher education at three different institutions. I’ve built ministry structures inside churches. I’ve consulted with nonprofits, for-profits, and faith-based organizations across all four divisions of Pathway Advisors. The patterns repeat. The solutions are knowable. What’s hard is the discipline to actually do the redesign — and the willingness to disrupt comfortable patterns that aren’t working anymore.

If the description in this post sounds uncomfortably familiar, the organization doesn’t need a new strategy. It needs a structural intervention. We do that work, and we do it in a way that respects what’s already working rather than tearing the place down.

---