New book coming soon: Only Answer Once → Get book updates

Frankensteining Your Mentors: Take the Good, Leave the Bad

Prefer to listen? Hear this article on Spotify.

Listen on Spotify

Most of us are told to find a mentor. One person we admire, one person whose advice we trust, one person whose example we should follow.

I’ve never particularly liked the idea of handing one person that much influence. People are complicated, and success in one part of life doesn’t make someone an authority on everything else.

So, in honour of Halloween, here’s a slightly strange suggestion: Frankenstein your mentors.

I’m not recommending a trip to the graveyard. I’m suggesting we borrow the best parts of different people and deliberately assemble the qualities we want to develop in ourselves.

The Problem With Having Heroes

We have a habit of treating people as complete packages. We find a successful business owner, an inspiring leader, a great athlete, or a thoughtful teacher, and begin to admire the person rather than the particular qualities that impressed us.

Then something uncomfortable happens. We discover they were a terrible spouse, made a dishonest decision, treated employees poorly, or held a view we strongly disagree with.

Sometimes our reaction is to throw the whole person away. Everything they ever taught us suddenly becomes suspect, as though one failure somehow proves they never had anything useful to offer.

The opposite reaction can be just as dangerous. We become so attached to our hero that we start explaining away their failures. We rename arrogance as confidence, cruelty as toughness, and obsession as dedication because we don’t want to reconsider someone we admire.

Neither response requires much judgment. One rejects the whole person; the other defends the whole person. Both avoid the more difficult work of deciding which specific lessons are worth keeping.

People Are Not Values

I think it’s better to admire characteristics than people.

Maybe you know a business owner who is incredibly disciplined. They keep commitments, arrive prepared, follow up when they say they will, and do the unglamorous work that most people avoid. That’s worth learning from.

But perhaps that same person has a short temper and leaves a trail of frustrated employees behind them. You can learn their discipline without adopting their temper. In fact, their weakness might teach you something about how to apply that discipline without making everyone around you miserable.

Another person might be exceptionally patient with inexperienced employees but struggle to make difficult decisions. Someone else might make bold decisions quickly, yet take risks they don’t fully understand.

Why would I want to become any one of those people? I’d rather learn patience from one, decisiveness from another, and sound risk assessment from a third.

That’s the idea behind Frankensteining your mentors. Take the good. Leave the bad. Then do the work of making those borrowed qualities your own.

A Good Road Can Still Have Potholes

There’s a difference between recognizing someone’s shortcomings and letting those shortcomings erase everything else about them.

Imagine getting directions from someone who knows an excellent route through an unfamiliar city. Halfway through, you discover the road has potholes. Do you turn around and pretend the entire route was worthless? Or do you acknowledge the hazards, steer around them, and keep what was useful about the directions?

People can be like that. A mentor may show you a good way to solve a problem while also showing you behaviours you never want to repeat.

Of course, some flaws are far more serious than potholes. Dishonesty, exploitation, and abuse are not charming imperfections. They can undermine the lesson itself, especially when someone’s apparent success was achieved through the very behaviour you’re being asked to overlook.

If a leader builds a profitable company by cheating customers, you shouldn’t study the cheating as though it were clever strategy. You should question whether the apparent success is worth calling success at all.

And you don’t owe anyone your admiration, forgiveness, access to your life, or a public defence of their reputation just because they happen to possess one useful skill.

Understanding someone’s strengths doesn’t require blindness to their faults. Sometimes the best lesson a person can give you is an example of what not to become.

Don’t Just Copy the Costume

There’s another problem with heroes. We often imitate the easiest parts of them to see.

We copy how someone dresses, talks, runs meetings, or projects confidence. We repeat their favourite phrases and adopt their opinions. It gives us the feeling that we’re becoming more like them without requiring us to develop the qualities that actually made them effective.

It’s a little like putting on a costume for Halloween. You might look the part, but you haven’t acquired the skills underneath it.

A confident business owner may appear decisive because they’ve spent years learning their industry and can recognize patterns quickly. Copying their certainty without building the same competence is not leadership. It’s just being confidently wrong.

Likewise, you can admire someone’s work ethic without copying an unhealthy schedule, or learn from a demanding manager without deciding that disrespect is a prerequisite for high standards.

Study the behaviour that produces the result, the sacrifices that come with it, and the effects it has on other people. Then decide whether it’s a trade you’re actually willing to make.

Build Your Own Version

Here’s an exercise I find useful. Before choosing the people you want to emulate, define the characteristics you want to possess.

Perhaps it’s patience, courage, curiosity, discipline, honesty, sound judgment, or the ability to stay calm when things go wrong. Whatever your list looks like, make the words specific enough that you can recognize the behaviour in real life.

Then think about the people you’ve met, worked with, read about, or learned from. Who demonstrates each quality particularly well? What do they actually do that proves it?

For example, “be more disciplined like Alex” is vague. “Prepare tomorrow’s three priorities before leaving the office, as Alex does” gives you something to try on Monday morning.

You could write four columns on a page: the person, the behaviour worth borrowing, the behaviour you want to avoid, and one practical action you’ll take. It doesn’t have to become a complicated self-improvement system. You’re simply turning admiration into a deliberate choice.

And keep editing your creation. As you gain experience, you’ll realize some of the things you admired weren’t as useful as you thought. You may also discover strengths in people you initially dismissed.

You’re not trying to assemble a perfect human being. You’re learning to make better judgments about who you want to be.

Be Your Own Creation

The danger of having heroes is that we can hand over the responsibility for deciding what is right, admirable, or effective. If they do it, we assume we should do it too.

I’d rather start with my own values and use them as the measuring stick. Other people can provide examples, methods, cautionary tales, and inspiration, but they shouldn’t get to decide which parts of their personality I inherit.

We don’t need perfect people to learn good lessons. We need enough judgment to separate a useful quality from the person carrying it, and enough discipline to actually develop that quality ourselves.

This Halloween, go ahead and Frankenstein your mentors. Just remember that you’re the one who has to live with the creature you build.

You Don’t Create Company Culture. You Set the Standard.

Business owners often ask the same question: How do I create a great company culture?

They want employees who take ownership, care about their work, support each other, and make good decisions. They want a company where everyone shares the same expectations about how things should be done.

So they start talking about building culture. They organize team-building activities, write a list of company values, and perhaps put those values on the wall.

But I think they’re approaching the problem backwards.

Culture isn’t something you create directly. Culture is the result of the standards you establish, the behaviours you demonstrate, and the expectations you consistently uphold.

If you want a particular culture, stop focusing on culture itself. Focus on the things that produce it.

Start by Defining the Company You Want

Before you can develop the culture you want, you need to understand what that culture actually looks like.

What kinds of people do you want working in your company?

How should they approach problems? How should they treat customers? How should they communicate with colleagues? What should they do when something goes wrong?

What principles should guide their decisions, especially when you’re not around?

These questions are far more useful than simply asking whether you want a positive or productive culture.

I’m not particularly fond of traditional corporate values. Too often, they’re vague words like integrity, excellence, innovation, and teamwork.

There’s nothing inherently wrong with those words. The problem is that they don’t tell anyone how to behave.

I’d rather see companies establish guiding principles that provide meaningful direction.

For example, instead of saying you value accountability, you might establish a principle that people take ownership of their mistakes, communicate problems early, and participate in finding solutions.

Now you’ve described something observable. Something you can demonstrate, teach, and hold people accountable to.

That’s the difference between describing an aspiration and establishing a standard.

Define What Those Principles Look Like in Practice

Writing down your guiding principles is only the beginning.

You need to translate them into the everyday behaviours and expectations of your company.

If you believe employees should take initiative, what does that mean?

Does it mean bringing potential solutions when raising problems? Making certain decisions without management approval? Identifying opportunities for improvement?

If you believe in continuous improvement, are employees expected to identify inefficient processes and suggest better ways of doing things?

If you believe in transparency, what information should people share, and when?

You should be able to look at your guiding principles and explain what following each one actually looks like.

Otherwise, you haven’t really defined a standard. You’ve defined an idea.

Culture Is Built Through Accountability

This is where many businesses fall short.

They define their values, communicate them during onboarding, and then largely forget about them.

But the actual culture of a company isn’t determined by what appears in its employee handbook.

It’s determined by what happens every day.

What happens when someone repeatedly fails to take responsibility?

What happens when a manager treats employees poorly but consistently produces good financial results?

What happens when someone ignores the company’s principles because doing so is more convenient?

If those behaviours are allowed to continue, they become part of your culture, regardless of what you’ve written down.

Your culture is ultimately shaped by what you consistently accept.

That means you need to be prepared to have difficult conversations.

