How a 25-person business stopped rebuilding its management team and freed the founder from daily operations

The founder of this 25-person business had already hired managers.

That was not the problem.

The problem was that he kept having to hire them again.

Employees were joining the company at relatively junior levels, taking months to become useful, and then leaving. Managers were not removing the founder from day-to-day operations in any lasting way. Eventually, responsibility would drift back toward him, and he would once again find himself managing people, solving operational problems, and looking for the next person who could supposedly take those responsibilities away.

The company had employees. It had managers. It had processes.

But it still depended on the founder.

Over three working sessions, we began looking at the problem differently. Rather than asking, "Who should we hire next?", we asked a more important question:

What would have to change inside the operating system of the company so that the founder no longer needed to be part of that system every day?

That question changed the project.

The company did not have one hiring problem

At first, the situation could easily have been interpreted as a recruitment problem.

The business had a relatively young and junior team. People required significant training before they could operate independently, and turnover meant that much of this training investment had to be repeated.

A new employee could take roughly four months to move through the company's informal learning process.

That meant each hire was effectively a 16-week operational project.

The cost was not simply the employee's salary during that period. Experienced people inside the company had to answer questions, explain procedures, correct mistakes and repeatedly transfer knowledge.

When the employee eventually left, a large part of that investment disappeared with them.

The obvious response was to hire better people.

But that still did not explain why managers were failing to remove the founder from operations.

So we looked at the structure underneath the hiring.

One management role was actually two different jobs

One of the first problems we found was role ambiguity.

For example, the responsibilities assigned to the executive manager significantly overlapped with the responsibilities of the marketing manager.

On paper, the company had different positions.

In practice, two distinct functions were partially sitting inside the same definition of management.

That creates several problems.

An employee can perform well in one part of the role and poorly in another. Accountability becomes difficult because nobody knows exactly where one person's responsibility ends and another person's begins. And when an issue falls between the two positions, it usually travels upward.

In this business, "upward" meant the founder.

So the first intervention was not another hire.

We separated the jobs.

The executive manager received a clearly defined operating role. The marketing manager received a distinct marketing role. Responsibilities, decision authority and expected outcomes could now be attached to positions instead of personalities.

That sounds like a relatively small organizational change.

For the founder, it was fundamental.

Until the company could define what management actually meant, it could not reliably recruit, evaluate or replace a manager.

We stopped trying to hire the smartest possible person

The second problem was more subtle.

The company's hiring logic was optimized around finding strong candidates, but not necessarily candidates whose natural working style matched the position.

Those are not the same thing.

We redesigned the recruitment system so that each position had a more specific candidate profile.

Instead of simply looking for the person with the highest apparent intelligence or the strongest interview performance, candidates were evaluated against two role-specific dimensions: appropriate cognitive capability and an appropriate DISC profile for the job.

The important distinction was "appropriate."

A position did not automatically require the highest possible score on every dimension.

Someone can be highly capable and still be poorly suited to a repetitive, detail-oriented role. Another person may perform extremely well in a structured operating position without having the personality characteristics that would make them successful in a highly entrepreneurial or externally focused role.

Previously, the company was effectively hiring the person and then trying to make the job fit them.

We reversed that logic.

First define the job.

Then define the behavioural and cognitive requirements.

Then recruit against those requirements.

The objective was not to make hiring more complicated. It was to reduce the probability that the company would spend four months developing someone who was fundamentally mismatched with the position.

The four-month onboarding cycle was consuming the company

Changing recruitment would help future hires, but it did not solve the second cost attached to every new employee.

Training.

Before the redesign, much of the knowledge required to perform a job lived inside other people's heads.

A new employee would join and then learn through repeated interaction with the existing team.

That meant onboarding was not really a process.

It was a recurring demand on people's time.

And because the training period stretched across roughly four months, every new employee could create approximately 16 weeks of interruptions, explanations and follow-up.

The problem became worse when turnover was high.

The company was not simply training people. It was repeatedly rebuilding capability that it had already paid to create.

We therefore designed a structured onboarding system that could transfer the core knowledge without requiring the same people to teach the same material manually every time.

Processes were documented.

Training was organized into a repeatable sequence.

The information a new employee needed could increasingly be delivered through the system rather than through ad hoc conversations with senior employees.

This changed the economics of hiring in an important way.

A new employee could still require supervision. No onboarding system eliminates management completely.

But the business no longer needed to recreate four months of training from scratch for every person who entered the company.

Knowledge started becoming an asset of the company rather than an asset stored primarily inside individual employees.

Then we redesigned the executive manager position

The founder's largest constraint was still unresolved.

Someone needed to own the operating system.

For a company of approximately 25 people, allowing every staffing, compensation and operational issue to climb back to the founder was creating an organizational bottleneck.

So we established a dedicated executive management role.

The executive manager's responsibility was not simply to supervise today's employees.

The position had to maintain the system itself.

That included overseeing staffing needs and replacing employees when necessary, managing the operating responsibilities attached to the team, and administering the compensation structure rather than sending routine people decisions back to the founder.

This distinction mattered.

A manager who can only run the company while the current employees remain in place is not really managing a system.

People inevitably leave.

A functioning operating system has to be able to recruit, onboard and replace people without requiring the founder to rebuild the organization every time it happens.

