The word "manage" gives itself away if You look at where it comes from. It goes back to the Italian maneggiare, to handle, originally to handle horses, from the Latin manus, the hand. And many managers do exactly that: they handle everything by hand. Every employee, every task, every step. Like a parent teaching a child to write by holding the child's hand in his own. At first this is necessary. But if a year later the parent is still guiding the child's hand, the child has never learned to write, and the parent has no time for anything else.
For many years I have watched how management works in small and mid-sized companies, and I see the same picture again and again. The founder started out doing everything himself. Then he hired people but went on doing everything himself, only now with his employees' hands. Every email to a client passes through him, every decision waits for his approval, every task gets checked and redone by him. The company grows, and the founder turns into a bottleneck through which the company's entire life has to squeeze.
The puppeteer and the captain
There are two images that help me explain the difference. The first is the puppeteer. He holds strings to every figure, and the puppets move only when his fingers move. This is very precise control: everything happens exactly as intended. But a puppeteer has ten fingers. As soon as there are more puppets, the strings tangle, the figures freeze and the show stops.
The second image is the captain of a sailing ship. He does not haul every rope himself. He sets the course, knows where the ship is going and why, watches the weather and the chart. The sailors themselves know how to set the sails, when to reef, how to respond to a gust. The captain steps in when he sees danger or when the course needs to change. The ship sails on even while the captain sleeps, because the system works without him.
A good leader is measured not by how many decisions he makes, but by how many right decisions get made without him.
Why we handle everything by hand
The reasons are understandable, and they do not make someone a bad leader, they make him a tired one. The first is fear: "If I don't check it, they'll get it wrong, and I'm the one who answers for it." The second is speed: "Explaining takes longer than doing it myself." The third is habit. A founder who once sold, designed and programmed himself genuinely does these things better than many of his employees, and it is physically hard for him to watch someone do them worse.
All three reasons are true in the moment. Yes, explaining takes longer. Yes, the employee will do it worse than You. But that is calculating one step ahead. Over the long run a leader who does everything himself limits the company to the size of his head and the number of hours in a day. And employees who are constantly led by the hand stop thinking, because why think if it will be redone anyway.
Management is architecture
As an architect, I find this definition closest: management is designing a system in which the right things happen without constant manual intervention. Exactly like good software architecture: modules know their area of responsibility, communicate through clear interfaces, errors are detected automatically, and the architect does not sit there calling every function by hand.
In the nineteenth-century Prussian army a principle emerged that later came to be called mission command. The commander gives a subordinate the goal and explains his intent: what must be achieved and why. But he does not dictate how exactly to act. Because on the battlefield the situation changes faster than orders arrive, and the officer on the spot sees more than the general at headquarters. Business today resembles that battlefield even more.
In practice, managing through a system rests on several pillars:
- A clear goal. People understand not only what to do but why. Then they can make decisions in situations You did not foresee.
- Standards instead of checks. Instead of checking every piece of work, You describe once what a good result looks like.
- Decision rights. It is clear which decisions an employee makes alone, which he coordinates and which remain with You.
- Transparency. You see what is happening without asking. That is what proper business systems are for: CRM, task tracking, reports. At Ingello we build Forma largely for this reason: so a leader can see the state of the company on a screen instead of piecing it together from phone calls.
- Feedback. Regular short reviews that discuss not who is to blame but what to improve in the system.
How to stop handling everything by hand
The transition does not happen in a day, and dropping all the strings at once is as dangerous as holding them forever. The puppets will simply fall. It is better to start with one area. Choose a type of decision that currently passes through You but could be made without You. Describe how You make it: what You look at, what criteria You use, where the boundaries are. Hand it over to someone together with the right to make mistakes. For the first weeks, look at the result but do not interfere in the process. There will be mistakes, and that is tuition that will pay off.
What to do tomorrow
Run a simple thought experiment: if You went offline for a month starting tomorrow, what would stop in the company? Write down everything that comes to mind. That is the list of strings You are holding. Pick one, the simplest, and this week hand it over together with a description of the goal and the right to decide. A month later, take the next one. In a year You will be surprised how much time You have for what a captain is supposed to do: watch the horizon and choose the course.
