bottom

Why Does Everyone Quit This Role?

Home Office Video Call

“Every year, someone leaves this same position.”

One of my client’s employees said this to me soon after I started working with the company. They meant the founder’s second-in-command, who handled the day-to-day running of the business.

By then, the founder had been through the routine a few times and saw each departure as another hiring mistake. The job ad was tweaked and the interviews got a little tougher. Maybe a better candidate would finally break the cycle. 

I came in to help the latest second-in-command grow into the role. We tried, but things weren’t working out. When they left, I stepped into the job myself. Suddenly, I was sitting in the seat that nobody seemed able to stay in. 

What was this person supposed to accomplish? Which decisions could they make on their own? How would the founder know if they were doing a good job?

Nobody had ever agreed on what success in the role looked like or how to hold someone accountable for it. Yet, year after year, the founder had been making that judgment.

How do you know you’ve hired the wrong person when you haven’t agreed on what the right person is supposed to do?

Is It the Person or the Role?

The answer can go either way. At my client, part of it was the person: the owner came to see that the second-in-command who had carried the business to its current size wasn’t the leader to carry it further. Saying so out loud was kinder than another year of hoping.

Other times the role is the problem. When a founder tells me they can’t keep anyone in a role, I ask three things. How many times have you refilled it? What did the last few people say on the way out? How long did each new hire take to start repeating the previous person’s complaints? Two or three hires in a few years with the same exit story is a pattern pointing at the role.

To find out whether it’s the person or the role, make the expectations clear and watch what people do. Once the team knows the goals and how success is measured, anyone who likes having a plan and cares about the company’s purpose tends to settle in. Someone who enjoys the work but doesn’t share the values often decides to move on without anyone asking. If a person doesn’t change at all, you have your answer, and leadership has to address the performance.

Try a five-minute exercise before you read further. Write down why each of the last few people in the role left, then circle whatever repeats.

What Job Did They Accept, and What Job Did They End Up Doing?

A job description is a photograph of the company on the day someone wrote it. A year after the hire, the company has grown and the person in the role is doing work the posting never mentioned. I see a reasonable job turn into an impossible one in five ways:

  • Missing accountability is the most common cause I see. Either the person doesn’t hold themselves to results, or nobody holds them to results, and both versions look identical until a deadline passes.
  • Role expansion piles on responsibilities, and nobody adds the time, people or support to carry them.
  • Accountability without authority means the person owns the result and has to ask permission for every decision that would produce it.
  • Competing expectations pull the person in two directions. The founder tells them to lead on their own, then keeps jumping into the daily work and redoing their decisions.
  • Promotion without support happens when someone great at the work gets put in charge of the people doing it, and nobody helps them learn to manage. Sometimes nobody even asked whether they wanted the job.

At my client, the business ran on two schedules. When the founder was working in the business, the team dropped everything to push the founder’s priorities forward. When the founder stepped out, the regular scheduled work picked up again. The second-in-command had to manage both schedules.

Picture an operations manager hired to fix delivery processes and plan capacity. Six months in, her days go to calming upset clients and chasing late invoices, and she still needs the founder’s sign-off to move a single person onto a project. Her title hasn’t changed, and her job is unrecognizable. Before you replace her, sort out which of those tasks belong in her job and which need a clear process and owner of their own. The Operations Playbook shows how to set up processes and ownership for the work around her.

What Did the Last Few Departures Have in Common?

What you remember about each exit is your side of the story. Go back to the evidence: exit interviews, former employees who’ll still take your call, and the colleagues who worked beside each person. Then compare the departures side by side.

What to CompareQuestion to Ask
TimingDid problems start at the same point in each person’s tenure?
ResponsibilitiesWhich duties became hardest to carry?
AuthorityWhich decisions always needed someone else’s approval?
RelationshipsDid the same conflicts or communication problems come up?
SupportDid each person get the training, resources, and feedback they needed?
AccountabilityWas anyone holding them to clear goals and expectations?
How they got the roleDid they ask for it, or were they promoted into it for their skills?
Workload and payWas the scope realistic for one person, and paid accordingly?

People usually give the easiest reason on the way out: a better salary, a shorter commute, personal reasons. Any of those can be true. Ask what made each person start looking in the first place. A problem that comes up no matter who holds the job comes from the job.

The Founder’s Part in the Pattern

Founders often hold back tough feedback while someone is new, because they want to build trust first. A new person needs clear feedback early, while changing course is still cheap.