People should know what the expectations are. They should receive feedback when they fall short, and a reasonable opportunity to improve.

But there also needs to be a point where you recognize that someone simply isn’t aligned with the company you’re trying to build.

That’s not necessarily a judgment of their character. They may be perfectly capable people who would thrive in another organization.

But if they repeatedly undermine the principles you’ve established, allowing them to stay comes at a cost to everyone else.

You cannot hold a company to a particular standard while continually making exceptions for people who refuse to meet it.

The Owner Must Hold Themselves to an Even Higher Standard

There’s an uncomfortable part of this conversation that business owners need to acknowledge.

You don’t get to exempt yourself.

In fact, you should probably hold yourself to a higher standard than anyone else.

If you demand accountability but blame your employees when things go wrong, you’ve established a culture of blame.

If you expect people to communicate respectfully but routinely lose your temper, you’ve established that respect is optional for people with authority.

If you tell employees to follow documented systems but constantly work around them yourself, you’ve demonstrated that those systems don’t really matter.

Employees pay attention to what their leaders do, not just what they say.

And the higher you are in an organization, the more influence your behaviour has.

I think business owners should make a habit of regularly reviewing their guiding principles. Perhaps even as part of a morning routine.

Read them. Think about them. Consider how you’ve demonstrated them recently.

Ask yourself:

Am I actually behaving like the kind of leader I want this company to have?

It’s easy to establish expectations for everyone else. It’s much harder to examine whether you’re consistently meeting those same expectations yourself.

But that’s where leadership begins.

Culture Requires Constant Reinforcement

Establishing company culture isn’t a one-time project.

You don’t spend a weekend defining your principles, announce them at the next staff meeting, and consider the job finished.

Those principles need to influence your decisions.

They should affect who you hire, how you onboard employees, what behaviours you recognize, who you promote, how you address problems, and sometimes who you decide can no longer be part of the organization.

And they should be revisited regularly.

Not because you need more meetings or corporate bureaucracy, but because standards are only meaningful when they continue to influence how the company operates.

The objective isn’t to create rules for the sake of having rules.

It’s to develop a shared understanding of how the company operates, so that people can make good decisions without constantly relying on the owner for direction.

That’s particularly important as a business grows.

You cannot personally oversee every interaction, decision, and problem. At some point, your employees need to understand the principles behind how you want the company to operate.

When those principles become second nature, people begin making decisions that align with the company’s direction, even when you’re not involved.

That’s when culture becomes particularly powerful.

Stop Asking How to Create Culture

If you’re unhappy with the culture of your company, don’t start by planning a team-building event or writing a new mission statement.

Start by examining what’s actually happening.

What behaviours are you encouraging? What are you tolerating? What expectations haven’t been clearly communicated?

Then define the company you want.

Identify its guiding principles. Translate those principles into real behaviours. Communicate the expectations. Demonstrate them yourself. Hold people accountable, consistently.

And be prepared to make difficult decisions when those standards aren’t being met.

You don’t need to manufacture culture.

You need to establish the conditions that produce it.

Define the standards. Live by them. Hold everyone accountable to them.

The culture will follow.

Systems vs. Processes: What’s the Difference in Business?

The words system and process are often used interchangeably in business. While they are closely related, they serve different purposes.

At Infinite Leverage, we believe understanding this distinction is important when building a business that operates consistently, scales effectively, and does not depend on the owner for every decision.

Let’s break down the difference and how these concepts fit within BOSS (Business Operating System & Standards).

What Is a System?

A system is the overall structure that organizes how a particular function of the business operates.

It defines the workflow, responsibilities, stages, and how work moves from beginning to end.

A system is not necessarily software or an application. It is the organized way your business accomplishes something.

Examples of business systems include:

A well-designed system establishes how work enters the business, who is responsible for it, how it progresses, and what happens when it is completed.

What Is a Process?

A process is a specific sequence of actions performed within a system to accomplish a particular task or outcome.

While a system organizes the overall function, processes describe how individual activities within that system are completed.

Processes give structure to repeatable work, helping employees understand what needs to happen and in what order.

Example: The Sales System

Let’s look at how systems and processes work together.

A business might have a Sales System that moves opportunities through six stages:

Lead → Qualify → Estimate → Proposal → Follow-up → Close

That’s the system. It establishes the overall workflow for turning prospective customers into paying customers.

Within that system are several processes:

Each process supports the larger Sales System.

Different businesses might use different processes or stages. What matters is that the system provides a clear, repeatable structure for how the work gets done.

How Systems, Processes, SODs, and Controls Fit Within BOSS

Within BOSS, we distinguish between four related concepts.

ElementPurpose
SystemOrganizes how work flows.
ProcessDefines the steps for completing part of that work.
SOD (Standard Operating Document)Documents the instructions, standards, and knowledge needed to perform the work.
ControlMonitors whether the system is performing as expected.

Let’s return to our Sales System example.

The system organizes opportunities through the sales pipeline.

The processes define how employees qualify opportunities, prepare estimates, and follow up with customers.

SODs provide the supporting documentation, such as estimating procedures, proposal templates, qualification criteria, and company policies. Capturing this knowledge also supports our Only Answer Once philosophy.

Controls provide visibility into performance, such as the number of outstanding proposals, conversion rates, and average response times. But controls should inform judgment rather than become goals in themselves, a distinction we explore in When the Measurement Becomes the Goal.

Together, these elements help the business operate consistently while giving managers and owners the information they need to make better decisions.

Having Processes Doesn’t Mean You Have a System

This is an important distinction.

A company can have dozens of beautifully documented processes without having a functioning system.

You might have an excellent estimating SOP, a proposal template, and a detailed follow-up checklist.

But what happens when a new lead arrives?

Who receives it? Who decides whether it is worth pursuing? When does it move to estimating? Who follows up? How does management know when opportunities are being neglected?

If those questions don’t have clear answers, the company may have documented processes, but it doesn’t necessarily have an effective Sales System.

A system isn’t simply a collection of SOPs.

It needs to organize the work, establish responsibilities, connect activities, and make execution repeatable.

And importantly, a system shouldn’t create unnecessary bureaucracy. The purpose is to make work easier and more reliable, not to introduce rules for the sake of having rules.

Building a Business That Doesn’t Depend on You

This distinction matters because many owner-led businesses operate through the owner’s personal knowledge and involvement.

The owner knows which leads are important, who should prepare an estimate, when to follow up, and which opportunities deserve attention.

The business functions because the owner keeps everything moving.

But as the business grows, that approach becomes increasingly difficult to maintain.

At Infinite Leverage, our goal is to help owner-led businesses become values- and systems-driven, allowing owners to spend less time directing everyday activities and more time focusing on strategy, growth, and company well-being.

Through BOSS, we help turn scattered knowledge, decisions, processes, and expectations into a structured operating framework the team can actually use.

The objective isn’t to document everything or create complicated procedures.

It’s to establish enough structure that the right work gets done, by the right people, with the right information, without requiring the owner’s constant involvement.

The Bottom Line

The distinction is simple:

A system organizes the work. A process describes how a particular piece of that work gets done.

Processes make individual activities repeatable. Systems connect those activities into a functioning operation. SODs preserve the knowledge required to perform the work, and Controls help measure whether it is working.

When these elements work together, your business becomes less dependent on individual people remembering what to do and more capable of operating through an established structure.

That’s the foundation of BOSS, and an important step toward building a business that can grow beyond its owner.

The 5 Whys: How to Get Beneath Business Problems

When something goes wrong in a business, the first explanation you hear is rarely where the investigation should stop.

A proposal goes out late.

A customer disappears.

An invoice does not get sent.

A material order is missed.

An employee makes a mistake.

Someone asks what happened, gets an answer, and moves on.

That is usually too early.

The 5 Whys is a simple method for getting underneath the visible problem and understanding what actually produced it.

The basic pattern is:

“Why did that happen?”

“Because X.”

“Okay. Why did X happen?”

“Because Y.”

“Okay. Why did Y happen?”

Each answer becomes the subject of the next question.

Keep going until you reach something useful enough to act on.

A Simple Example

Problem:

“The proposal went out late.”

Why did that happen?

“Estimating didn’t finish it in time.”

Okay. Why did THAT happen?

“They were waiting for supplier pricing.”

Why was the supplier pricing late?

“The requests didn’t go out until late in the process.”

Why did that happen?

“Nobody realized they hadn’t been sent.”

Why did that happen?

“We don’t have a standard kickoff process that assigns and tracks supplier pricing requests.”

Now you have something useful.

The original problem was:

“The proposal was late.”

The first explanation was:

“Estimating was late.”

If management stops there, the response might be:

