← Guides Guide · Leadership

Hiring Senior Leaders Without Losing Control

By Stan Tscherenkow · Published September 2025 · 10 min read

Quick Answers

Why do senior hires fail? Most senior hire failures are structural, not performance-related. The pattern has three stages. Stage one: the hire is made against an outcome (the founder is overwhelmed, a senior leader is hired for relief), not against a defined role. Stage two: the new leader and the existing organization spend three to six months figuring out the actual role boundaries, which creates confusion and friction. Stage three: the founder re-inserts themselves to resolve the friction, the new leader's authority becomes visibly conditional, and they either leave or stop making decisions independently. The failure was not caused by the wrong person. It was caused by a role that was defined by what the founder wanted to stop doing, not by what the organization actually needed, with authority structured to match.

How do you define the role before you define the person? Three things must be specific before any candidate search begins. Domain boundaries: what this role is responsible for and where its responsibility ends. If the role is responsible for revenue but not for the pricing decisions that determine revenue, the role is not functional. Decision authority: which decisions this role makes unilaterally, which require approval, which are advisory only. Written down before the hire, not clarified afterward through conflict. Success definition: what success looks like at 90 days, 12 months, and 24 months. Specific outcomes, not activity.

What is the company-size mismatch problem in senior hires? The most predictable senior hire failure in founder-led companies is hiring a leader from a significantly larger organization into a role that requires a different operating mode. In a $500M company, a VP of Operations manages systems that other people built. In a $15M company, a VP of Operations builds the systems while simultaneously running operations. These are structurally different work. The interview must test for operating mode, not just experience: ask about building something from scratch with no existing infrastructure, about leading small teams where the person also did execution work, about solving a process problem without budget.

What do the first ninety days require? More founder involvement, not less. Having hired specifically to reduce their own involvement, most founders reduce involvement immediately. That is a mistake. The first ninety days require more founder involvement for context transfer, even while stepping back from decisions. Weekly 1:1s focused on context, not status. At least three joint decision situations where the founder demonstrates their approach then steps back. Explicit introduction to the three or four relationships in the organization that will determine whether the new leader is accepted. And one meaningful decision in the new leader's domain that the founder visibly defers to, a public signal that the authority is real.

Hiring a senior leader is one of the highest-leverage decisions a founder makes. And one of the most reliably botched. The failure mode is rarely about competence. It is about what was left undefined when the hire was made.

Why senior hires fail, the real pattern

Over a twelve-year period working across boards and operating situations, I observed the same senior hire failure pattern repeat more often than any other single leadership problem. The pattern has three stages.

Stage one: the hire is made against an outcome, not a role. The founder is overwhelmed and needs relief. A senior leader is hired to provide it. The outcome, less founder involvement in day-to-day, is clear. The role that produces it is not.

Stage two: the new leader and the existing organization spend three to six months figuring out the actual role boundaries. This creates confusion, slows decisions, and produces friction between the new leader and people who have been in the company longer. The founder attributes this to "culture fit" or "personality."

Stage three: the founder re-inserts themselves to resolve the friction. The new leader interprets this as undermining. Their authority is now visibly conditional. They either leave or stop making decisions independently. The hire has failed, even if the person is still employed.

The consistent finding: the failure was not caused by the wrong person. In most cases the person was genuinely capable. It was caused by a role that was defined by what the founder wanted to stop doing. Not by what the organization actually needed, with authority structured to match. The documented case sits in when hiring a senior executive backfires.

Defining the role before you define the person

Most hiring processes begin with a person in mind. A profile, a background type, a set of experiences. The role should be defined first, with specificity about three things before any candidate search begins.

Three definitions required before the search begins

Domain boundaries. What is this role responsible for, and where does its responsibility end? The boundaries matter as much as the content. If the role is responsible for revenue but not for the pricing decisions that determine revenue, the role is not functional.
Decision authority. Which decisions does this role make unilaterally, which require approval, and which are advisory only? This must be written down before the hire is made. Not clarified afterward through conflict.
Success definition. What does success look like at 90 days, 12 months, and 24 months? Specific outcomes, not activity. A senior hire who is told they are succeeding based on effort has no basis for self-correction when they are not.

The most predictable senior hire failure in founder-led companies is hiring a leader from a significantly larger organization into a role that requires a different operating mode. In a $500M company, a VP of Operations manages systems that other people built. They optimize, govern, and scale. In a $15M company, a VP of Operations builds the systems while simultaneously running operations. These are not versions of the same job. They are structurally different work requiring different capabilities.

The resume looks right. The background is relevant. The problem is the operating context, which the resume does not describe.

This does not mean you should not hire from larger companies. It means the interview process must test for operating mode, not just experience. Specific questions that reveal this: Describe the last time you built something from scratch, a process, a team, a system, with no existing infrastructure to work from. What did that look like day-to-day? What is the smallest team you have led where you were also the person doing a meaningful portion of the execution work? And: when a process you were responsible for was not working and the budget to fix it was unavailable, what did you do?

Structuring authority at point of hire

Authority structure must be agreed at hire. Not derived from experience, not assumed from title, not clarified later through conflict. The conversation is uncomfortable to have explicitly. It is less uncomfortable than the alternative. The related framework on authority structures themselves lives in leadership authority structures.

Four things to document at point of hire

Authority matrix. Decision categories, who decides, who approves, and where escalation goes. One page. Signed by both parties.
Retained decisions. The specific decisions the founder is explicitly retaining. Capital above a threshold, key hires, strategic pivots. Everything else is transferred.
Review cadence. When and how authority will be reviewed. Typically at 90 days and 12 months. Authority can expand. The mechanism for that expansion should be agreed in advance.
Success definition. The 90-day, 12-month, 24-month outcomes that were used in the hiring decision. Written down so both parties can track against them.

The first ninety days and what to do when it is not working

The first ninety days of a senior hire determine whether the hire takes root. Most founders are not present enough in this period. Having hired specifically to reduce their own involvement, they reduce involvement immediately.

The first ninety days require more founder involvement, not less. Not in decisions. In context. The new leader needs to understand the organizational history that is not written anywhere. The relationships that matter. The decisions that were made and why. The things that were tried and failed. None of this is in the onboarding documentation.

Specifically in the first ninety days: weekly 1:1s with the founder focused on context transfer, not status reporting. At least three joint decision situations where the founder demonstrates how they approach decisions in the new leader's domain, then steps back. Explicit introduction to the three or four relationships in the organization that will determine whether the new leader is accepted or resisted. And one meaningful decision in the new leader's domain that the founder visibly defers to. A public signal that the authority is real.

The signal that a senior hire is failing is almost never performance data. It is organizational behavior. People start routing around the new leader. Decisions that should go through them come directly to the founder. The new leader becomes more cautious, not less, as time passes. Conflict with peers increases. When these signals appear, the diagnostic is structural before it is personal: Is the authority structure functioning as designed, or is it being regularly overridden? Are the role boundaries clear enough that the new leader knows what they are supposed to be deciding? Is the founder's behavior reinforcing or undermining the authority that was formally granted?

If the structural diagnosis clears and the problem is genuinely the person, then the decision is simple. Though not easy. The related guide sits in should I fire a senior leader. But starting with the structure prevents the common error of replacing a capable person whose role was never actually designed to succeed.

Stan Tscherenkow Private Business Advisor Two decades operating across Europe, Russia, Asia, and the United States.

About Stan →