You Probably Don’t Have a Bonus Problem

Your employee keeps missing the target.

Attendance is inconsistent.

Sales aren’t where you want them.

Training isn’t sticking.

Productivity needs to improve.

So someone throws out what sounds like a simple solution:

“What if we gave them a bonus?”

More money. More motivation. Better results.

Except that isn’t always what happens.

Sometimes you pay more money and get the exact same problem.

Sometimes you get more of the wrong behavior.

And sometimes you create a compensation structure you can’t get rid of without upsetting your entire team.

Because a bonus does not fix a broken process.

It amplifies behavior.

If you haven’t gotten clear on the behavior, the process, and the outcome first, you may be paying people to work harder inside a system that doesn’t work.

That is why the first question shouldn’t be:

“Are my employees motivated by money?”

The better question is:

“Is the work I’m trying to influence actually compatible with a bonus?”

That’s a very different conversation.

A Bonus Should Never Replace a Good Pay Structure

Start here.

Your employee’s base compensation should answer a simple question:

What am I paying this person to consistently do as part of this role?

That’s the job.

Showing up for work?

The job.

Performing the core responsibilities of the position?

The job.

Hitting reasonable expectations you’ve clearly built into the role?

Still the job.

A bonus should not be the thing holding together an unfair, unclear, or poorly designed base-pay structure.

And it shouldn’t be the only reason someone performs the responsibilities you hired them to perform.

A bonus should reward something beyond the normal expectation.

That’s where owners can get sideways.

We start bonusing the basics.

Then the basic expectation slowly becomes the exceptional expectation.

If you pay an attendance bonus for simply coming to work, what message are you sending?

Showing up is no longer just part of the job.

Now it’s something extra.

That’s probably not the standard you intended to create.

Bonuses Amplify What You Measure

Imagine you tell a cleaning technician:

“If you can clean four houses instead of three, I’ll pay you a bonus.”

What did you ask for?

Four houses.

So you may get four houses.

But what else happened?

Did quality drop?

Were corners cut?

Did complaints increase?

Did the technician rush?

Did teammates have to pick up unfinished work?

Did you create more callbacks or recleans?

The employee didn’t necessarily do anything wrong.

They did exactly what you rewarded.

You measured quantity.

They produced quantity.

The problem wasn’t the employee.

The problem was the structure.

This is why incentives become dangerous when we reduce a complicated outcome to one number.

The number goes up while everything around it quietly starts falling apart.

Not Every Job Should Be Bonused the Same Way

Bonuses tend to work better when the outcome is:

• Easy to measure
• Repetitive or routine
• Clearly defined
• Within the employee’s control
• Directly connected to the employee’s actions

They become much harder when the work depends heavily on:

• Judgment
• Creativity
• Customer care
• Collaboration
• Problem-solving
• Complex decision-making

Why?

Because an incentive naturally pulls someone’s attention toward whatever you’re measuring.

If you bonus a salesperson only for closing jobs, don’t be shocked when they become obsessed with closing jobs.

But did they sell the right customer?

Did they quote it correctly?

Did they protect the margin?

Did they overpromise?

Did operations inherit a nightmare after sales collected the win?

A 1 Layer Deep® business doesn’t just ask whether the number moved.

We ask what happened between the person and the outcome.

That’s where the system lives.

Stop Bonusing People for Things They Can’t Control

This one should be obvious.

But it isn’t.

If an employee cannot influence the outcome through their own daily actions, be very careful about tying compensation to it.

Imagine you offer cleaners a bonus for generating new Google reviews.

One technician has a schedule full of long-term recurring clients who have already left reviews.

Another employee gets new customers every week.

Who has the better chance of earning the bonus?

The second employee.

Not necessarily because they’re better.

Because the system gave them more opportunities.

That’s not motivation.

That’s a structural advantage.

The same thing happens when employees are expected to hit bonuses despite:

• Poor scheduling
• Bad estimates
• Missing supplies
• Weak training
• Broken workflows
• Lack of capacity
• Inadequate tools
• Unclear expectations

You cannot compensate your way out of those problems.

Don’t bonus someone around a broken process. Fix the process.

Money Is Sometimes the Most Expensive Way to Avoid the Real Problem

Before adding another incentive, ask:

Why isn’t the outcome happening now?

Maybe the employee needs better training.

Maybe the workflow is confusing.

Maybe the schedule makes the target impossible.

Maybe expectations haven’t been clearly communicated.

Maybe they don’t have the tools.

Maybe the role has too much on it.

Maybe nobody has given them feedback.

Maybe the process simply doesn’t work.