I see the same habits in the founders, CEOs, and managers I work with:

  • Asking a manager to decide, then reversing the decision
  • Giving instructions directly to the manager’s team
  • Changing priorities without revisiting deadlines or resources
  • Expecting a new hire to know preferences nobody wrote down
  • Stepping in every time a problem escalates, so the manager never builds judgment

Most of the time, a founder steps in because a client calls them directly when something goes wrong. Once they’re involved, they start worrying about how everything else is being handled.

When I start working with a new team, I see this a lot. A big client is unhappy, so they skip the account lead and call the founder. The founder wants to fix things fast, promises a new delivery date, and signs the team up for extra work. The account lead is still responsible for that client, but someone else made the promises. After the team and I have worked together for a while, this pattern stops.

If your team needs you to make all the decisions, you’ve accidentally trained dependence. Trained dependence starts with the founder, and it’s contagious. Once managers are empowered, they often repeat the habit with their own teams, so there’s a stretch where managers have to make room to teach and support their people, or they become the next bottleneck. If you took time off recently, your week away already ran the test for you.

When an Off-the-Shelf Framework Doesn’t Fit the Business

The founder hoped one of the well-known business operating systems would fix the role. Most of those systems expect the company to run on the same rhythm every week, and this one had two: everything stopped when the founder was in, and the regular work picked up again when the founder stepped out. That rhythm was part of the business and wasn’t going to change. So we built the second-in-command role around both schedules, founder weeks and all. Every tool I bring in, my own Strategy Alignment Framework included, has to bend to how the business works.

What Needs to Change Before You Refill the Position?

Sometimes, after a founder and I go through everything below, we decide not to hire at all. The real issue is a short-term capacity crunch, and a specialist brought in for a few months can build the systems and process that make the work easier to get done.

At my client, the founder’s one change was to stop managing the people directly. Once I took that over as second-in-command, the team had consistent accountability check-ins. I’ll let you in on a trade secret: a second-in-command doesn’t technically change anything. We share clear expectations, report on business performance, support people as they grow, and give feedback. We influence the change, and each team member decides whether to rise to the occasion.

Four decisions come before the job ad, and they improve life for the people already on your team as much as for the next hire.

Give the Role a Manageable Scope

Define what success looks like in the role, and who the ideal candidate is, before you write a word of the posting. Then run an operations triage on everything the role currently touches: what to keep, what to stop, what to start, and what to delegate or eliminate. The purpose of the business and the places where your team is stretched thin tell you what the role has to cover, and whether the job has grown too broad for one person. The 90-Day Ownership Test walks through the definition step by step, and its worksheet gives you a page to fill in before the role reopens.

Match Authority With Accountability

Decide which decisions the role makes alone, which need consultation, and which stay with you. Then build the rhythm that makes accountability ordinary. With my clients, the vision for the year, the goals, and the measures of success are clear by our first team planning session. Everyone on the team gets a growth plan that connects their individual goals to the company’s. We check in regularly, review progress monthly, and set new goals each quarter. You’ll know someone is in the right seat when they consistently do what the role expects, contribute to company goals, and show up every day modeling what the company is working toward.

Create the Support the Role Needs

Ask whether the person wants the role before you hand it to them. If you’re promoting someone for their skill, plan the support for the part of the job that’s new to them, which is managing people. Then check the basics: onboarding, access to information, working relationships, leadership coaching, feedback, and agreed expectations for communication.

Review Capacity and Compensation

Compare the workload, resources, seniority, and pay against what the role demands today. A role scoped for a company half your current size, at the pay to match, is an invitation to leave.

Before You Post the Job Again

What did the last few people in your hardest role tell you on the way out, and how much of it was the same?

A role with a season needs someone who stays long enough to fix it, and leaving the seat empty has costs of its own. During the hardest stretch with my client, I remember saying, “I don’t want to leave. I want to fix it.” So I stayed in the role, trained my replacement, and supported them until they were thriving. When they were thriving and still wanted me around, I knew it was time to go, because wanting me and needing me are different things. Before I left, I reviewed the hiring systems and triaged what to automate and delegate, so my replacement could lean into their own growth with confidence.

If your managers are learning to lead while the role settles, the Leadership Multiplier Playbook gives them a place to start. If you’d like someone holding the role while you fix it, see how fractional COO support works, or book a discovery call and tell me about the role nobody stays in.