When the Hiring Plan Is the Actual Problem
Many founders who think they have a hiring problem actually have a design problem in how the business is run. Telling the two apart late can cost Rs. 40L to Rs. 80L in senior hires that don't work out before anyone names the real cause.
I've seen this often enough that I stopped treating it as an exception.
A founder at Rs. 30 Cr to Rs. 60 Cr in revenue spots an operations breakdown. Execution is slow, the founder is in every decision, and the team keeps growing while output per person falls. The diagnosis the founder reaches is "we need a strong operational leader".
So the firm hires a COO, a Head of Operations or a Business GM. The hire looks good on paper and does well in the first month, and then, over the following months, the same problems come back. Decisions still go to the founder and handoffs still break. The new leader proves useful for narrow, defined tasks but never owns the function from end to end, and 18 months later the founder is saying "we need a stronger hire" all over again.
The Question Founders Skip
Founders usually ask whether they hired the right person. The question that matters more is what operating model they hired that person into.
Most founder-led businesses at the Rs. 20 Cr to Rs. 80 Cr stage run on operating models built for one person. The founder made the model work through informal ownership, closeness to every decision and the ability to pull together context nobody else had, and the business grew around that setup. A new leader hired into that model is asked to perform inside a structure nobody designed for them. Accountability is informal, decision rights are never said out loud and the founder's presence is built into every handoff, so the hire spends their energy coping instead of succeeding.
The Signals
The signals look much the same from one business to the next:
• Senior hires take three to five months to become useful, then leave within twelve to eighteen months
• Decisions that belong with the function still go back to the founder
• Handoffs between teams break at the same points, whoever is in the role
• New leaders become expensive execution support instead of owning their function
• The team grows, but the founder's operational load doesn't shrink
These signals come from design, so changing the people doesn't remove them. The operating model has a structural gap, and the firm is using the hire to cover it up.
The Misdiagnosis
The misdiagnosis is nearly always about calibre. The founder concludes that the firm needs someone stronger, more experienced and more senior, so it pays more, and the same pattern repeats. A more senior hire walks into the same invisible wall, because the wall is built into the structure and doesn't care how much the hire costs.
The Structural Truth
When the structure is mapped, it usually shows three things:
• Decisions stall at the founder because there's no agreed escalation path for anything above a certain size or complexity.
• Handoffs between functions break because the operating logic between them was never written down; it lived in the founder's head.
• Senior hires can't own work end to end because nobody ever formally handed ownership over; everyone just assumed it had moved.
Those are problems of architecture, and architecture problems need architectural fixes rather than different people.
Structural Clarity Before Headcount
Before the next senior hire, the founder should map where decisions actually stall in the business today, as opposed to where the founder would like them to sit. The map should also show who informally owns what, and which work can't move without the founder present. It will point to one of two things:
- The role the founder wants to hire for has a clear space to operate in, in which case the firm should hire.
- The role has no real ownership to sit in, in which case the firm should define the ownership first and then hire.
At this stage it's usually the second. The right hire in a well-designed model costs less, gets up to speed faster and stays longer, because that person can own something real and doesn't have to invent their own operating context every morning. That's why I'd put structural clarity before headcount every time.
Principle
The businesses that scale well build the structure first and then hire people into something real, instead of hiring first and sorting out the structure later. The right person dropped into a broken model doesn't fix the model, and usually becomes its next casualty.
Take the Mini Diagnostic → get your Structural Health Score. Free at metmov.com