“Estimating needs to be faster.”

But that does not necessarily fix anything.

After continuing to ask why, the problem looks different:

There is no reliable process for assigning and tracking supplier pricing requests when an estimate begins.

That is something the business can actually change.

Ask Why About the Answer You Just Received

This is the most important part of the method.

Do not keep asking why about the original problem.

Ask why about the answer you just received.

The conversation should move like this:

“Why did this happen?”

“Because X.”

“Okay. Why did X happen?”

“Because Y.”

“Okay. Why did Y happen?”

“Because Z.”

You are following the chain downward.

That is different from asking:

“Why was the proposal late?”

and getting five separate answers:

Those may all matter, but that is more like brainstorming possible causes.

The 5 Whys is about taking one cause and following it deeper.

Do Not Stop at Convenient Answers

Some answers sound like explanations, but they are often only the next layer of the problem.

For example:

“The employee didn’t know.”

Okay. Why didn’t they know?

“They weren’t trained.”

Why weren’t they trained?

“We assumed their manager had shown them.”

Why was it based on an assumption?

“We don’t have a documented onboarding checklist.”

The employee genuinely did not know.

That part may be completely true.

But the more useful business problem may be the lack of a reliable onboarding process.

The same thing happens with answers like:

These phrases may describe what happened.

They often do not explain why it happened.

If you hear one, ask why again.

“Poor communication.”

Why was communication poor?

“People weren’t keeping each other updated.”

Why weren’t they?

“There wasn’t a scheduled project meeting.”

Why wasn’t there one?

“Our project setup process doesn’t establish a recurring meeting cadence.”

Now you have something concrete.

Do Not Stop at “Someone Forgot”

This one deserves special attention because businesses use it all the time.

Someone forgot.

Okay.

Why was the process dependent on someone remembering it?

If something is important enough that the business cannot afford to forget it, perhaps there should be:

The question changes from:

“How do we make people remember?”

to:

“How do we build a process that doesn’t depend entirely on memory?”

That is a much stronger management question.

Human beings forget things.

If an important process succeeds only when someone remembers one small step at exactly the right time, the process may be fragile.

Avoid Turning It Into Blame

The 5 Whys should not become:

“Which employee screwed this up?”

The point is to understand how the business produced the outcome.

For example:

“John forgot to send the invoice.”

Why?

“He didn’t realize the job was complete.”

Why?

“Nobody told accounting that the field work had finished.”

Why?

“There is no automatic handoff between operations and accounting.”

You could tell John:

“Remember next time.”

Maybe he will.

But the condition that allowed the problem to happen is still there.

A better solution might be to change the workflow so accounting is automatically notified when a job moves to Complete.

That does not mean employees are never responsible for mistakes.

It means the goal should be to prevent the next occurrence, not just identify who was involved in the last one.

Follow One Thread at a Time

Sometimes when you ask why, you will get several answers at once.

For example:

Why was the proposal late?

“Engineering took longer than expected, we were waiting for supplier pricing, and the estimator was pulled onto another project.”

Those may all be legitimate contributors.

But do not investigate all three at the same time.

Pick one.

Write down the others so you do not lose them, then follow one thread.

For example:

Why was the proposal late?

“We were waiting for supplier pricing.”

Why was the supplier pricing late?

“The requests went out too late.”

Why did that happen?

“Nobody realized they had not been sent.”

Why did that happen?

“There is no standard estimating kickoff process that assigns and tracks supplier requests.”

Finish that thread.

Then go back to the others:

Each of those can become its own investigation.

This matters because it is easy for these conversations to become scattered.

Someone mentions supplier pricing.

Someone else mentions engineering.

Then workload comes up.

Then staffing.

Then scheduling.

Five minutes later, everyone is discussing six different things and nobody has actually followed one of them very far.

Stay on one path.

Follow it until you reach a useful stopping point.

Then go back and investigate the next branch.

Problems Can Have More Than One Branch

Following one thread at a time does not mean every business problem has one perfectly linear cause.

Often there are several.

Suppose you ask:

Why was the project late?

The answer is:

“Engineering took longer than planned and procurement started late.”

Those are two different branches.

Write them both down.

Then investigate them separately.

Branch 1

Why did engineering take longer?

“Because the requirements changed.”

Why did the requirements change?

“Because they were not confirmed with the customer before design began.”

Branch 2

Why did procurement start late?

“Because purchasing did not know the drawings had been released.”

Why didn’t purchasing know?

“Because there is no formal design-to-procurement handoff.”

You may discover several underlying problems rather than one magical root cause.

That is fine.

The purpose is understanding, not forcing reality into a neat diagram.

Five Is Not a Rule

Despite the name, you do not need to ask “why” exactly five times.

Sometimes you uncover the useful problem after three questions.

Sometimes it takes six or seven.

Do not stop simply because you have asked why five times.

And do not keep asking pointless questions just to reach five.

Keep going while each question is producing a deeper and more useful explanation.

Stop when you reach something the business can reasonably act on, or when another why is no longer giving you useful insight.

The number five is not the important part.

The habit of continuing beyond the first explanation is.

Another Example: “The Customer Ghosted Us”

Imagine a salesperson says:

“We lost the customer.”

Why?

“They stopped responding.”

Why did they stop responding?

“They weren’t seeing enough value in continuing the conversation.”

Why?

“We hadn’t given them anything specific enough to make a decision on.”

Why?

“We didn’t have the information required to prepare a recommendation.”

Why?

“The salesperson never completed discovery.”

Why was the opportunity able to progress without completed discovery?

“Our sales process doesn’t define what information must be collected before an opportunity moves to the proposal stage.”

You started with:

“The customer ghosted us.”

You ended with:

“Our sales process allows opportunities to move forward without completed discovery.”

That is much more useful.

The customer may still have ghosted you.

But now the business has something it can improve.

Fix the Lowest Useful Level

Think of the chain like this:

Problem
↓
Immediate explanation
↓
Underlying explanation
↓
Process failure
↓
Systemic cause

You do not need to keep digging forever.

You are looking for the lowest useful level.

The point where you can make a meaningful change.

There is a big difference between:

“Tell estimating to send supplier requests sooner.”

and:

“Every estimate begins with a kickoff checklist that assigns supplier requests, gives them due dates, and tracks whether they have been sent.”

One depends on people trying harder.

The other changes how the business operates.

Fixing something near the top of the chain may solve today’s incident.

Fixing something lower in the chain may prevent an entire category of incidents.

The Simple Habit

The 5 Whys is not complicated.

You do not need special software.

You do not need a workshop.

You do not need a complicated root-cause framework.

You just need to stop accepting the first explanation as the end of the conversation.

Something goes wrong.

Ask:

“Why did that happen?”

Listen to the answer.

Then ask:

“Okay. And why did THAT happen?”

Follow that answer.

Stay on one thread.

Write down other branches and come back to them later.

Keep going until you understand what in the business actually produced the outcome.

Very often, the visible failure is only the last link in a much longer chain.

The purpose of the 5 Whys is to find the part of that chain worth fixing.

Your Turnover Problem Might Not Be a Turnover Problem

When employee turnover starts increasing, it is tempting to treat turnover as the problem.

Maybe compensation needs to improve.

Maybe benefits need to change.

Maybe employees want more flexibility.

Maybe morale is low.

Maybe the company needs better engagement programs, better communication, more team events, or a new retention strategy.

Any of those things could be true.

But turnover is not really a problem by itself.

It is a signal.

And before you start building solutions around that signal, it is worth figuring out what it is actually telling you.

Sometimes your business does not have a turnover problem.

Sometimes you have one person making everyone else miserable.

And sometimes that person is the owner.

A Metric Is Not a Diagnosis

Businesses naturally turn complicated things into numbers.

Revenue.

Margin.

Utilization.

Absenteeism.

Turnover.

That is useful. Good businesses need controls that tell leadership what is happening.

But a control is different from a diagnosis.

If turnover rises from 10 percent to 20 percent, you have learned something important: more people are leaving.

You have not learned why.

Nobody quits because the company’s turnover rate reached 20 percent.

One person quits because they cannot stand their manager anymore.

Someone else quits because every interaction with a particular coworker becomes an argument.

Another employee likes the company and likes the work, but has slowly lost confidence because every decision gets second-guessed.

Another gets tired of priorities changing every week.

Another leaves because of compensation.

And another leaves because of the owner.

Eventually, those individual decisions get grouped together in a spreadsheet and become “turnover.”

The danger starts when we take an aggregate metric and assume it must have an aggregate cause.

Then a company-wide retention strategy gets created to solve a problem that may be sitting in one office.

Follow the Problem Upstream

