What do you do when the very thing that got you here becomes the thing holding you back?

There is a concept worth borrowing from biology: Lobsters grow by shedding their rigid shells.
To grow, a lobster must spend a vulnerable period without protection before a new, larger shell can form.
The old shell didn't fail. It served its exact purpose.
But without shedding it, further growth is literally impossible.

Companies work the exact same way. The processes, structures, and habits that drove your early success will eventually become your biggest bottlenecks. This isn't a failure; it is a natural consequence of scaling.

The shell that once protected you is now limiting you.

The Symptoms of a Too-Tight Shell

Most companies chasing significant growth or culture change will eventually hit a hard ceiling. You know your company is constrained when:

  • Reactivity rules: Every decision feels like a reaction to an immediate crisis. You know you're here when the sound of a new Slack notification triggers a fight-or-flight response.
  • Tech debt spirals: Technical debt accumulates much faster than your team can address it.
  • Decision paralysis and stagnation: Frustration that nothing moves forward. Decisions are endlessly debated, deferred, or made in a meeting only to never be acted upon. Usually right after someone says, "let's take this offline," which we all know is where ideas go to die.
  • Firefighting is the baseline: Individual contributors spend their days patching instead of building, whilst leaders manage incidents rather than setting strategy.

The most dangerous part? This dysfunction feels normal. Teams adapt to the pressure, and a team that used to ship weekly slowly degrades to shipping monthly without anyone noticing the exact shift.

Surviving with intention

You cannot always call for a massive reset the moment you feel constrained; real people are depending on your real work. However, how you navigate this survival phase makes all the difference.

Under pressure, the instinct is often to panic and reach for immediate relief.
To be clear: formalising a process, introducing a new tool, or reorganising a team are not inherently bad moves. In fact, they are often necessary steps to stabilise the ship. The danger lies entirely in how and why they are executed.

  • The Trap of the Band-Aid: When changes are slapped on as panicked, reactive quick fixes, they carry a compounding cost. They stack on top of each other thoughtlessly until temporary workarounds become your permanent, limiting culture. This is how you end up with a mission-critical business process that relies entirely on a single spreadsheet named Data_Final_V3_REALLY_FINAL.xlsx living exclusively on Robert's desktop.
  • The Power of the Bridge: When you restructure a team or add a process intentionally, acknowledging it as a stepping stone toward a larger structural shift, it serves a vital purpose. It needs to be part of a bigger, clear plan.

Survive with intention: when leadership acknowledges that the current state is temporary, you can make smarter decisions. You can accept a slower pace in the short term to preserve your options, ensure your organisational changes are thoughtful rather than reactive, and keep the core problem highly visible.

How to Execute a Reset

Eventually, a slow bleed in delivery or a major escalating incident will force your hand. A good leader listens to the signals from engineers and delivery leads, who feel the weight of these constraints firsthand and often try to act before disaster strikes.

When it is time to shed the shell, here is what it takes:

  • Shift your mindset: Leadership must accept that things will get slower before they get faster. A structural change is required, not just another layered fix.
  • Carve out real space: A reset demands dedicated time, budget, and attention pulled away from day-to-day delivery.
    And no, booking a two-hour "strategy workshop" on a Friday afternoon does not count.
  • Make it company-wide: Technical debt is rarely just an engineering problem; it reflects decisions across product and leadership. And yes, this includes that one "tiny" feature Sales promised a major client before asking if it was even possible to build. Shared ownership is mandatory.
  • Be transparent: Customers need to be part of the conversation. Communicating honestly about changing timelines builds trust instead of eroding it.

Hitting Your Limits is a Sign of Success

Here is the reframe that matters most: Constraints are a signal, not a failure.

Companies that struggle the most are the ones that treat constraints as a source of shame to be hidden from investors, customers, and their own teams. But feeling constrained simply means you have outgrown your current structure. That is a fantastic position to be in, provided you are willing to shed the shell.

When you emerge from a proper reset, you aren't trying to return to how things used to be. You have built a new shell designed specifically for your next stage of growth. It won't last forever either, but next time, you won't be afraid to shed it.

So maybe ...

the shell is the bottleneck