You decide it is time to improve your planning. You sit down to work out where to start, and you cannot. Everything runs through one person, and the reasoning lives in their head. You ask why a number was set where it was, and the answer is fluent, reasonable, and impossible to check. The function has become a black box.
There is no wrongdoing in this. Nobody is hiding anything. It is simply what happens when a capable person carries a whole function for long enough: the logic stops being written down because it never needed to be. The first part of this series called this the catch. The very thing that made the team of one efficient, everything held in one head, is what now makes it impossible to see into. The cost shows up the day you try to change something and find there is nothing to take hold of.
The two honest objections
Move to change it and you will meet resistance, and it deserves respect, because two of the objections are true.
The first is that the current solution genuinely does some things better than anything that would replace it. That is not sentiment, it is often simply true. Years of one expert’s judgement produce a fit no standard process will match at first. You would be right to value that, and right to resist losing it.
But valuing it is not the same as keeping it. Steve Jobs put this well at Apple’s developer conference in 1997. He was cutting technologies that developers revered, genuinely brilliant work, some of it years ahead of its time, and he did not pretend it was anything less. He simply moved the question: not whether a piece is brilliant on its own, but how it fits a single coherent vision, built backwards from the customer. The same test applies here. The artisanal solution can be the best in the building at the things it does, and still be the wrong thing to keep, if it does not fit a coherent, scalable, coordinated way of running the whole company. The question is not “is it good?” It is “does it fit the whole?”
The second objection is quieter and more human. The solution is someone’s craft, built over years, and a large part of their standing. Replacing it is personal. I have been that person, watching something I built carefully give way to something plainer. The feeling is real and worth naming. It is also not a reason to keep a function the business can no longer see into.
Redesign, do not just scale
When the decision is finally made, the obvious move is to add a second pair of hands. Resist it. Two people running the same undocumented, in-the-head process is not progress. It is the same black box with a longer queue, and two people to lose instead of one.
The task is different. It is to turn an artisanal solution into an industrial one. Not bigger, but repeatable: the logic written down, the routine decisions governed by rules anyone can follow, the few genuinely hard calls clearly marked for a person. Something that runs the same way whoever is at the desk, and that fits how the rest of the company is already managed, rather than standing as a brilliant island with its own private logic.
This is where the first part pays off. Choosing the few things that matter and writing down the rules for the rest was not only how a team of one stays sane. It is the first brick of the industrial version. The reorder rules, the forecast rhythm, the short list of judgement calls: written down, all of it becomes legible, teachable, and owned by the business rather than by one person.
A planning team of one is an excellent way to begin and a poor place to stay. The work, when the time comes, is not to replace the person but to free the function from depending on them: to take what lived in one head and make it visible, repeatable, and owned by the company. Do it deliberately, while you still can, rather than the morning you have no choice.