One of the most useful habits in running a business is separating symptoms from causes by following the problem upstream.

If sales are declining, “we need more leads” might be the answer.

Or it might not be.

Perhaps leads are fine and the sales process is broken.

If projects are constantly late, “we need more staff” might be the answer.

Or perhaps decisions are taking too long, responsibilities are unclear, or one bottleneck is slowing down every project.

Turnover works the same way.

High turnover is a symptom.

The useful question is not simply:

“How do we reduce turnover?”

It is:

“Why are these particular people leaving?”

Those questions lead to very different actions.

The first can easily produce a new policy.

The second requires investigation.

Owners Do Not Experience Employees the Same Way Their Coworkers Do

There is another reason this problem can be difficult for an owner to see.

Owners usually experience employees vertically.

You see whether someone produces results.

You know whether they answer your calls.

You see whether they solve problems.

You know whether they are dependable.

You may know that they bring in a lot of revenue, keep projects moving, or seem deeply committed to the company.

Their coworkers experience them horizontally.

They sit through meetings with them.

They wait for their answers.

They have ideas dismissed by them.

They deal with their temper.

They hear the complaining.

They clean up the messes.

They work around their habits.

They hear what gets said after leadership leaves the room.

Those are two very different perspectives on the same person.

An owner can sincerely think:

“Sarah is one of the best people we have.”

The people working beside Sarah can sincerely think:

“I don’t know how much longer I can work with Sarah.”

Both can be true.

As leaders move farther from the day-to-day work, that perspective gap becomes easier to miss. It is one of the reasons to keep the head and the hands connected through a strong feedback loop.

Leaders naturally evaluate people based on what those people contribute directly.

But direct contribution is only part of someone’s impact on a company.

Measure Organizational Drag, Not Just Individual Output

Businesses are usually much better at measuring individual output than organizational drag.

Imagine someone who appears to be an exceptional performer.

They produce excellent work.

They hit their numbers.

They respond quickly when the owner needs something.

They take responsibility.

They solve difficult problems.

On a performance report, they look fantastic.

But people avoid asking them questions because every conversation becomes confrontational.

Meetings become quieter when they enter the room.

Employees stop bringing forward half-formed ideas because they know those ideas will immediately be criticized.

Information starts flowing around them instead of through them.

Good employees become frustrated.

Eventually, some leave.

That employee may still be producing excellent individual results while reducing the output of the organization around them.

That is organizational drag.

And it can be remarkably expensive while remaining almost invisible in traditional performance measurements.

A great salesperson can make the sales team worse.

A brilliant engineer can make an engineering department worse.

A highly productive project manager can make everyone on the project less effective.

Individual productivity and organizational value are not always the same thing.

Managers Have Even More Leverage

The effect becomes larger when the person creating the problem is a manager.

A difficult coworker can make someone’s day unpleasant.

A difficult manager can influence almost everything about someone’s working life.

Workload, priorities, opportunities, decision-making authority, schedule, compensation, feedback, confidence and advancement can all flow through that person.

Yet managers are often primarily evaluated from above.

Leadership sees the department’s numbers.

Employees experience how those numbers are being produced.

A manager can hit every target and still leave behind an exhausted, defensive team.

In fact, strong short-term results can sometimes hide the problem.

The department performs.

The manager looks effective.

People quietly leave.

New people get hired.

The department performs again.

More people leave.

Eventually someone says, “We seem to have a retention problem.”

At that point, it is worth looking for the recurring variable.

Sometimes it is not the employees.

It is the manager.

And Sometimes the Recurring Variable Is the Owner

Owners should not exempt themselves from this analysis.

That is difficult because we experience our own behaviour through our intentions.

Other people experience it through its consequences.

An owner thinks:

“I have high standards.”

The employee experiences:

“Nothing I do is good enough.”

The owner thinks:

“I move quickly.”

The employee experiences:

“The priorities change every few days.”

The owner thinks:

“I stay involved.”

The employee experiences:

“I am not trusted to make decisions.”

The owner thinks:

“I am direct.”

The employee experiences:

“Every mistake becomes embarrassing.”

The owner thinks:

“I push people because I know what they are capable of.”

The employee experiences:

“I dread talking to the owner.”

Sometimes both descriptions contain truth.

The point is not that owners should surrender their standards or manage entirely according to employee perception.

The point is that intentions do not eliminate consequences.

If capable people repeatedly leave the same part of the business, reporting to the same person, or after experiencing the same pattern, that deserves investigation.

Even when the pattern leads back to you.

The Founder Does Not Have to Be the Manager

There is also an assumption worth questioning in owner-led companies.

Ownership and management are not the same job.

Someone can be an exceptional entrepreneur and an average people manager.

They can be brilliant at sales, strategy, product development, technical work, relationships or identifying opportunities.

None of that automatically means they should have 40 people reporting through them.

As a company grows, the role where the founder creates the most value can change.

At an earlier stage, being involved in everything might have been necessary.

Later, the same behaviour can become a bottleneck.

The business may eventually outgrow your ability to manage it before it outgrows your ability to contribute to it.

That is not necessarily a failure.

Recognizing it may be part of successfully moving from owning your job to actually directing a company.

Build a Better Turnover Control

The answer is not to stop measuring turnover.

The answer is to make the control more useful.

Instead of recording only how many people leave, look for the patterns underneath the number:

Now turnover becomes more than an HR statistic.

It becomes a business control.

And a good control does not just tell you that something is wrong.

It helps you find where to look.

Fix the Cause, Not the Metric

There are legitimate company-wide causes of turnover.

Compensation can be wrong.

Benefits can be poor.

People can be overworked.

Roles can be unclear.

There can be no opportunity for advancement.

The culture itself can be unhealthy.

Those problems deserve systemic solutions.

But the opposite mistake is equally dangerous.

Not every recurring problem needs another policy.

Not every employee issue requires a company-wide initiative.

Not every retention problem requires better benefits.

Sometimes the system is telling you about a very specific problem.

The job of leadership is to find it.

Before changing compensation, introducing another engagement program, reorganizing the company or buying everyone pizza, ask a simpler question:

“What is actually causing good people to leave?”

Then follow the answer as far upstream as it goes.

It might lead to a policy.

It might lead to a manager.

It might lead to one employee.

And every once in a while, it might lead back to the owner.

That is what business controls are supposed to do.

Not just tell you what happened.

Help you see what needs your attention.


This article builds on an idea first explored on Jeremiah Vanderlaan’s personal blog in “Your Business Might Not Have a Turnover Problem. It Might Have a ‘One Shitty Individual’ Problem.” Infinite Leverage takes that idea one step further: how owners can use signals like turnover to identify the underlying problems inside their businesses.

Your Strategy Needs a Do-Not-Do List

Most businesses are very good at adding things.

Every strategic planning session seems to produce more:

Very little gets removed.

The result is predictable. The new strategy gets added on top of everything the company was already doing.

New priorities. Old priorities. New initiatives. Existing responsibilities.

Eventually, strategy starts to mean more work.

A useful strategy should do something different. It should help the business decide what deserves its limited attention, resources and energy.

And that means it should also tell you what not to do.

Strategy Requires Exclusion

Michael Porter famously argued that the essence of strategy is choosing what not to do.

That matters because virtually every strategic decision contains a trade-off.

If you decide to focus on a specific kind of customer, you are also deciding not to focus equally on every other customer.

If you decide to standardize your service, you are deciding that you will not customize everything for everyone.

If you decide that your management team needs to focus on improving the core business, you are deciding not to chase every adjacent opportunity that appears.

The positive side of strategy is usually easy to write down.

The harder question is:

What are we going to stop doing, refuse to do, or deliberately ignore because of those decisions?

That is where a Do-Not-Do List becomes useful.

The Do-Not-Do List

A Do-Not-Do List is an explicit record of things your business has consciously decided not to pursue.

It could include markets, customers, projects, products, behaviours, processes, investments or management activities.

For example:

These are not necessarily things that are bad.

Some may be excellent opportunities.

They are simply things the business has decided are not important enough right now.

That distinction matters.

A Good Idea Can Still Be the Wrong Idea

One of the hardest things for an owner to accept is that a good idea can still be a bad idea to pursue.

There are always more opportunities than there is capacity to pursue them properly.

A business has finite:

Every new initiative competes with something already underway.

That means the question cannot simply be:

Is this a good idea?

It also has to be:

Is this more important than what we have already decided to do?

Those are very different questions.

An opportunity can be profitable, interesting and completely reasonable, and still deserve a no.

Sometimes the best strategic decision is not “never.”

It is simply “not now.”

This Takes Discipline

Writing the strategy is usually the easy part.

Following it is harder.

