Why Your First Operations Leader Can't Hold Anyone Accountable in Year One

A founder hires their first real operations leader, a Director of Operations, a Head of Ops, sometimes a first COO, and expects what most founders expect: someone to take the operating mess off their desk. The sales lead who will not commit to a forecast and the two tenured people who have been at each other all year, plus a leadership meeting that only happens when the founder remembers to call it. The title goes on the org chart, and everyone, founder included, assumes accountability came with it.

Usually it did not, or not for a long while, and the reason isn't that the founder hired the wrong person. You see, a title and standing with a leadership team come from different places and tenures. The title is LIVE on the start date. But standing, that has to be earned, and it can take quarters, and being careful about who you hire does not shorten that. I've watched good operators grind through a hard first year learning this, and I have watched founders decide they made a bad hire when the real problem was that everybody assumed that as soon as a body was in the chair, that everything was golden... set up for success!

The Hiring-Problem Assumption

The default plan is some version of "hire someone good and let them grow into the role." It sounds reasonable on paper but it also leaves the accountability gap open for a year or more while everyone believes it is covered. Things are getting done, but mostly process and less so the people to pair with that process.

The statistic everyone quotes on this topic is that 40 percent of executives fail within 18 months. This is commonly cited as settled fact... It is not. That number traces back to a 2009 Financial Times interview in which the head of an executive search firm referred to an unpublished internal study. No methodology was ever released, there was no definition of what counted as failure, and the firm sold onboarding services, so it had an interest in a scary number. Nobody has sourced it properly since. I bring it up because founders treat the underlying problem about as carelessly as the field treats that number. A big figure gets passed around and nobody looks at what is actually going on.

There are better numbers out there. DDI's 2021 research on leadership transitions, which covered more than 15,000 leaders, found that 35 percent of internally promoted executives were judged failures, compared with 47 percent of external hires. That 12-point gap between promoting from inside and hiring from outside is the telling part, and it supports what founders actually miss.

Why Standing Does Not Transfer With the Title

The clearest explanation I know is decently old. In 1959 the social psychologists John French and Bertram Raven laid out the different bases of power a person can hold, and two of them I want to focus on. First: Legitimate power comes from your position. The org chart hands it to you the day you start. Second: Expert power and referent power are different. They come from competence people have watched you demonstrate and from relationships and trust you have built, and nobody can assign them. A founder can give a new leader legitimate power on day one. The other two get earned in front of the team, and teams hand them out slowly, after watching for a while.

How slowly is also helpful to know, and that best evidence on it comes from a 2011 study by Matthew Bidwell at Wharton, published in Administrative Science Quarterly. Using detailed personnel records, he found that external hires were paid about 18 percent more than people promoted into the same jobs, came in with more experience and more education, and still performed worse for their first two years. They also left at higher rates. The people promoted from inside did better early on for an unsurprising reason: they already had the relationships and the context the outsider had to build from nothing. Bidwell's data comes from one industry, so I would focus less on the exact percentages, but the pattern matches the rest of the evidence and it matches what most operators have seen up close. The outsider spends the first stretch learning things the insiders already knew, and the team is watching that happen.

This is the part founders discount. When the new leader tells a tenured salesperson to change how they forecast, the salesperson hears the instruction and then asks a second question: does this person have the standing to give it. The new leader has not built that standing yet. The org chart says they can give the order. The people receiving it have not agreed to that.

The Peer Problem Makes It Worse

It gets harder when the people who need to be held accountable have been there longer than the new leader, or were their peers until last month, or have a direct line to the founder. Managing former peers is so common that most of the advice on it takes the situation for granted: earn credibility first and reach for authority second, because pulling rank early spends that standing the new leader does not have. A new operations leader who tries to hold the founder's ten-year right hand accountable in month two is spending credit they have not earned, and the rest of the team can see that.

The Comp Problem Nobody Adjusts

There is a second reason accountability stalls, and it has less to do with credibility. People are asked to lead but paid to produce.

In 1975 Steven Kerr published a paper called "On the Folly of Rewarding A, While Hoping for B," and the title is pretty telling of most of the argument. Organizations pay for one behavior, hope for a different one, and then act surprised when they get the one they paid for. It is one of the most predictable failures in management and it shows up around new operations leaders constantly. A founder asks a senior person to start managing, to hold others accountable and think about the business as a whole, and keeps paying that person entirely on their own output. The person does the math and keeps working their own number, because the check rewards the number. The founder asked for management and paid for production, so production is what they got.

