From doing everything to leading: a founder's guide
How a founder moves from doing every task to leading: log your time, hand work over properly, write down decision rights and grow people who can lead.
Share on WhatsApp
Conceptual image · created with AI
The habits that kept a business alive in its first years are often the ones that stop it growing later. When every task and decision still passes through the founder, the business can only grow as fast as one person can work.
Moving to leading is not about becoming less involved. It is about being involved in different things, and it can be done in small, deliberate steps. Here is a practical order in which to take them.
What you should come away with
- Log three typical days to see how much of your time goes to work in the business and how much on it
- List what only you do, then challenge each item and choose three to move
- Hand work over with a clear outcome, a check-in point and room to decide
- Write a one-page note of which decisions the team can make alone, and review it
- Expect different, imperfect ways of working, and judge them against the agreed standard
- Grow a second layer of leaders through real stretch work, not only through hiring
In the early years, the founder who does everything is often what keeps a business alive. They sell, deliver, answer the phone, chase payments and fix whatever breaks. The trouble starts when the business grows and the founder's habits do not. Each new problem still lands on the same desk, and the founder gets busier while the business stalls. Moving from doing everything to leading is mostly a matter of changing what you do, in small and deliberate steps.
Start by looking at your actual week, not the one you intended. Keep a simple log for three days, in half-hour blocks, and note what you did. Then mark each block as work in the business, such as delivering, selling or solving today's problem, or work on the business, such as planning, hiring, fixing a process or reviewing numbers. Most founders find the second category is close to empty. That is not a failing. It simply shows where the shift needs to begin.
Next, write a list of everything only you do. Be honest about it. For each item, ask whether it truly needs your judgement or your relationships, or whether it is there because it has always been. Include the tasks you simply enjoy. It is fine to keep some of them, but you should know that you are keeping them by choice. From this list, choose the three least necessary for you, and plan how to move them. Start with the one that is easiest to explain and least risky if it goes slightly wrong.
Handing work over properly takes more care than most founders expect. State the outcome you want and why it matters, not only the steps. Agree a deadline and a point at which the person will check in. Say what they can decide for themselves and what they should come back about. Offer help once, then step back. When the work comes back, review it and give feedback, whether it went well or not. The common failure is handing something over vaguely, finding it done differently, and taking it back. After that, the person learns that it is safer to ask than to decide.
Be explicit about decisions, too, because many founders delegate tasks but keep every decision. Write a one-page note listing which decisions anyone in a role can make, which should be made and then reported, which should be discussed first, and which only you make. Put limits in rupees where money is involved, for example on discounts or purchases. Share it with the team and review it every few months. A great many daily messages disappear once people know where the boundary is.
Expect to be uncomfortable. Your team will do some things differently from you, and some of those ways will be slower or less polished than yours. The test is not whether it matches your way, but whether it meets the standard you agreed. Accept that a few manageable mistakes are the cost of people learning, and when one happens, ask what they learned before you say what you think. Fix the cause, such as unclear authority, and not just the error.
Then think about who will lead. A business with one decision-maker has one point of failure. Look for people who already help colleagues without being asked, raise problems with a possible solution and take ownership when things go wrong. Give them a stretch: a small project to lead, a weekly meeting to run, a new colleague to train, or a supplier relationship to manage. Talk to them about what they want to do next. A first-time manager needs to be shown the job, since managing is different work from doing, and the best performer does not always make the best manager. Some good people prefer to grow as specialists, and that is a legitimate route.
Finally, set direction. One of your main jobs as a leader is to say where the business is going, in plain words: what matters most this quarter, what you will not do, and how people will know things are going well. A team cannot follow a direction that has not been stated. Ask two or three people for honest feedback on what slows them down, in writing if that makes honesty easier, and choose one thing to change.
A hypothetical example may help. An owner approves every discount, however small. She agrees a rule: the sales lead can give up to a set percentage, and anything above comes to her. In the first month the sales lead makes two decisions she would have made differently. She discusses them afterwards instead of reversing them. Over time, requests to her drop, and the sales lead starts bringing recommendations instead of questions.
This week, do three things. Log your time for three days. Pick one task from your 'only I do this' list and decide who should take it. Draft the first five lines of your decision note. If you can only do one, make it the log, because it shows where your time goes and gives you a basis for every other change.
Letting go will not happen all at once, and it is not a promise that nothing will go wrong. It is a way of making the business less dependent on one person, including you.