The opportunity outside your target market will eventually appear.

A large customer will ask for an exception.

Someone will show you an interesting piece of software.

A competitor will launch something that makes you wonder whether you should launch it too.

A new market will suddenly look attractive.

The owner will have another idea.

This is where strategy is tested.

It takes discipline to look at something genuinely attractive and still say:

That isn’t what we have decided to focus on.

It takes discipline not to chase every dollar of revenue.

It takes discipline not to customize the business for every customer.

It takes discipline to leave a good idea alone while a more important idea is still being implemented.

It takes discipline to allow resources to remain concentrated instead of spreading them across ten initiatives.

Without that discipline, the strategy slowly becomes meaningless.

Every exception seems reasonable on its own.

But enough reasonable exceptions eventually produce a business that is doing everything again.

Stop Doing and Do Not Do Are Different

There is an important distinction between a Stop-Doing List and a Do-Not-Do List.

A Stop-Doing List asks:

What are we doing today that we should stop?

That is valuable.

Maybe there is a report nobody needs anymore. A meeting that serves no purpose. A service that has become unprofitable. A process that should have disappeared years ago.

The Do-Not-Do List asks a different question:

What have we decided we will not start doing?

It is preventative.

Instead of cleaning up complexity after it enters the company, you establish boundaries that help prevent unnecessary complexity from entering in the first place.

Both are useful.

One removes yesterday’s clutter.

The other protects tomorrow’s focus.

Turn Strategy Into Decision Rules

This becomes especially valuable in an owner-led business.

Consider how many questions eventually find their way back to the owner:

If all of those decisions require the owner, the owner is still functioning as the business’s decision engine.

A well-designed Do-Not-Do List can turn some of those decisions into company knowledge.

Instead of the owner repeatedly deciding whether to quote small projects, the company might establish:

We do not quote projects below $100,000 unless they are for an existing strategic customer.

Now there is a decision rule.

Employees can act without waiting for the owner.

This is one of the ways strategy can become part of a business operating system rather than something that exists only in a planning document.

Good strategy should help people make decisions when the owner is not standing beside them.

Then Create a Didn’t-Do List

There is another side to this idea that I think deserves more attention.

Businesses are constantly recording what they accomplished.

Visible action gets celebrated.

Restraint rarely does.

But some of the most valuable management decisions a company makes may be things that never happened.

Those decisions can create enormous value, but they are almost invisible.

So alongside the Do-Not-Do List, consider keeping a Didn’t-Do List.

The Do-Not-Do List is prospective:

Here are the things we have decided not to do.

The Didn’t-Do List is retrospective:

Here are the things we had the opportunity to do, but deliberately chose not to.

One establishes the discipline.

The other shows whether you actually had it.

Review It Like Any Other Strategic Commitment

At a quarterly or annual strategy review, businesses naturally ask:

Add another question:

What did we say we weren’t going to do?

Then ask:

Did we actually avoid doing it?

Suppose leadership decides the company will no longer pursue projects below $100,000.

Six months later, 25% of the estimating team’s time is still being spent pricing projects below $100,000.

The strategy says one thing.

The operating behaviour says another.

That is useful information.

The Do-Not-Do List makes the contradiction visible.

The Didn’t-Do List gives you evidence when the opposite happens and the strategy is actually being followed.

Strategy Should Reduce Options

There is a natural temptation to think good strategy should create more possibilities.

Sometimes it should.

But one of the most valuable things a strategy can do is eliminate possibilities.

It narrows the field.

It tells people where not to spend their time.

It prevents every interesting opportunity from becoming an organizational priority.

It helps employees make decisions without continually escalating them.

And it protects important work from being interrupted by the next attractive idea.

That does not mean becoming rigid.

Strategies change. Markets change. Businesses learn.

The Do-Not-Do List should change too.

But those changes should be deliberate.

There is a difference between changing your strategy because you learned something important and abandoning your strategy every time something interesting appears.

The difference is discipline.

What Did Your Strategy Make You Say No To?

A useful test for any strategy is surprisingly simple:

What does this strategy cause us to say no to?

If the answer is nothing, the strategy may not have created much direction.

It may simply have added another set of priorities to everything the business was already doing.

Instead, try creating three lists:

  1. What are we going to do?
  2. What are we deliberately not going to do?
  3. What did we have the discipline not to do?

The first list shows your intentions.

The second establishes your boundaries.

The third tells you whether those boundaries were real.

Because strategy isn’t only demonstrated by what a business accomplishes.

Sometimes it is demonstrated just as clearly by what the business had the discipline to leave alone.

When the Measurement Becomes the Goal

Most growing businesses eventually reach a point where the owner cannot personally know everything that is happening.

When the company is small, the owner might be involved in every sale, every project, every customer problem and every important decision. They do not need a dashboard to tell them how the business is doing because they are standing in the middle of it.

That stops working as the company grows.

People are hired. Managers take responsibility. Processes are created. The owner becomes further removed from the day-to-day work.

And that creates a perfectly reasonable question:

How do I know whether the business is actually working?

The answer is, at least partially, measurement.

Revenue, gross margin, close rate, utilization, leads, production output, defects, response time, schedule performance, customer satisfaction and dozens of other measurements can help leadership understand what is happening without personally observing everything.

Measurement is an essential part of delegation and accountability.

But it creates another problem.

Eventually, the organization can stop using the measurement to understand the goal and start treating the measurement as the goal.

Goodhart’s Law

There is already a name for this problem: Goodhart’s Law.

It is commonly summarized as:

“When a measure becomes a target, it ceases to be a good measure.”

The underlying idea is associated with British economist Charles Goodhart, who described the problem in the context of monetary policy in 1975. His original observation was that an observed statistical relationship could break down once pressure was placed on it for control purposes.

The familiar wording above came later. Anthropologist Marilyn Strathern used that generalized formulation in a 1997 paper about auditing and accountability in British universities.

So this is not a new idea, and it is certainly not an argument against measurement.

Goodhart’s Law is a warning about what happens when we confuse a measurement with the thing we actually care about.

The Measurement Is Not the Goal

Imagine a business that wants more sales.

Management believes consistent prospecting contributes to sales, so it starts measuring the number of sales calls each salesperson makes.

The original logic looks something like this:

Goal → Activity → Measurement

Profitable sales → Consistent prospecting → Calls made

There is nothing inherently wrong with that.

Then management creates a target:

Every salesperson should make 50 calls per day.

Eventually the system can start working in the opposite direction:

Measurement → Target → Behaviour designed to improve the measurement

The salesperson’s job quietly changes from generating good customers to making 50 calls.

Those are not necessarily the same thing.

People may shorten valuable conversations so they can get to the next call. They may contact poor prospects because those calls are easier to make. They may become more concerned about logging activity than advancing opportunities.

The dashboard improves.

The business might not.

Metrics Do Not Just Measure Behaviour. They Create It.

This is the part of measurement that leaders need to take seriously.

The moment you tell people something is being measured, you have changed the system.

The effect becomes even stronger when the measurement is connected to bonuses, performance reviews, promotions, rankings, reprimands or constant management attention.

People naturally pay attention to what the organization signals is important.

If management repeatedly says that 50 calls represents good performance, employees will try to produce 50 calls.

That does not necessarily mean anyone is dishonest or intentionally gaming the system.

They may simply be responding rationally to the system leadership created.

Before blaming employees for optimizing a metric, leadership should ask whether the organization taught them to optimize it.

That makes KPI design more than a reporting exercise.

It is part of organizational design.

Instead of only asking:

Can we measure this?

We should also ask:

What behaviour are we likely to create if we make this number important?

This Happens Everywhere

The sales call example is easy to understand, but the same problem can appear almost anywhere in a business.

Marketing

You want more customers, so you measure leads.

Marketing finds ways to produce more leads. Lead volume increases dramatically, but qualification deteriorates and the sales team spends more time sorting through people who were never likely to buy.

The lead dashboard looks fantastic.

Revenue does not move.

Customer Service

You want customers to get help quickly, so you measure tickets closed.

Employees learn that closing tickets is rewarded. Difficult problems get closed prematurely, customers reopen tickets and the number of completed tickets rises while the actual customer experience gets worse.

Operations

You want employees to be productive, so you measure utilization.

People become extremely good at filling timesheets and keeping themselves busy.

Whether that activity is producing the most valuable outcome for the business is a different question.

Project Management

You want projects completed on schedule, so you closely monitor percentage complete.

Now everyone has an incentive to describe their portion of the project as slightly further advanced than it really is.

The schedule can remain green right up until everyone suddenly discovers that the project is late.

Safety

You want fewer workplace incidents, so you reward teams that report zero incidents.

