Transformation in mid-sized companies: when you need a rebuild and when fine-tuning is enough

How do you know a rebuild is needed?

One test answers it: will your business still make money in five years if the market keeps developing the way it's already visible today? If the honest answer is no, a rebuild is due. If the answer is yes, but with weaker numbers, your job is fine-tuning.

This test is uncomfortable, because it demands a statement about the market rather than about your own performance. Three signals point to a rebuild:

• The customer is buying something else. Not less, but something different. If you sell machinery and your buyers will soon be purchasing uptime instead of machines, you don't have a sales problem. You have a different business ahead of you.
• The service is delivered differently. When part of the value creation can be replaced by software, regulation or a new production method, your share of the final earnings shifts.
• Competition comes from a different direction. A new entrant who runs your business as a byproduct does the math differently than you do. Price pressure from that direction can't be answered with efficiency.

If none of these signals is present, a rebuild is the most expensive way to work on an earnings problem.

You can back this test with numbers instead of debating it in a meeting. Take your three largest product groups and model a five-year trajectory for each: volume, price and contribution margin, assuming the visible trend holds. If two out of three groups fall below the threshold where they cover their fixed costs, the question is answered. This calculation takes an afternoon and ends the debate about whether things are really that serious.

What separates fine-tuning from a rebuild?

The scope of the decisions, and with it the amount of attention they tie up.

The last row explains why the judgment call matters more than the approach. A rebuild that didn't need to happen burns trust. Fine-tuning in a situation that calls for a rebuild pushes the problem into a time when fewer resources are available to solve it.

What phases does a rebuild go through when it works?

Three, and they only overlap at the edges. The most common shortcut is jumping from the first to the third.

• Clarify. What will carry the business in five years, what won't, and which capabilities are missing. This phase ends with a decided direction, not an action plan. Three to six months.
• Build while the old business runs. The new business gets its own people, its own budget and its own metrics. It isn't measured against the numbers of the core business, or it loses every comparison. One to three years.
• Switch over. The new business becomes the standard business, the old one is wound down or sold. This phase requires the hardest decisions and is the one people most like to postpone.

Between phase two and phase three sits the point where most rebuilds get stuck. The new business exists, it doesn't earn enough yet, and the old business keeps funding it. As long as nobody sets a date for the switch, that state stays stable and costs money every year.

Who drives the rebuild day to day?

Not the management line alone. A rebuild of the organization creates uncertainty for the people affected. Uncertainty leads to hesitation and sometimes to resistance. If you run the change exclusively through the existing hierarchy, you lose speed at the middle level, which sits between the ambition from above and the daily reality from below.

What helps is a second network alongside the line: a community of decision-makers, multipliers and supporters from different levels and areas, with backing from the very top and clear ground rules. Alongside it sits a steering group that owns the rebuild and meets on a fixed routine.

Getting this network started is manual work and takes six things: a selection process for the community and the steering group, fixed dates for the kickoff and the reporting routine, a link to the goal cascade, clear rules with backing from the top, a communication channel that works in both directions, and a storyline that makes wins visible. The last point is the one most often forgotten, and it's the one that decides the mood.

One person from management who gets time freed up for it. Not a project lead with a steering committee, and not the management team as a whole.

The difference is practical. A rebuild produces decisions every week that cut across existing responsibilities: a sales territory gets redrawn, a price gets calculated differently, a resource goes to the new business instead of the existing one. Decisions like these are made by someone with a mandate, or by no one.

That includes relief from other duties, in writing. Anyone who owns the rebuild while continuing to run their unit unchanged will run the unit. That's not a matter of character. It's a matter of what comes first in the calendar. In practice: two fixed days per week, a deputy who takes over day-to-day business, and both announced to the leadership team.

How do you keep the organization with you?

By saying what stays the same. In phases of change, people talk a lot about the new and almost nothing about what already exists, and that's exactly where the unease comes from.

Three statements help more than any presentation: which parts of the business keep running, which sites and roles are not up for discussion, and when the next update comes. The third point is the most effective. A fixed date takes the ground out from under rumors, even when there's nothing new to report.

Resistance is information, not noise. Someone in sales who has served the same clients for twenty years and says the new offering doesn't fit there usually has an observation you can verify. It deserves to be checked instead of dismissed as stubbornness. After the check, the decision still gets made, but it's better grounded and the person stays on board.

How do you measure that the rebuild is making progress?

By numbers that show up before revenue does. Revenue from the new business comes late, and until then leadership needs something that tells them whether it's working.

Three numbers are useful. How many clients have seriously evaluated the new offering, meaning they booked a meeting of their own and asked about price or timing. How many people in the company are working on the new business and how much of their time actually goes there. And what share of investment goes into the new business, because the budget shows the real priority far more clearly than any explanation.

If these three numbers stay flat over two quarters, the rebuild isn't moving, no matter how many workshops have taken place. That's the moment for a decision about mandate, budget, and time, not for another workshop.

If you have an advisory board, a bank, or shareholders outside of management, report these three numbers to them as well. It sounds like extra work and it works in both directions: the group gets a question it can ask, and management gets a date on which standstill becomes visible. A rebuild without that outside view loses its urgency after about a year, because everyone inside the company has gotten used to the slow pace.