Why Execution Breaks Down at Scale

You said it in the Monday meeting and you meant it. Nobody here owns anything end to end any more.

The evidence was in front of you. A ₹42 lakh order that shipped eleven days late because the customer's revised drawing reached the plant after cutting had started. An invoice unraised for three weeks because the delivery challan came back unsigned and nobody chased it. A customer who called your personal number on Sunday because his mail from Friday had not been answered.

Three failures, three departments. Now look at what each one did. Sales received the revised drawing and filed it. Production ran the job it had been released. Accounts does not raise an invoice against an unsigned challan, correctly, because that is what the audit requires. Nobody did anything wrong inside their own boundary.

That is not luck. Execution almost never breaks inside a team. It breaks between them — for a reason that has nothing to do with the calibre of your people. A handoff is the one place in a company where ownership is ambiguous by default.

Inside a team there is a manager and a standard. Somebody's name is on the output and somebody senior looks at it. At a handoff there is neither. A gap sits between two owners, and the gap has no owner unless someone deliberately assigned one. Nobody ever does, because at twenty people nobody needs to.

This is the five conditions of ownership failing in their most specific form. At a handoff the first condition fails outright: no standard exists for the gap, because no owner exists to hold one.

Growth does not cause this. It reveals it.

The handoffs in your business have always existed. What changed is who was covering them.

At twenty people you were the connective tissue. You were in every WhatsApp group. You heard about the drawing revision because the sales fellow mentioned it while you were both standing near the machine. You noticed the challan had not come back because you signed the payment run yourself. You did this hundreds of times a year without calling it work, and because you did it, no gap was ever visible.

At eighty people you cannot. Not because you have become distant, but because handoffs do not grow in line with headcount. They grow with the number of pairs of people who must coordinate, which grows far faster. Nine departments across three shifts produce more seams than you could cover if you did nothing else.

So every gap that was invisible becomes a dropped ball. And because they drop in different places each week, with different names attached, the pattern you perceive is not our handoffs are unowned. It is the team has stopped taking ownership.

In Indian businesses this shows up in a narrow band, roughly 40 to 120 people. The trigger is not a headcount, it is the week you stop being in every WhatsApp group that matters. Some promoters hit it at 35 across three locations, some hold on until 150 in one plant. The symptoms are identical: more escalations, later escalations, more meetings, and a private suspicion that the second line you hired is weaker than the first. It is usually the moment a business notices its growth has flattened for no visible reason.

Gallup's India engagement series ran at 26% in 2021, rose to 33% in 2022, then fell to 30% in 2024 and 23% in 2025 — a decline across the years in which a great many Indian mid-market businesses added their second and third layer of management. That proves nothing on its own. But it should make you slower to conclude that the people you hired while growing were worse than the ones you started with.

The Handoff Map

The Handoff Map takes about ninety minutes with the right four people in the room. It works because it forces you to write a column you have never written before.

Take one real flow and follow it concretely. Not a value chain diagram. One order. Order to cash is the best start, because it crosses the most boundaries and its failures are financially visible.

Walk the flow and mark every point where work changes hands

For a typical Indian B2B manufacturer, enquiry to cash changes hands something like this: enquiry to inside sales; inside sales to the field salesperson; salesperson to costing and back; salesperson to production planning once the PO lands; planning to purchase; purchase to the vendor; vendor to stores and incoming quality; stores to production; production to quality; quality to dispatch; dispatch to the transporter with the e-way bill; transporter to the customer's stores; signed challan and GRN back to your commercial team; commercial to accounts for invoicing; accounts to collections. And at any point in all of that, the customer to whoever picks up the phone.

Sixteen changes of hand for one order. Write them out for your own business; the number is always higher than the org chart suggests, because the chart shows boxes and the work moves along the lines between them.

For each one, name three things

Against every handoff, write who owns the work before, who owns it after, and who owns the gap.

The first two are easy; everyone answers quickly and agrees. The third column is where the room goes quiet.

Who owns the drawing revision between the moment sales receives it and the moment planning acknowledges it? Not sales, whose job was to receive it. Not planning, who cannot acknowledge what they have not been sent. There is a window of six hours or three days in which that revision belongs to nobody, and almost everything that goes wrong in your business goes wrong inside windows like that one.

How to test it this week: take the last four things that went badly wrong, the ones that reached you personally. For each, ask one question: did this fail inside a department's work, or in the space between two? Do not accept "communication gap"; make someone name the exact moment the work was in nobody's hands. Four out of four will land in the gap column. If one lands inside a team, treat it as the different problem it is.

The four handoffs that break first

Every business has its own map, but four seams fail first.

Sales to operations

The promise made to win the order that operations never agreed to.