Unfortunately, you may have created two ways to improve the number:

Only one of those makes the workplace safer.

Start With What You Actually Want

A useful way to think about controls is to separate three different things.

1. The Outcome

What does the business actually want?

For a sales organization, that might be profitable customers who stay with the company.

2. The Behaviour or Process

What activities do we believe contribute to that outcome?

Perhaps consistent prospecting, good qualification, useful sales conversations and reliable follow-up.

3. The Measurement

What information can we use to understand whether those things are happening?

Calls, meetings, qualified opportunities, proposals, sales, gross margin and retention could all tell us something.

The danger begins when the third item replaces the first.

A measurement is evidence about what is happening.

It is not the reason the business exists.

Leading Indicators Are Useful, but They Need Context

Businesses understandably like leading indicators because outcomes often arrive too late.

Revenue tells you what already happened.

If revenue falls significantly this month, the underlying problem may have started several months ago.

That makes it useful to look further upstream:

Calls → Meetings → Qualified Opportunities → Proposals → Sales → Gross Profit → Retained Customers

You do not want to wait until the end of that chain before realizing there is a problem.

But there is a trade-off.

The further a KPI is from the outcome you actually care about, the more carefully it needs to be interpreted.

Increasing calls is easy to measure quickly.

Increasing profitable, satisfied, long-term customers takes much longer to observe.

You could dramatically increase the first number without improving the last one at all.

Leading indicators should therefore be treated as signals, not guarantees.

One Number Rarely Tells the Whole Story

Businesses are systems.

Changing one thing can affect something else.

That makes individual metrics particularly dangerous when they are viewed in isolation.

A salesperson could have fewer calls and fewer meetings while producing larger deals, a higher close rate, better margins and stronger customer retention.

Is the low call volume a performance problem?

Maybe.

Maybe not.

You need more of the system before you can understand what the number means.

The same problem exists throughout a company:

If You Only MeasureYou Might Miss
RevenueGross margin, receivables and customer retention
LeadsQualification, cost per opportunity and eventual revenue
Production outputDefects, rework and waste
Tickets closedReopen rate and customer satisfaction
UtilizationActual value created and unnecessary work

This is where balancing metrics can help.

You do not need 50 KPIs to run a good business.

You simply need enough context that one number cannot create a completely misleading picture of reality.

Not Every Measurement Belongs on the Owner’s Dashboard

As businesses become more sophisticated, there is a tendency to keep adding measurements.

Someone discovers that a number can be measured, so it gets added to a report.

Eventually the owner receives a dashboard containing dozens of numbers, charts and colours.

More information does not automatically create more understanding.

It can be useful to distinguish between three types of measurement.

Core Controls

These are the relatively small number of indicators leadership regularly watches because they provide information about the overall health of the business.

Revenue, gross margin, cash position, qualified pipeline, customer retention or on-time delivery might belong here depending on the company.

Operational Metrics

These help managers understand and operate a particular system.

A sales manager may need more detail about calls, meetings, conversion rates and follow-up activity than the owner needs every week.

Diagnostic Metrics

These are measurements you investigate when something appears wrong.

If the close rate suddenly falls, leadership might examine lead sources, salesperson performance, response times, pricing, competitive losses and dozens of other measurements.

Those numbers can be extremely useful without requiring a permanent position on the owner’s dashboard.

The objective is not to see every number.

The objective is to know where attention is needed.

A Good Control Should Cause the Right Question

Suppose gross margin falls from 31 percent to 24 percent.

The control has already done something valuable.

It got your attention.

But the number does not necessarily tell you what to do.

Perhaps estimating has deteriorated.

Maybe material costs increased.

Maybe labour productivity fell.

Maybe the company took on a different mix of work.

Maybe one unusually bad project distorted the month.

Maybe the data itself is wrong.

A poor approach to controls says:

The number changed. Take this predetermined action.

A better approach often says:

The number changed. Look here.

A good control does not always give you the answer.

It helps you ask the right question. The 5 Whys is one simple way to follow that question deeper until you reach something useful to fix.

Employee turnover is a useful example: the number can tell you people are leaving, but it cannot tell you whether the cause is compensation, a manager, one employee, a broken system or the owner.

Metrics Have a Shelf Life

There is another danger with business measurement: once a KPI exists, it tends to live forever.

Imagine a company where salespeople are simply not prospecting enough.

Management starts tracking outbound activity.

For the next six months, measuring calls is extremely useful. Behaviour changes, prospecting becomes consistent and the original problem disappears.

Three years later, the business may still be obsessing over the same call target even though the constraint has moved somewhere else.

Maybe qualification is now the problem.

Maybe capacity is constrained.

Maybe close rates are excellent and there is no reason to increase call volume.

The business changed.

The measurement did not.

Controls should evolve with the systems they are intended to monitor.

Periodically ask:

A system that continues simply because “that is how we do it” has stopped being a useful system and started becoming bureaucracy.

The Dashboard Is a Map, Not Reality

This problem becomes more important as the owner moves further away from the day-to-day work.

Eventually, leadership experiences more of the business through abstractions:

That is necessary.

You cannot build a scalable company where the owner needs to personally observe every process.

But abstraction creates distance.

A dashboard can say everything is green while the employees doing the work know that a process is falling apart.

Both can be true.

The dashboard is measuring what someone decided to measure.

The people doing the work are experiencing the entire system, including the things nobody thought to put on the dashboard.

This is one reason leadership cannot completely separate the head from the hands.

Measurement should complement judgment, observation and conversation.

It should not replace them.

The Owner’s Measurement Trap

This is particularly important for owner-led businesses.

The owner often begins with too much direct involvement.

They know what is happening because they are involved in nearly everything.

Eventually they realize this is unsustainable and begin delegating.

Then something uncomfortable happens.

They no longer know everything.

The natural response is to demand more reporting.

That instinct is not wrong. A business that operates through delegation needs controls.

But the owner can move from one extreme to another:

Personally involved in everything → Managing everything through numbers

Neither is the objective.

The goal is to build enough visibility that leadership can understand where attention, judgment and intervention are actually required.

How to Design Better Business Controls

Before turning a measurement into an important KPI, ask a few questions.

  1. What outcome are we actually trying to create?
  2. Why do we believe this metric tells us something about that outcome?
  3. How far removed is this measurement from the outcome?
  4. What behaviour might people adopt if we make this number important?
  5. Could someone improve this number while making the actual business worse?
  6. What other measurement would reveal that?
  7. Who actually needs to see this measurement?
  8. What decision should this measurement help us make?
  9. Is this a permanent control or a temporary diagnostic measure?
  10. Should this number trigger an action or simply trigger a conversation?

Those questions create a much stronger control system than simply asking what data is available.

Controls Should Concentrate Judgment, Not Eliminate It

There is a temptation when building systems to try to remove human judgment.

If we can create enough rules, enough KPIs and enough dashboards, perhaps the business can simply run itself.

That is usually the wrong objective.

The purpose of a good business system is not to eliminate judgment.

It is to concentrate judgment where it has the most value.

An owner should not need to spend valuable time determining whether someone made 47 or 50 calls yesterday.

The system can track routine activity.

Human attention can then be directed toward larger questions:

That is where leverage starts to matter.

As an owner builds leverage through people, systems and technology, they no longer personally perform every action in the company.

They need controls that allow them to understand the business from a distance.

But the controls are there to help leadership see reality.

They are not reality themselves.

Never Confuse the Measurement With the Thing Being Measured

Goodhart’s Law does not tell us to stop measuring.

Quite the opposite.

A growing company needs good measurement because an owner cannot manage a larger organization through intuition and personal involvement alone.

But every KPI is ultimately a proxy for something the business actually cares about.

The moment improving the proxy becomes more important than improving the underlying outcome, the measurement begins to lose its value.

Build controls.

Measure the business.

Use leading indicators.

Create accountability.

But keep asking what those measurements actually represent and what behaviour you are creating by making them important.

A KPI is an instrument.

A dashboard is a map.

A control is a signal.

Use them to know where to look, and then apply judgment to what you find.


Sources and Further Reading

Goodhart, Charles A. E. “Problems of Monetary Management: The U.K. Experience.” 1975. Goodhart’s original observation was developed in the context of monetary policy and later became known as Goodhart’s Law.

Strathern, Marilyn. “‘Improving Ratings’: Audit in the British University System.” European Review, Vol. 5, No. 3, 1997, pp. 305-321. This paper contains the widely used generalized formulation, “When a measure becomes a target, it ceases to be a good measure.”

Every Growing Business Has Two Scaling Problems: Demand and Capacity

Business owners talk about “scaling” as though it is one problem.

