The delegation trap in Indian SMEs is not a leadership failure. It is a founder’s habit that has outlived its usefulness. When you started with five workers in a Ludhiana shed or a Rajkot workshop, you did the estimating, the machine setting, the vendor chasing, the quality check, and the dispatch entry. Now you have 60 or 120 workers. You are still doing too much of it. Delegation is the practice of transferring decision rights and operating tasks to others while keeping accountability for outcomes. It sits next to span of control, shop-floor ownership, standard work, and second-line development. For owners and plant heads in auto components, light engineering, metal fabrication, plastics, packaging, and textiles across tier-2 and tier-3 clusters, the inability to delegate is not a personality quirk. It is a capacity ceiling that shows up as late deliveries, stalled supplier development, and an owner who cannot leave the factory for a customer visit in Pune or Faridabad without twenty phone calls.

Why You Are Still Doing Everything Yourself
Let us name the real reasons without dressing them up. In most small and medium manufacturing units, the owner or senior plant manager holds on to tasks because of three forces: fear of quality loss, lack of a trained second line, and the emotional pull of being useful. None of these are imaginary. A Coimbatore pump-component unit owner once told me, “If I don’t check the final packing list, the customer gets short shipment.” He was right. The packing supervisor had been changed four times in six months. But the fix was not to keep checking the list forever. The fix was to build a packing checklist, train one person, and audit weekly instead of daily.
In auto-component shops in Pune and Ahmedabad, the same pattern appears with machine setting. The owner is the only one who can set the CNC lathe for a tight-tolerance job. So the owner stays near the machine, and every other responsibility waits. This is not delegation failure; it is skill concentration. Until the skill is transferred, the owner cannot step away. The problem is that many owners do not see skill transfer as a production task. They see it as an extra burden. So the machine remains a personal tool, not a company asset.
What Delegation Actually Means on a Shop Floor
Delegation is not telling someone, “You handle dispatch from now.” That is abdication. Delegation in a manufacturing unit means transferring a defined task with three things attached: a clear outcome, a method or boundary, and a review rhythm. For example, in a Faridabad sheet-metal fabrication unit, the owner wanted to stop approving every purchase order under ₹25,000. He created a simple rule: the purchase manager can approve any order under ₹25,000 if it is from an approved vendor list and matches the rate contract. Above that, the owner signs. Every Friday, the purchase manager gives a one-page summary of orders placed, vendor, amount, and delivery date. The owner reads it in ten minutes. That is delegation with a control point. The owner did not lose control. He changed the point of control from before the decision to after the decision.
Many owners confuse delegation with losing authority. Authority remains with you. What you transfer is the task and the decision right within a boundary. The boundary matters more than the task. A textile unit in Ahmedabad gave the shift supervisor authority to stop a machine for safety or major quality issues without calling the owner. The supervisor was hesitant for two weeks. Then a yarn breakage jammed a roller. He stopped the line, saved the batch, and called the owner after. That is the moment delegation starts working: when the person uses the authority within the boundary and reports after.