We also designed the structure so management talent could increasingly emerge from inside the company.

Rather than treating every future management vacancy as an external recruitment project, high-performing employees who demonstrated cultural fit could be identified through the operating system and assessed over approximately three months.

That created a roughly 12-week internal pathway for identifying people capable of taking greater responsibility.

The business was beginning to create managers instead of repeatedly searching for them.

Compensation became part of the operating system

There was another problem with the old model.

If the only way an employee could increase their income was to negotiate with the founder or wait for management to offer a raise, compensation itself created additional management work.

We redesigned the compensation system so employees had a clearer connection between their performance and their ability to earn more.

Financial incentives were attached to the behaviours and outcomes the company actually wanted.

This meant an employee did not need to rely entirely on a manager deciding, subjectively, when they deserved more money.

They could see a pathway.

Perform at the expected level.

Produce the required result.

Create more value in the position.

Increase compensation according to the rules of the system.

The goal was not simply to pay people more.

It was to make compensation reinforce the operating model.

Recruitment determined who entered the system. Onboarding helped them become productive. Performance standards showed what good work looked like. Incentives rewarded the right behaviour. The management structure dealt with replacements and progression.

Those pieces needed to work together.

Otherwise, every improvement in one area would eventually create another problem somewhere else.

The founder's real job had to change

This was ultimately the most important part of the project.

The founder had been treating the company as both an asset he owned and a job he personally performed.

Those are very different relationships with a business.

As long as his role was effectively "owner plus executive manager," every improvement in the company could create more work for him.

More employees created more people to manage.

More customers created more operational decisions.

More complexity created more questions that eventually reached his desk.

Our objective was to remove the second job.

The business still needed the founder.

It simply needed him working on a different category of problem.

Once the operating responsibilities could be transferred into a defined executive management system, his available time could move toward work that only the founder was well positioned to do.

In this case, that meant examining expansion into new markets for the company's existing service and evaluating adjacent markets with stronger profit potential.

That was a very different use of his time.

Instead of asking which employee needed replacing this month, he could ask which market the company should enter next.

Instead of repeatedly explaining an internal process, he could work on where the company should grow.

Instead of acting as the operating system, he could work on improving the machine.

What actually changed

The intervention did not depend on one exceptional manager arriving and rescuing the business.

That would have recreated the original problem.

We changed the architecture around the manager.

A business of roughly 25 people moved from an operating model in which the founder repeatedly absorbed unresolved management work toward a model with clearer job definitions, two role-specific hiring filters, a standardized onboarding process replacing a roughly four-month informal training cycle, a dedicated executive management position, a performance-linked compensation structure and an approximately three-month pathway for identifying future management talent from inside the organization.

The most important result was not a dramatic short-term revenue number.

We did not have enough evidence to claim one.

The result was management capacity.

The founder's time was no longer intended to be the resource that held the operating system together.

That capacity could now be redirected toward expansion.

Why this worked

The original problem looked like employee turnover.

Then it looked like a recruitment problem.

Then it looked like a management problem.

But all three were connected.

Poor role definition made it harder to recruit the right people.

Weak hiring fit increased the chance that employees would leave.

Long, person-dependent onboarding increased the cost of every departure.

An unclear management structure pushed unresolved decisions toward the founder.

A compensation model without sufficiently clear performance incentives created another reason for employees and managers to depend on management intervention.

Hiring another manager without fixing those underlying systems would only have changed the person occupying the position.

It would not have changed the company.

Once the operating system was redesigned, the manager no longer had to compensate for a structurally weak organization.

The system could increasingly support the manager.

And that is what made it possible for the founder to begin stepping away from daily operations.

The business lesson

Many founders think they need a better manager when what they actually need is a business that is easier to manage.

Those are not the same problem.

If roles overlap, recruitment depends on intuition, onboarding knowledge lives inside employees' heads, compensation requires constant negotiation and every replacement requires the founder's involvement, hiring a stronger manager may temporarily reduce the pressure.

Eventually, however, the system catches up with them.

A founder becomes genuinely less operationally necessary when the company can answer five questions without depending on them:

Who should we hire?

How should that person be trained?

How will we know whether they are performing?

How will their compensation progress?

Who takes responsibility when that person leaves?

Once those answers live inside the organization, management becomes a position rather than a dependency on one particular person.

For this 25-person company, that was the real shift.

We were not trying to help the founder become better at managing 25 people.

We were building an organization in which managing those 25 people no longer needed to be his job.

Questions worth asking in your own business

1. If your current manager left tomorrow, would you be replacing a person or rebuilding an entire operating system?

2. How many of your job descriptions contain responsibilities that actually belong to two different positions?

3. When you hire, are you searching for the strongest candidate overall, or the candidate whose abilities and behavioural profile fit the specific job?

4. If a new employee currently requires four months of training, how much of that knowledge could be transferred through a repeatable onboarding system instead?

5. Can strong employees see a defined pathway toward greater responsibility and compensation, or does every progression decision depend on the founder?

6. If you disappeared from daily operations for one month, which decisions would immediately stop moving?

If several of those questions expose the same dependency, the next hire may not be the first thing to fix. The higher-leverage question may be whether the operating system around that hire is strong enough to work without the founder.