If the new leader is supposed to hold a team accountable while the team's pay makes cooperating with that leader a personal financial loss, the pay plan is going to win that fight.

The Hardest Case: Professional-Services Partnerships

Everything above applies to any founder-led company. It is worst in professional-services partnerships, law firms, accounting firms, medical groups, engineering and architecture practices, because there the people the new manager is supposed to hold accountable own the place.

A firm hires a capable administrator or a non-owner COO, gives them a real title and a slot on the org chart, and expects them to bring some order to how the partners operate. The structure will not allow it. The management literature for firm administrators is consistent on this: the non-owner runs the business side and reports to the managing partner or a committee, and holding partners accountable stays with the owners. A non-owner cannot hold an owner accountable when the owner is, in the end, one of the people the non-owner answers to. The authority points the wrong direction.

Compensation makes it worse in exactly the way Kerr described. In an "eat what you kill" partnership, partners are paid on origination and on their own production, and the money is significant. Recent survey data put the median origination value for equity partners above a million dollars. Running the firm and mentoring associates pay nothing comparable, and they usually cost a partner billable time on their own book. So an administrator who is asked to get the partners operating as a team is pushing directly against a pay system that rewards each partner for doing the opposite.

Medicine adds a legal/regulatory layer. In many states, corporate-practice-of-medicine rules require that physicians keep authority over clinical decisions, which limits what a non-physician administrator can direct when the people being directed are physician-owners. The practice-management literature notes that groups who bring in a practice administrator without physician-level leadership behind them are usually disappointed, because the administrator has no way to direct owners who never actually gave up the authority. The role is set up to fail before the person starts.

The practitioner vocabulary most founders know for the healthy version of this split comes from the book Rocket Fuel, which pairs a Visionary who owns direction with an Integrator who owns execution and accountability. It is a good description of the division of labor, and I mention it because a lot of founders and partners have read it. It comes out of practice rather than research, and the limit is the same one: if the owners have not actually handed over authority, no title given to a non-owner will manufacture it.

What Actually Closes the Gap

So if accountability does not come with the title, it has to come from somewhere, and the list is short and fairly dull. Most of it falls on the founder rather than the new hire.

Explicit sponsorship from the founder

The most consistent finding in the change-management research is about sponsorship. Prosci has been running benchmarking studies for more than twenty years, and in every one of them, active and visible support from the senior leader comes out as the top predictor of whether a change succeeds, cited more than three times as often as whatever comes second. In the same body of work, initiatives with highly effective sponsors met their objectives 79 percent of the time, and initiatives with poor sponsors met them 27 percent of the time. For a new operations leader, that means the founder (or a surrogate) cannot make the hire and then step back. The founder has to be seen backing that person's authority, over and over, in front of the team, because the team reads silence correctly and will wait the new person out. In practice sponsorship is the founder routing decisions through the new leader instead of around them, and doing it long enough that everyone stops testing whether it will hold.

Decision rights in writing, not implied

Most founders leave the new leader's actual authority implied, and anything implied is, inevitably, contested. What can this person decide on their own, and what stays with the founder? Where do the two decide together? Writing the answers down keeps every decision from becoming a new argument about whether it was the new leader's to make. Bain's research across hundreds of companies found that how well a company makes decisions correlates strongly with its financial results, and the peer-reviewed work on role clarity points the same way, with role ambiguity reliably tied to lower performance. Written decision rights also settle the other common problem, which is a team member going around the new leader straight to the founder. When the rights are written, the founder can point to the page.

A scope they genuinely own from day one

"Grow into the role over the first year" is the plan that keeps the gap open. The more successful alternative is to give the new leader a bounded piece of the business they own completely from the start, even if it is smaller than the job they were hired for. Owning something narrow outright builds standing faster than holding nominal authority over everything, because the team gets to watch the person decide and deliver inside clearly drawn lines. That is how expert and referent power get built.

Compensation that pays for the behavior you are asking for

If you want someone to lead, some of their pay has to depend on how the leading goes, and not only on what they produce themselves. That applies to the new operations leader, and it applies just as much to the senior people you are asking to fall in line behind them.

Someone senior holding the hard line in the interim

