How to Upgrade Your Scaling SMB's Operating System Without Losing Agility

Growth is supposed to feel like acceleration. For most companies with 50-500 employees, it feels like wading through mud.

You added people, more layers, and “responsible adults.” But instead of getting faster, you got slower. Predictability is down, and coordination overhead is overwhelming your top talent.

I was discussing this exact problem with Dave West on the Scrum.org podcast, as part of a series focused on how agility can help small and medium-sized businesses tackle their growth challenges. We agreed: scaling doesn’t have to mean slowing down, but it almost always does. It’s because leaders fail to address four systemic traps.

https://api.substack.com/feed/podcast/1195288.rss

Here’s the pragmatic breakdown.

1. Your ‘Founder Brain’ Is Now the Bottleneck. The skills that got you from 10 to 30 people (hustle, intuition, product-market fit) are not the skills that get you to 100 or 300 (operating as a system). Early-stage leaders who excel at building often hit a ceiling when they need to enable a multi-team organization. The system is now too complex for a single person to manage. It’s time to scale up.

2. You Optimized for Silos, Not for Value. As you added functions—Sales, Marketing, Product, Ops—you built functional fiefdoms. Now, each department hits its own scorecard, but the customer waits. You’re spending more time in “alignment” meetings than on execution because value flow is breaking down at every handoff. You’re optimizing locally while the system slows globally.

Instead of defaulting to departments, organize around outcomes. A cross-functional “Pipeline Health” team, for instance, will consistently outperform disconnected Sales and Marketing units trying to “coordinate” via endless meetings. Your collaboration structures should reflect the flow of value, not a list of functions.

4. Your Scaling Framework Became a ‘Responsibility’ Checklist EOS, Scaling Up, D4X… these frameworks can be helpful. But too often organizations end up serving the framework instead of making it serve them. You’re treating “rocks” and scorecards as activity trackers, not as measures of real-world traction. All of these frameworks can benefit from a healthy dose of outcome orientation, aligned autonomy and evidence-based management.