It usually is not.

One of the biggest challenges of scaling a business is that growth depends on two separate systems expanding at roughly the same time.

The first creates demand.

The second creates the capacity to fulfill that demand.

Those systems are related, but they are not the same. Understanding the difference makes it much easier to diagnose what is actually limiting the growth of a company.

If your team has unused capacity and not enough work, you probably have a demand problem.

If good opportunities are available but you cannot reliably deliver more work, you probably have a capacity problem.

And if the owner is personally responsible for solving both problems, you may have an owner leverage problem.

TL;DR

A growing business has to scale two things at once: demand and delivery capacity. Demand brings enough of the right work into the company. Capacity gives the company the people, systems, processes, management and resources required to deliver it reliably.

When one falls behind the other, growth stalls. The mistake is treating the imbalance as one generic “growth problem” instead of identifying which side is actually constrained.

The First Scaling Problem: Demand

Every business needs enough suitable work coming through the door.

That is the job of the demand side of the company.

Depending on the business, this might include marketing, sales, business development, customer relationships, estimating, proposals, lead generation, account management, or some combination of them.

The important word is not simply “more.”

It is suitable.

A business does not benefit from filling its pipeline with work that is unprofitable, outside its expertise, strategically undesirable, or difficult to deliver.

The demand side of the company is responsible for creating enough of the right opportunities.

At its simplest, the question is:

How much good work can we bring into this company?

As the business grows, that becomes a scaling problem of its own.

Those are demand-scaling questions.

The Second Scaling Problem: Capacity

Winning more work is only useful if the company can actually deliver it.

That is the second scaling problem.

Capacity is not simply the number of employees a business has.

It is the practical ability of the organization to deliver more work reliably.

That may involve hiring, but it can also involve:

A company with 30 employees can sometimes have less usable capacity than a well-organized company with 20.

The capacity side of the business is therefore asking a different question:

What needs to change so we can reliably deliver more?

That distinction matters because the answer to a capacity problem should not automatically be to stop creating demand.

Diagnose the Problem Before Trying to Fix It

One useful way to think about growth is to ask which side of the company is currently constrained.

If you have employees, equipment, or production capability sitting idle, you probably have a demand problem.

You have capacity available. The business needs more suitable work to use it.

If the sales pipeline is healthy but the company is constantly delaying work, turning opportunities away, missing deadlines, or overloading employees, you probably have a capacity problem.

There is enough demand.

The organization needs to expand its ability to deliver.

This sounds obvious when written down.

In practice, companies often blur the two together.

Someone says, “We are too busy,” and the response is to slow down sales.

Or someone says, “We need more revenue,” and the response is to sell aggressively without addressing the operational problems already developing underneath the business.

Both reactions can create problems.

Growth becomes easier to manage when you identify which machine actually needs attention.

The Dangerous Mistake: Letting Today’s Capacity Determine Tomorrow’s Demand

Imagine a business sees a promising new market.

There appears to be significant demand. The work fits the company’s capabilities. Margins look attractive. Existing customers may already be asking for it.

Someone raises the opportunity internally.

The immediate response is:

“We couldn’t handle that right now.”

That may be completely true.

But it does not necessarily mean the company should walk away from the opportunity.

The better question may be:

What would have to change for us to handle it?

Would we need another crew?

Another manager?

Different equipment?

Better training?

A stronger scheduling process?

A new supplier?

A different operating system?

Six months to build the capacity?

Those are very different questions from simply asking whether the company can handle the work today.

A growing business gets into trouble when it allows its present delivery capacity to define its future demand.

Today’s capacity is a constraint.

It should not automatically become a strategy.

A Capacity Problem Should Not Automatically Become a Sales Problem

This distinction can be surprisingly powerful.

When demand exceeds capacity, organizations sometimes solve the imbalance by slowing the demand side down.

Stop marketing.

Stop prospecting.

Turn away opportunities.

Tell the sales team not to sell quite so much.

Sometimes that is temporarily necessary. There are real limits to how quickly a business can safely expand.

But it should be a deliberate decision.

Otherwise, an operational limitation has quietly become a sales strategy.

The business is no longer asking:

“What opportunities should we pursue?”

It is asking:

“What opportunities fit inside the organization exactly as it exists today?”

Those are not the same thing.

The first question is strategic.

The second is constrained by the present.

Why Demand and Capacity Eventually Need Separate Accountability

As an owner-led business grows, I think demand and capacity should eventually have different accountable leaders.

Not because the two sides should operate independently.

Quite the opposite.

They need to work closely together.

But separating accountability creates productive tension.

The sales or demand leader can say:

“There is a lot more good work available.”

The operations leader can respond:

“To deliver that amount of work reliably, we need two additional people, another manager, and a better scheduling process.”

Leadership can then decide:

“Is this where we want the company to go?”

That is a useful conversation.

The alternative is often more subtle.

If the same person owns both demand and operations, they naturally see every sales opportunity through the lens of today’s operational limitations.

They may see a promising opportunity and immediately think:

“We don’t have the capacity.”

“We don’t have the people.”

“We are already too busy.”

And because they are accountable for both sides, the easiest solution is often to throttle demand.

No conflict occurs.

But no one is really challenging the current capacity of the company either.

Separate accountability prevents today’s operational limitations from quietly becoming tomorrow’s growth ceiling.

The Tension Is the Point

The demand leader and operations leader should not always agree.

In fact, some disagreement is useful.

The demand side should be finding opportunities that occasionally stretch the organization.

The operations side should be identifying what would be required to service those opportunities reliably.

That does not mean sales should promise anything it wants and throw the problem over the wall to operations.

Nor does it mean operations should be forced into reckless growth.

The tension exists so that the company can make explicit decisions.

Demand asks:

What opportunities exist?

Operations asks:

What would it take to deliver them?

Leadership asks:

Should we make that investment?

That is a much healthier growth conversation than simply allowing whoever feels busiest to determine how large the company should become.

The Owner May Temporarily Lead One of These Functions

Of course, most owner-led businesses do not begin with two executives sitting beneath the owner.

The owner probably performs both roles at first.

They generate work.

They deliver work.

They hire people.

They solve problems.

They manage customers.

They make almost every important decision.

Over time, parts of those responsibilities begin moving to other people.

Often, operations is one of the first major functions to receive dedicated management.

The owner may continue leading sales and business development.

That can make sense for quite a while.

Owners often have advantages that are difficult to replicate.

They have credibility.

They understand the market.

They know the company’s capabilities.

They have relationships.

They can make decisions quickly.

They can communicate the vision of the business better than almost anyone else.

So an owner can be extremely effective at generating demand.

But that does not necessarily mean the owner should permanently be responsible for leading the demand side of the company.

Being Good at Sales Is Different From Leading Sales

The problem is often not skill.

It is consistency.

The owner may be the best salesperson in the company and still be a poor long-term sales leader.

Because the owner has another job.

A customer problem escalates.

An employee quits.

A major financial decision needs to be made.

A new partnership opportunity appears.

An operational issue requires attention.

A strategic decision cannot be delegated.

The owner’s attention moves constantly.

Sales and marketing leadership, meanwhile, require consistency.

Pipeline reviews need to happen.

Follow-ups need to happen.

Marketing needs direction.

Opportunities need to be developed.

Processes need to improve.

People need coaching.

When the owner is also the company’s escalation point for everything else, those activities are easily interrupted.

The problem is not that the owner is incapable of leading sales.

The problem is that the organization is still relying on the owner’s personal attention to keep one of its two major growth systems functioning.

That is an owner leverage problem.

Growth Requires Two Machines

A healthy growing business is continually expanding two things.

Demand.

And capacity.

Demand reveals where capacity needs to grow.

New capacity creates room for additional demand.

More demand reveals the next constraint.

The company adapts again.

The cycle continues.

There will rarely be perfect balance.

Sometimes demand will temporarily lead capacity.

Sometimes capacity will be built ahead of demand.

That is normal.

The important thing is recognizing that these are two different systems with two different jobs.

When people are sitting idle, ask how to create more suitable demand.

When worthwhile opportunities exceed what the company can reliably deliver, ask how capacity needs to change.

Do not automatically solve a capacity problem by reducing ambition on the demand side.

And do not solve a demand problem by adding capacity nobody needs.

The Owner’s Job Eventually Changes

Early in a business, the owner is often both machines.

They create demand and figure out how to deliver it.

That works because the business is small enough for one person to hold much of the system together.

As the company grows, that approach becomes increasingly difficult.

The owner’s role has to change.

Instead of personally creating all the demand and personally solving every capacity problem, the owner begins building accountable functions that can do both.

One leader expands demand.