This is the piece founders most want to skip, and it is the one that decides whether the first year is survivable. Someone has to make the costly calls early, the reassignments and the removals that spend goodwill, before the new leader has the standing to make them without damaging their own position for good. A new leader who does the hard thing in month two pays for it for the rest of their time there, looked at like a butcher. So someone who already has standing, the founder, a board member, or a seasoned interim leader, has to hold that line while the new person earns theirs. The person holding it can be anyone the team already accepts as having the authority to do it; an outsider is one option among several.

The Sequencing Problem

None of this is an argument against hiring a full-time operations leader. That hire is usually right and eventually unavoidable. The argument is about order. The common plan puts the person in the seat and hopes accountability builds on its own gradually over time, and it treats the first year as a ramp when the first year is the most fragile stretch of the whole tenure and the one where the most goes wrong. The founders who do well are the ones who close the gap on purpose, with sponsorship, written authority, a scope the person really owns, pay that matches the ask. But most importantly bringing in someone senior other than that individual inheriting the seat that can hold the hard line, instead of throwing that person into the deep end and assuming the title alone will do all that heavy lifting.

The Boat

When a founder asks me why they should bring in someone part-time instead of just hiring the ops leader they know they need, this is what I tell them.

You own the boat. You decide where it is going, and none of that changes. What I am doing is getting the vessel ready for the person who is going to run it day to day, and then handing them the helm.

Some of that work is the obvious kind. We find out whether the hull is actually sound. We stock what this trip requires instead of what somebody guessed at two years ago. We get out of the dock and onto a heading, so the new captain inherits a boat that is already moving rather than one still tied up with a list of unanswered questions.

The part that matters more is the crew. A vessel can be seaworthy and well provisioned and still come apart the first time a captain nobody picked starts giving orders. So part of readiness is establishing, while I am still aboard, that the helm gives orders and the crew follows them. That is how the ship runs, rather than something the captain has to win personally by being likable enough. When they step aboard, there is already a working chain of command instead of one they have to build from nothing against people who have been here a lot longer than they have.

Somebody has to make the calls that cost you goodwill, whether that is reassigning a watch or letting go of a person who is not working out. If your new ops leader does that in month two, they spend the rest of their tenure paying for it. If I do it, I take the hit and then I am gone. Your captain arrives without an enemy in the building.

Sometimes I am training that captain directly and the handoff happens gradually. Once they have the helm I am usually still around for occasional check-ins while they find their footing, but the boat is theirs at that point.

FAQ

Why can't a new COO or head of operations hold people accountable right away?

Because the title arrives on day one but the standing to use it does not. French and Raven called the first kind legitimate power, granted by position; the kind that makes a team actually follow someone is expert and referent power, earned over time through demonstrated competence and relationships. Research on external hires shows them underperforming internal promotions for roughly two years while they build what a title cannot grant.

How long does it take a new operations leader to become effective?

There is no precise, well-validated figure, and anyone quoting one exactly is guessing. The credible proxies land in quarters rather than weeks: peer-reviewed data shows external hires taking around two years to match internal performers, and practitioner research puts a mid-level leader's break-even at roughly six months. Plan for a first year that is fragile rather than fully productive.

Is a failed operations hire usually a bad hire?

Often not. Studies of why new hires fail consistently find most failures coming from relational and cultural factors rather than a lack of technical skill. A capable person can fail in the seat because the conditions around them, sponsorship, decision rights, scope, and compensation, were never set up to let their authority stick.

What is the single most important thing a founder can do?

Sponsor the new leader, visibly and for longer than feels necessary. The change-management research is unusually consistent that engaged senior sponsorship is the top predictor of success by a wide margin. In practice the founder is seen, again and again, routing decisions through the new leader instead of around them, well past the point of announcing the hire.

Why is this harder in a law firm, accounting firm, or medical group?

Because the people who must be held accountable are the owners, and a non-owner manager cannot truly hold an owner accountable. The reporting line points back to the partners, compensation formulas reward individual production over firm cooperation, and in medicine, corporate-practice-of-medicine laws limit a non-physician's authority over physician-owners. Accountability of owners has to come from owner-level governance, which an administrator's title cannot substitute for.

Should I just hire a full-time operations leader or not?

Usually yes, in time. The trouble is the assumption that accountability arrives bundled with the hire. Founders who succeed close the gap deliberately during the first year, with sponsorship, written decision rights, a genuinely owned scope, aligned compensation, and someone senior holding the hardest calls until the new leader has earned the standing to make them.