The Real Cost of Not Delegating
The cost is not just your time. It is the factory’s throughput, the supplier’s development, and the second line’s confidence. When you do everything yourself, you become the bottleneck. A Rajkot auto-component unit with 85 workers had a simple problem: the owner personally handled all customer complaint calls. Every complaint went to his mobile. He would stop whatever he was doing, call the quality inspector, check the part, call the customer back. The result: production planning meetings were interrupted, vendor follow-ups delayed, and the owner’s evening was spent on firefighting. The unit’s on-time delivery stayed at 82 percent for three quarters. After he delegated complaint logging and first response to a quality engineer with a clear escalation rule, on-time delivery moved to 91 percent in four months. Not because the engineer was better than the owner. Because the owner finally had time to fix the root causes instead of answering the phone.
In plastics and packaging units, the same bottleneck appears in die changes and job scheduling. The owner knows every die, every material, every customer’s tolerance. So the owner does the scheduling. When the owner travels for a day, scheduling stops. The plant runs on yesterday’s plan. Delegating scheduling means building a simple job card system, defining priority rules, and letting the production supervisor make the daily plan within those rules. The owner reviews the plan every morning for ten minutes. That is enough.
Why the Second Line Is Weak in Most Indian SMEs
Let us be direct. Most tier-2 and tier-3 manufacturing units do not have a real second line because the owner has never allowed one to form. Workers and supervisors are trained to ask, not to decide. In Ludhiana, a hosiery unit with 150 workers had a supervisor who had been there for twelve years. He knew every machine, every operator, every yarn lot. But he still called the owner before changing a machine speed or approving a fabric batch. Why? Because for twelve years, the owner had corrected him every time he made a small decision. The supervisor learned that the safest decision was no decision. This is not a lazy supervisor. This is a system that punishes initiative.
Building a second line requires three things: selecting the right person, giving them a small area of ownership with clear limits, and tolerating a few mistakes that cost less than your own time. In a Coimbatore motor-component unit, the owner selected a diploma engineer to own in-process inspection for one product line. For the first month, the engineer missed two defects that reached the customer. The owner’s first instinct was to take the job back. Instead, he asked the engineer to write down why each defect was missed and what check he would add. The engineer added a go/no-go gauge check after the second operation. The defect did not repeat. That is how a second line grows: through small failures and corrective loops, not through perfect execution from day one.
A Practical Delegation Sequence for a 20–200 Worker Unit
Do not try to delegate everything in one month. That will fail and you will say, “I tried, it doesn’t work here.” Instead, follow a sequence that respects the reality of your shop floor.
Step 1: List what only you do today
Take a plain notebook. For one full week, write down every task you personally handle, no matter how small: machine setting, vendor calls, quality sign-offs, dispatch entries, customer visits, bank follow-ups, worker attendance, purchase approvals. At the end of the week, group them into three columns: tasks that only I can do, tasks that someone else could do with training, and tasks that someone else could do tomorrow with a clear rule.
Most owners find that the third column is larger than they expected. A Faridabad packaging unit owner listed 23 tasks. Only four were truly owner-only: bank negotiation, one key customer relationship, final pricing for new jobs, and hiring for senior roles. The other nineteen could be delegated with a rule and a review rhythm. That list is your delegation queue.
Step 2: Pick one task and define the boundary
Do not pick the hardest task first. Pick a task that is frequent, visible, and has a clear pass/fail outcome. Daily production reporting, purchase order approval below a limit, first-piece inspection sign-off, or vendor delivery follow-up are good candidates. Write down: who will do it, what is the exact outcome, what are the limits, and how often you will review.
For example, in a Rajkot forging unit, the owner delegated daily production entry to the shift supervisor. The rule: every shift, the supervisor enters production quantity, scrap quantity, and downtime reason in a register before leaving. The owner reviews the register every morning at 9:15. No entry, no chai. That is the review rhythm. It takes the owner five minutes.
Step 3: Train by doing, then watching, then leaving
Training in a manufacturing unit is not a classroom. It is three rounds. First round: you do the task, the person watches and asks questions. Second round: the person does the task, you watch and correct. Third round: the person does the task alone, you review the output. This applies to machine setting, quality checks, vendor calls, and even customer emails. The third round is where most owners get stuck. They keep watching. Watching is not delegation. Watching is supervision. You must leave the room and let the person do it alone, then check the result. That is the only way the skill moves from your hands to theirs.
Step 4: Set a review rhythm, not a permission rhythm
Many owners delegate the task but keep the permission. The person still has to ask before every action. That is not delegation. That is shifting the work without shifting the decision. Instead, set a review rhythm: daily for the first two weeks, then weekly, then monthly for stable tasks. The person knows they will be checked. But they do not need to ask before acting within the boundary. This is the difference between a supervisor who owns a process and a supervisor who is a messenger.
What to Do When the Person Fails
Failure will happen. A vendor order will be placed with the wrong specification. A dispatch will go with a short quantity. A machine setting will be off. When this happens, do not say, “This is why I have to do everything myself.” That sentence kills delegation in your unit for a year. Instead, ask three questions: What exactly went wrong? Was the boundary unclear? Was the training incomplete? Then fix the boundary or the training, not the person.
In a Pune auto-component unit, a purchase engineer delegated to order cutting tools placed an order for the wrong insert grade. The owner found out when the tools arrived. His first reaction was anger. Then he checked the purchase file. The approved vendor list said “insert grade: general purpose.” The engineer had ordered exactly that. The problem was the boundary was too loose for the specific job. The owner added a column to the purchase requisition: “job number and material grade.” The engineer kept the authority. The mistake did not repeat. That is how delegation matures: through boundary tightening, not through authority withdrawal.

