The Refactoring Discipline

My partners and I have built Rootstrap over fifteen years. In that time, the firm has passed through many distinct inflection points.

These are the moments when what has been working stops working — sometimes loudly, more often quietly. Revenue plateaus. The leadership team that ran a $5M firm breaks under a $10M load. The meeting cadence designed for thirty employees suffocates a team of a hundred.

Each inflection looked different but shared one feature: whatever got us to that inflection was the thing we had to let go of next.

In our world — software development — there’s a discipline called refactoring. You restructure working code so it does what it does more cleanly, more efficiently, more ready for what comes next. Refactoring isn’t tearing down. It’s the deliberate practice of making working systems more capable.

That’s what growing a firm actually looks like. Not pure addition. Continuous refactoring. This is the discipline that separates firms that scale from firms that plateau.

What happens when you don’t refactor

The cost is rarely dramatic. It’s gradual, which is what makes it dangerous.

It manifests in predictable ways:

• Bloat. Headcount, processes, meetings, tools — accumulating without anyone questioning whether they still earn their place.
• Bureaucracy. Decisions that used to take a hallway conversation now require three meetings.
• Diminished speed. What you used to ship in two weeks takes three or four. Not because the work got harder. The firm got heavier.
• Margin compression. Bloat shows up in your P&L before it shows up anywhere else.
• Loss of the boutique edge. Speed, intimacy, senior touch, taste — diluted by every layer you add.
• Talent drift. Your best people feel the slowdown. They start looking elsewhere, or worse, they stay but stop pushing.

Every one of these is a symptom of organizational debt. Like technical debt, it accrues quietly and compounds. The firms that compound on the upside pay it down deliberately.

What needs refactoring, and when

At every inflection point, the same dynamic repeats. What got you to a level of success keeps working for a while. Then it works against you. Founders rarely catch it in time, which is how the friction shows up in five places.

The founder’s hands. Identify the highest-leverage moments where your involvement actually moves the needle and step back from everything else. Your presence in too many conversations limits the people around you. Talented operators can’t grow into senior roles when the founder is still occupying the seat.

The early processes that stop scaling. The all-company, free-for-all Slack channel. The decisions made purely by gut instinct. Most firms wait too long — the processes still mostly work, changes feel bureaucratic, and no one wants to kill the magic. So we wait. The firm grows past the system. Something breaks publicly and we replace it under duress. The discipline is to refactor before the break, not after.

The clients that built the firm. Early customers who said yes when you had nothing to show are precious. Some become your most valuable advocates. Some become friends. Some grow alongside you. But some may also become the wrong fit for the firm you are becoming. The move isn’t to walk away from them — it’s to have honest conversations early, redefine engagements to match your evolution, and orchestrate and support smooth transitions if and when necessary. Done with care, those conversations are something the best clients respect.

The people who built the firm. This is incredibly hard. The team member who was perfect for year three is not always the one you need at year ten. First, bring as many people along as possible. Training. Stretch assignments. New roles. Mentorship. Honest feedback delivered early. When leaders genuinely commit to growing their people, they usually grow. But when they don’t, the right thing — for the team, for the firm, and for the person themselves — is to confront reality rather than carry the mismatch indefinitely.

The identity. The story you tell yourself and the world about what your firm is. At each inflection, that story has to evolve. Most founders cling to the old identity past its expiration date out of pride. The story of “we’re the scrappy boutique that punches above our weight” can be the same story that caps your ambition for what’s next.

Why founders resist

Refactoring feels like betrayal of what worked. The team member you grew with deserves loyalty. The client who took a chance on you deserves loyalty. The processes that run the company were the processes that built it. Letting any of it go feels like ingratitude.

It can be genuinely scary to change something that’s still working, even when you can see the limits. The devil you know, as they say. So we carry too much, too long, until it stops fitting. The firm pays in friction, drag, and growth that never quite compounds. The founder pays in burnout.

Refactoring is a team sport

The temptation is to make this a CEO discipline. It isn’t. The firms that refactor well do it not just within leadership, but as a company.

I love the concept of the Andon cord — the Toyota Production System idea that any worker on the line can pull a cord that halts production when they spot a defect. Quality and continuous improvement aren’t owned by the managerial class. They’re owned by everyone.

Refactoring works the same way. Leaders see some of what needs to change. The people doing the actual work see more. The discipline that compounds is the one that invites everyone to flag what’s no longer serving the firm and treats those flags as gifts rather than threats. There is always room for refinement. The job of leadership isn’t to pretend otherwise. It’s to make refactoring a permanent, normal, ongoing part of how the firm operates.

The firm you built got you here.

The firm you keep refactoring — deliberately, continuously, with your whole team — is the one that takes you further in the direction of your vision.

That work never finishes. That’s the point.

Want more?

• Apply for membership in Collective 54
• Subscribe to Collective 54 Insights
• Connect with me on LinkedIn