Adding $100 to the end of a bad process doesn’t make it a good process.

It makes it a more expensive bad process.

This is where Align. Delete. Execute. matters.

Align: What outcome are we actually trying to create?

Delete: What friction, broken steps, bad processes, or unnecessary expectations are preventing it?

Execute: Once the process works, determine whether an incentive would improve the outcome.

Clarity before compensation.

Before You Build the Bonus, Map the Process

If you’re reading this and realizing, I don’t actually know where the problem is, that’s your next step.

Not another bonus.

Not another contest.

Not another incentive.

Map the process.

I’ve created a free System Ownership & Process Map System to help you see how work actually moves through your business.

A Process Map gives you the bird’s-eye view: where the journey starts, the major phases, the decisions and handoffs along the way, and the outcome that defines “done.”

The goal isn’t to build another giant SOP library.

It’s to make the work visible.

Use the System Ownership & Process Map System to identify:

• Where the process starts
• What “done” actually means
• Who owns the outcome
• What steps happen in what order
• Where decisions are being made
• Where handoffs happen
• Where people are forced to improvise
• Where delays and breakdowns happen
• Which high-risk or high-confusion steps need a Microplay
• Where the process has drifted from reality

And here’s the important part:

Don’t map the business you wish you had.

Map how the work actually happens today.

That’s where you’ll find the broken layer.

[Download the Free System Ownership & Process Map System]

Map reality first.

Find the broken layer.

Fix it.

Then decide whether you still need the bonus.

The Two Types of Rewards You Should Understand

One useful way to think about rewards is the distinction Daniel Pink discusses in Drive: “if-then” and “now-that” rewards.

The “If-Then” Bonus

The employee knows about the reward beforehand.

If you accomplish X, then you receive Y.

This can make sense when the work is clearly measurable and largely within the employee’s control.

For example:

If you produce this measurable result while maintaining the required quality standard, you earn this incentive.

But you need guardrails.

Otherwise the employee may optimize for X while unintentionally damaging Y and Z.

The “Now-That” Reward

This happens after exceptional behavior has already occurred.

The employee wasn’t working toward a promised reward.

You noticed something worth recognizing.

For example:

• Saving a difficult recurring customer
• Helping a teammate through a difficult day
• Solving an unexpected operational problem
• Demonstrating exceptional leadership
• Going significantly beyond the normal expectations of the role

Then you say:

“Now that I saw you do that, I want to recognize it.”

Maybe it’s cash.

Maybe it’s a gift card.

Maybe it’s something else meaningful to that employee.

The point is that the reward recognizes exceptional behavior after it happens rather than turning every desired behavior into a transaction.

There is one important warning:

Once a surprise reward becomes predictable, people can start expecting it.

And an expected reward isn’t much of a surprise anymore.

Should Salespeople Get Bonuses If Their Job Is to Sell?

This is where the conversation gets interesting.

If you hired someone to sell, and selling is already part of their job, what exactly is the bonus rewarding?

There isn’t one universal answer.

But it’s worth separating the core responsibility from exceptional performance.

For an inbound salesperson, simply closing a reasonable percentage of qualified leads may already be part of the role.

Instead of only bonusing the sale, you might look at outcomes such as:

• Protecting profit margin
• Increasing profitable upsells
• Selling additional services
• Improving customer retention
• Increasing customer lifetime value
• Maintaining quality while improving conversion

The point isn’t that sales bonuses are bad.

The point is that you need to know exactly what behavior you’re buying.

Because that’s what you’re likely to get more of.

The 1LD Bonus Test

Before you roll out an employee bonus structure, run it through this test.

1. Is It Valuable?

Does the employee actually care about the reward?

Don’t assume everyone wants compensation structured the same way.

Some employees would rather have predictable, consistent compensation than a lower guaranteed amount with a larger potential bonus.

2. Is It Controllable?

Can the employee’s own actions meaningfully influence the outcome?

If another department, the schedule, lead volume, customer mix, or broken systems control the result, rethink the incentive.

3. Is It Attainable?

Can someone realistically earn it?

If nobody has hit your quarterly bonus in five years, you don’t have an incentive.

You have a fantasy.

Eventually people stop trying.

4. Is It Understandable?

Can the employee explain how the bonus works?

Not you.

Them.

If they can’t explain it, it’s too complicated.

Less layers. More results.

5. Is It Trustworthy?

Can employees see the numbers?

Do they trust how results are measured?

Do they trust the company to calculate and pay the bonus correctly?

Compensation without transparency creates suspicion fast.

6. Is It Actionable?

Does the employee know exactly what they should do differently because the bonus exists?