Another expands the organization’s ability to deliver.

The owner increasingly operates above those systems.

Where should we grow?

Which opportunities are worth pursuing?

Where should we invest?

What risks are acceptable?

What capacity should we build?

What is preventing the company from moving forward?

Those are different questions from the ones the owner asked when they were personally doing the work.

And that is part of the progression from running the business to directing it.

That progression still depends on staying connected to what implementation teaches. In Keep the Head and the Hands Close Together, I make the related argument that leaders should create distance from routine work without becoming insulated from the reality created by that work.

Growth requires two machines.

One creates demand.

The other creates the capacity to fulfill it.

The owner’s job is not to become both machines.

It is to build them, give each clear accountability, and keep them moving in the same direction.

Keep the Head and the Hands Close Together

Ideas are cheap.

That isn’t an insult to ideas. Ideas matter. But most businesses are not suffering from a shortage of them.

Owners have ideas. Managers have ideas. Employees have ideas. Consultants certainly have ideas. Put six reasonably intelligent people in a room for an afternoon and you can probably leave with a whiteboard full of them.

The harder part is knowing which ideas are actually good.

Then implementing them.

Then seeing what happens when the idea collides with customers, employees, schedules, software, budgets, existing processes, physical constraints and all the other irritating details that were conveniently absent from the whiteboard.

That last part is where a lot of management thinking breaks down.

We tend to treat thinking and implementation as two separate jobs. Someone comes up with the idea. Someone else does the work.

But implementation is part of thinking.

TL;DR

Leaders should delegate work. They should build management layers, systems and processes that reduce how much routine work depends on them.

But delegation becomes dangerous when the people making decisions stop seeing what happens after those decisions are implemented. The work can move down the organization. The information created by that work has to come back up.

The goal isn’t to keep the owner’s hands on everything. It is to keep the owner’s head connected to reality.

Ideas Are Cheap. Judgment Isn’t.

A good idea can be extremely valuable. But the idea itself is only the beginning.

You still need to know whether it is a good idea or merely an idea that sounds good in a meeting.

You need to understand what it will cost, who it will affect, how difficult it will be to implement, what could go wrong, what could go wrong if you do nothing, and whether the organization is actually capable of executing it.

That requires judgment.

And judgment gets better when it has evidence to work with.

An idea sitting in someone’s head hasn’t encountered very much evidence yet. It hasn’t frustrated a customer. It hasn’t confused an employee. It hasn’t run into a software limitation. It hasn’t added three unexpected steps to a process. It hasn’t saved two hours a week. It hasn’t broken anything. It hasn’t worked surprisingly well.

It is still mostly a hypothesis.

Implementation Is Part of Thinking

We often imagine the process like this:

Think. Decide. Implement.

Thinking happens first. Then a decision is made. Then everyone else gets busy executing it.

I think a better model is:

Think. Do. Observe. Learn. Think better.

Implementation creates information that did not exist when the idea was conceptual.

Suppose you create a new approval process because mistakes are slipping through. On paper, adding another approval makes perfect sense. The new control gets implemented and the error rate drops.

Success.

Except quotes now take two days longer to reach customers. Salespeople start finding ways around the approval process because they are losing deals. The approver becomes a bottleneck. Small decisions that used to take five minutes now sit in a queue.

Was the original idea wrong?

Not necessarily.

Maybe the company genuinely needed better control. But implementation exposed information that wasn’t available when the process was designed.

The next version can now be better. Maybe only certain quotes require approval. Maybe there should be thresholds. Maybe the underlying problem wasn’t approval at all, but unclear pricing authority.

You could not learn all of that from the original strategy meeting.

You had to put the idea into contact with reality.

When Ideas Only Travel Down

This is where hierarchy can become dangerous.

Hierarchy itself isn’t the problem. Businesses need roles, authority, management and delegation. Someone has to be able to make a decision without assembling the entire company for a town hall meeting.

The problem is one-way hierarchy.

A leader has an idea. It goes to a manager. The manager gives direction to an employee. The employee implements it.

And that is where the information stops.

The employee discovers that the process doesn’t quite work. The customer reacts differently than expected. A workaround becomes necessary. A seemingly minor rule creates a major delay.

But none of that makes its way back to the person who made the original decision.

So the leader moves on to the next idea while still believing the previous one worked exactly as intended.

Do that long enough and seniority can start insulating people from the consequences of their own decisions.

That is a dangerous place for a business to end up.

Authority can move downward. Reality has to be able to move upward.

The Hands Know Things the Head Cannot See From a Meeting Room

The people doing the work encounter information that simply isn’t visible from a strategy session.

That doesn’t mean the frontline employee is always right. It doesn’t mean management should abandon broader strategy every time someone dislikes a new process.

It means different positions inside a business can see different parts of reality.

The person doing the work may understand a physical constraint that management overlooked. The salesperson may see customer resistance before it appears in a report. The project manager may discover that two individually reasonable procedures conflict with one another. The bookkeeper may notice that a supposedly efficient process creates a mess three weeks later.

That information is valuable.

The hands don’t merely carry out the head’s ideas. They generate information the head needs in order to think well.

This same perspective gap can hide the real causes of employee turnover. Leadership may see a strong performer while the people working beside that person experience the organizational drag they create.

This Is Not an Argument Against Delegation

There is an obvious trap here.

An owner reads something like this and concludes that they need to stay involved in everything because nobody understands the business like they do.

Please don’t.

That is how the owner becomes the bottleneck for the entire company.

The objective of Infinite Leverage is almost the opposite. The owner should become progressively less necessary to routine execution. People, managers, standards, systems, technology, controls and written company knowledge should allow more of the business to operate without requiring the owner’s direct involvement.

But there is a difference between delegating work and disconnecting yourself from the information created by the work.

You can stop preparing every proposal without becoming ignorant of why proposals are being lost.

You can stop managing every project without becoming unaware of where projects regularly break down.

You can stop talking to every customer without becoming disconnected from what customers are actually experiencing.

You can stop personally following every process without having no idea whether the process works.

Leverage should create distance from routine work. It should not create insulation from reality.

There Is Such a Thing as Being Too Close

The opposite problem exists too.

If you spend every hour doing the work, you may understand today’s operational details extremely well while having almost no time to think about where the company is going.

You can miss patterns across departments. You can ignore capital allocation, risk, hiring, market changes, strategy and the design of the business itself because today’s problems consume all available attention.

That isn’t good leadership either.

Too close to the hands and you can lose perspective.

Too far from the hands and you can lose reality.

The goal is not maximum proximity. It is maintaining the feedback loop.

Design the Return Path

As a company grows, this feedback loop becomes less automatic.

When there are four people in the business, the owner probably hears about every problem whether they want to or not. At forty people, information starts moving through layers. At four hundred, an executive could make decisions affecting hundreds of employees without ever speaking to most of the people living with the consequences.

At that point, staying connected to reality has to become intentional.

A few questions are worth asking:

This doesn’t require executives hovering over people’s shoulders.

It requires a return path.

The business needs a way for what employees learn, what customers experience and what implementation reveals to feed back into standards, systems and future decisions.

Creators Stay Close Enough to Be Corrected

There is a useful distinction between having ideas and creating.

A creative person can imagine something that doesn’t exist.

A creator has to deal with what happens when they try to make it exist.

Reality starts arguing back.

The budget isn’t enough. The software won’t do what you expected. Customers don’t care about the feature you thought they would love. Employees interpret the instruction differently than you imagined. Something you assumed would be difficult turns out to be easy. Something that looked trivial becomes the entire project.

That doesn’t mean reality should limit ambition.

Quite the opposite.

Understanding the constraints tells you what actually has to change if you want to accomplish something ambitious.

There is a big difference between challenging a constraint because you understand it and ignoring a constraint because you never bothered to learn about it.

Keep the Head and the Hands Close Together

The higher you move in an organization, the easier it becomes to spend your time with abstractions.

Dashboards. Strategies. Reports. Plans. Policies. Budgets. Organizational charts.

Those things are useful because leaders need to see the larger system.

But every abstraction is a compressed representation of something happening in the real world.

A customer is waiting. An employee is making a judgment call. A manager is working around a broken process. A salesperson is hearing the same objection for the tenth time. A piece of equipment is sitting idle. Someone has figured out a better way to do something and nobody else knows about it yet.

The further the head gets from the hands, the easier it becomes to manage the representation while losing touch with the thing being represented.

So delegate.

Build management layers. Build systems. Document knowledge. Automate repetitive work. Create controls. Get yourself out of work that does not require you.

But make sure the learning comes back.

The goal is not to keep your hands on every task.

The goal is to make sure your thinking can still be corrected by reality.