Delegation and Family Governance
In family-run SMEs, delegation has an extra layer. The next generation or a cousin may be the person to whom you delegate. This is harder, not easier. You cannot fire a cousin. You cannot easily demote a son. So the boundaries and review rhythms matter even more. In a Ludhiana textile unit, the owner delegated vendor development to his son. The son had an MBA and good ideas, but he did not know the vendors personally. The owner expected him to negotiate like a veteran from day one. The son failed twice. The owner took the work back. The son lost confidence. The real problem was not the son’s ability. It was the owner’s expectation of instant skill transfer without a training round.
A better approach in family units is to delegate a project, not a role. Give the next generation a specific project: reduce rejection in the plating section by 20 percent in three months, or bring two new vendors for packaging material with a cost saving of 8 percent. A project has a clear end, a clear measure, and a natural review point. It builds trust without handing over a permanent function too early. Once the project succeeds, the role follows. This is how family governance and delegation can work together instead of against each other.
How Delegation Affects Supplier Development
Supplier development is one of the most under-delegated functions in Indian SMEs. The owner keeps all vendor relationships because the owner knows the vendor’s father, the vendor’s payment terms, and the vendor’s delivery habits. This is valuable knowledge. But it is also a bottleneck. When the owner is the only one who can call a vendor, supplier development stops when the owner is busy. A Rajkot auto-component unit solved this by creating a vendor scorecard. The owner and the purchase team listed the top ten vendors with ratings for quality, delivery, price, and response. Then the owner delegated routine follow-up calls to the purchase executive. The owner only calls vendors for rate negotiation or serious delivery failures. The purchase executive now owns the weekly follow-up and updates the scorecard every Friday. The owner reviews the scorecard on Saturday. Supplier development improved because someone was actually watching the vendors every week, not just when a shortage happened.
In Coimbatore and Ahmedabad, many units have the same pattern with customer service. The owner handles every customer call, every complaint, every schedule change. Delegating customer service means creating a simple communication log: who called, what they asked, what we promised, what we did. The customer service person can handle routine updates and first-level complaints. The owner steps in only for pricing, major quality disputes, or new orders. This frees the owner for new business development, which is the real owner-only job in most units.
Tools That Help Without Adding Complexity
You do not need expensive software to delegate. A whiteboard, a register, and a daily huddle are enough for most units under 100 workers. In a Faridabad metal fabrication unit, the owner uses a simple A3 sheet on the wall near the dispatch gate. It has four columns: today’s jobs, machine assigned, operator, and status. The shift supervisor updates it every two hours. The owner walks past it three times a day. That is delegation with visibility. No software, no login, no training.
For units that want a little more structure, a shared spreadsheet or a WhatsApp group with a daily update format works. The format matters more than the tool. A good daily update has three lines: what was planned today, what was done, what is blocked. The supervisor sends it at the end of the shift. The owner reads it in two minutes. If something is blocked, the owner acts. If nothing is blocked, the owner stays out. That is the whole system.
Common Excuses and What They Actually Mean
“My workers are not ready.” This usually means you have not trained them. Training is your job. It is not a cost. It is the price of getting your time back.
“They will make mistakes.” Yes. They will. Your job is to make the mistakes small and the learning fast. A mistake in a delegated task with a clear boundary is a training expense. A mistake made by you because you were overloaded is a business loss. Choose the smaller one.
“Customers only trust me.” Customers trust the unit, not just the person. If you are the only face, the customer will call you for everything. Introduce your second line to the customer. Take the supervisor or engineer to the customer visit. Let them answer one or two questions. Over time, the customer learns that the unit has depth. That is a selling point, not a weakness.
“I don’t have time to train.” You don’t have time not to. Every hour you spend training a person to do a task that you currently do five times a week is an hour that pays back within a month. The math is simple. The discipline is hard.
Delegation as a Capacity Decision, Not a Personality Decision
In the end, delegation is a capacity decision. Your unit’s capacity is not just machines and workers. It is the number of decisions that can be made per day without you. If that number is low, your unit is a job shop with an owner inside. If that number is high, your unit is a company with an owner on top. The difference is not the size of the shed. It is the number of people who can decide within a boundary and report after.
Start small. Pick one task this week. Write the boundary. Train one person. Set a review rhythm. Then do it again next week. In six months, you will have a different unit. Not because you hired more people. Because you finally let the people you already have do the work they are paid for.
Frequently Asked Questions
How do I know which task to delegate first?
Pick a task that is frequent, visible, and has a clear pass/fail outcome. Daily production reporting, purchase approvals below a set limit, first-piece inspection sign-off, or vendor delivery follow-up are good starting points. Avoid starting with complex tasks like pricing or new product development.
What is the difference between delegation and abdication?
Delegation transfers a task with a clear outcome, a boundary, and a review rhythm. Abdication dumps the task without any of these. If you tell someone “you handle dispatch” without defining what good dispatch looks like, how often you will check, and what limits they have, you have abdicated. That usually fails and then you blame the person.
How do I build trust in my second line without risking customer orders?
Build trust through small projects with clear measures. Give a supervisor or engineer a specific project: reduce rejection in one section by a set percentage, or bring two new vendors with a cost saving target. A project has a clear end and a natural review point. Once the project succeeds, the role follows. This builds trust without handing over a permanent function too early.
What should I do when a delegated task goes wrong?
Do not withdraw the authority immediately. Ask three questions: What exactly went wrong? Was the boundary unclear? Was the training incomplete? Then fix the boundary or the training. If the person acted within the boundary and the boundary was too loose, tighten the boundary. If the training was incomplete, retrain. Only withdraw authority if the person repeatedly ignores the boundary after clear correction.
Can delegation work in a family-run SME where the next generation is involved?
Yes, but it needs more structure, not less. Give the next generation a project with a clear measure and a review point, not a permanent role from day one. This builds trust gradually and avoids the emotional fallout when expectations are too high too soon. The project approach works well for vendor development, quality improvement, or a specific cost-reduction goal.


