If the answer is no, the bonus hasn’t created clarity.

It’s created noise.

Before You Launch a Bonus, Model It

Do not announce a new bonus on Monday because you got excited about the idea on Sunday night.

Model it first.

Pull at least 8–12 weeks of historical data.

Then ask:

Who would have won?

Who would have lost?

Why?

Could someone game the system?

Would the behavior have hurt quality?

Could you actually afford the payouts?

Does the additional result generate enough financial value to fund the bonus?

And here’s the part owners forget:

What happens when the program works really, really well?

Can you afford it at scale?

A bonus you can afford with three employees may become very different with 30.

Run the math before the employees run the program.

Make Every New Bonus Temporary First

Do not launch an untested bonus as if it will exist forever.

Start with a 60- to 90-day trial.

Tell the team it’s a test.

Be explicit.

You’re evaluating whether the program improves the business and the employee experience.

During the test, monitor more than the metric attached to the bonus.

Watch:

• Productivity
• Quality
• Complaints
• Callbacks or recleans
• Safety
• Teamwork
• Morale

If production goes up 15% while customer complaints double, the bonus isn’t working.

Your dashboard can’t stop at the number you wanted to move.

You have to look for what else moved with it.

Give Employees Visibility Into Their Numbers

If you’re going to tie someone’s money to a number, they should be able to see the number.

Weekly.

They should know:

Where am I?

What have I earned?

What am I missing?

What can I do about it?

And whenever possible, have the employee track their own bonus.

Your job is to review it.

Not spend another three hours every payroll cycle hunting down the numbers.

Remember:

Systems should create movement, not more work.

If your incentive program requires another complicated administrative process just to keep it alive, you’ve added another layer.

Before You Add Money, Fix the Layer

This is the bigger lesson.

Business owners love trying to fix people problems with money.

But sometimes the person isn’t the problem.

The process is.

A weak trainer doesn’t automatically become a great trainer because you add $25 per shift.

An employee with a broken schedule doesn’t suddenly gain capacity because you put a bonus at the end of the month.

A salesperson operating inside a bad estimating process doesn’t magically protect your margins because you offer more commission.

Your people are only as good as your processes.

So before you build another incentive, look one layer deep.

Ask:

What is actually preventing the outcome?

If you don’t know, map it.

If the process is broken, fix it.

If expectations aren’t clear, clarify them.

If the employee doesn’t control the outcome, change the measurement.

Then—and only then—decide whether money can amplify a process that’s already working.

Because that’s what a good bonus should do.

It shouldn’t hold the system together.

It should reward exceptional behavior inside a system that already works.

Summary

Employee bonuses can be powerful, but only when they’re attached to the right behavior and built on top of a functioning system.

Before creating a bonus:

• Define what base pay already covers.
• Identify the specific exceptional behavior you want to encourage.
• Make sure employees control the outcome.
• Confirm the target is realistic and understandable.
• Fix broken training, scheduling, tools, and workflows first.
• Map the process if you don’t know where the breakdown is.
• Model the bonus using historical data.
• Test it for 60–90 days.
• Monitor quality alongside productivity.
• Give employees visibility into their results.
• Make sure the financial value created can actually fund the incentive.

Don’t use money to hide a process problem.

Fix the layer first.

Frequently Asked Questions

Do employee bonuses actually motivate employees?

They can, but money alone doesn’t guarantee behavior change. The incentive must be valuable, attainable, understandable, actionable, and tied to an outcome the employee can influence.

Should I bonus employees for attendance?

Be careful. Showing up for scheduled work is generally a core expectation of the role. Turning basic job expectations into bonus behaviors can unintentionally change what employees view as part of their normal responsibilities.

How long should I test a new bonus structure?

Start with a 60- to 90-day trial. This gives you time to evaluate whether the incentive improves the intended behavior without immediately turning it into a permanent compensation expectation.

What should I measure during a bonus trial?

Don’t measure only the target metric. Watch productivity, quality, customer complaints, callbacks or recleans, safety, teamwork, morale, and the total financial impact.

Should sales employees receive bonuses?

They can, but first determine what base pay already covers. If closing sales is a core responsibility, consider whether exceptional outcomes such as profitable upsells, margin protection, retention, or additional services are better measures for incentive compensation.

What if employees aren’t hitting the bonus?

Don’t immediately increase the reward.

Determine what’s blocking the outcome.

Training, scheduling, capacity, tools, unclear expectations, or an unrealistic target may be the real problem.

If you aren’t sure where the breakdown is happening, map the process from beginning to end and find the layer that’s preventing the employee from producing the expected outcome.