The salesperson commits a delivery date standing in the customer's office, because the competitor quoted three weeks and the deal is closing now. Nobody in planning was asked. The commitment enters the business as a fact, and operations discovers it when the PO arrives. From that moment there are two dates — the customer's and the plant's — and neither department owns reconciling them.

The tell is the phrase "we somehow managed it," said with pride. Each time you hear it, a gap was closed by somebody's overtime rather than by a process. It will not close next time.

Operations to finance

The invoice that cannot be raised because the paperwork is incomplete.

Material went out. Value was delivered. But the challan came back unsigned, or the PO number was one digit off, or the GRN has not been posted in the customer's portal, so the invoice sits. Accounts is not wrong to hold it. Dispatch is not wrong to consider its work finished when the truck left. In between sits your working capital, with nobody's name on it. This is how a business with a healthy order book ends up with a cash problem nobody can explain.

The escalation that arrives outside anyone's hours

A customer's line stops on Saturday afternoon. Your service head is at a wedding. The plant WhatsApp group has forty people in it, so the message is seen by everyone and owned by no one. By Monday the customer has called your personal number, which teaches him that calling your personal number works. The habit is now permanent.

Defined hours create an undefined remainder, and the remainder is a handoff too. It needs a named owner like every other one.

Anything involving a vendor or a third party

Here the gap sits outside the company entirely, invisible to every internal review you run.

The job-work vendor has your material and has not confirmed a date. The customs broker is waiting for a document he asked for by phone. Your purchase executive believes he has followed up, because he sent a WhatsApp message. The vendor believes he is waiting for you. Nothing moves for nine days, and no meeting in your calendar would surface it, because your meetings review departments and this sits inside none.

Why writing more process does not fix it

Here is why the SOP project did not work.

An SOP describes the work inside a box. It tells production how to run the job and accounts how to raise the invoice. It is written by the person who owns the box, reviewed by the person who owns the box, and it is usually quite good.

The failures are between the boxes, which is exactly what an SOP does not cover, because no box owner has authority outside his box. So you write more process, execution does not improve, and the conclusion you draw — that the team does not follow process — is wrong. They followed it. It had a hole in the shape of the problem.

Your review meetings have the same defect: organised by department, and so unable to surface a failure that belongs to no department. That mechanism is in why meetings don't produce decisions, and its cousin — building reporting when what you wanted was ownership — in the accountability gap.

The repair: assign the gap

The fix is unglamorous, and small enough to do this month.

Every handoff on your map gets a named owner of the transition — not of the two sides, of the crossing itself — plus one observable signal that the handoff completed.

The signal matters more than the owner. Compare these two.

• Sales informs operations of any change in customer requirement. This is what your SOP says today. Nothing is observable, so nobody can be shown to have failed, so the gap stays unowned.
• Sales uploads the revised drawing to the order folder and planning confirms receipt in writing within four hours; if no confirmation by then, the plant head is notified. This is a working handoff. There is an artefact, a clock, a named confirmer and a defined failure path.

Apply the test everywhere. "Dispatch ensures documents are collected" becomes "signed challan scanned to the order record within 48 hours, commercial confirms." "Service responds promptly" becomes "messages outside working hours are acknowledged within two hours by the person named on the weekend roster."

Two things make this hold. The transition owner needs authority to act at it — to hold a dispatch, to escalate over a department head's objection — which means writing down authority that currently lives in your judgement alone, the work described in the decision bottleneck. And the people who should run these seams are your middle layer; if that layer only relays information, no handoff you design will survive. That diagnosis is in why middle management fails.

Start with three handoffs, not sixteen — the three behind your last four escalations.

When it really is a headcount problem

Sometimes structure is not the answer, and it would be dishonest to pretend otherwise.

If you map a flow and find one person named as owner of nine transitions across four departments, no signal design saves that. You have not found an ownership problem, you have found a missing role. In Indian businesses crossing roughly ₹25 crore it is usually a production planning function that has never existed as a job, a commercial role between sales and the plant, or a real second line under a department head still doing his own follow-ups.

The question is simple. If every handoff had a clear owner and a clear signal, would there be enough hours in the day for the named people to do it? If yes, it is structure. If no, it is a role, and every process you write instead of hiring is a delay you pay for in dropped orders. Businesses stuck between ₹10 and ₹50 crore are often one unglamorous coordination role short.

Where to start

Map the flow that generates the most customer complaints, end to end, this week, with the four people who touch it. Add the third column. Leave the room with three handoffs that have a named transition owner and an observable signal with a clock on it.

Then wait a quarter and count your escalations. You are not looking for zero. You are looking for the ones that reach you to be new problems, rather than the same seam failing again under different names.

If you would rather see which seams are failing across the whole business first, the Business Pulse diagnostic maps where work actually changes hands in your organisation, and which of those crossings belong to nobody.