This month, Jannice Koors’s firm at Pearl Meyer published a piece on one of the hardest calls a compensation committee ever has to make: what to do when the goal you set at the beginning of the performance period no longer reflects the business you’re running by the middle of it. The piece is written for early-stage growth companies, especially in life sciences, where strategic priorities can move fast enough that a goal set in January is not the right goal by July. Pearl Meyer lays out a crisp five-factor framework — strategic relevance, source of change, shareholder impact, materiality, board oversight, and timing — for deciding whether to adjust a goal mid-cycle, and then a menu of adjustment methods if the answer is yes.

It’s a disciplined piece of governance thinking. The authors are careful. The framework reads like exactly what a comp committee should have in hand when management walks in and says the plan has drifted.

Here’s what we’d add, from the seat of the HR and Total Rewards leader who has to run the same conversation one layer down the org chart, for an employee bonus plan that was never going to a proxy advisor in the first place.

The principle is the same. The stakes are not.

Pearl Meyer is writing about an executive incentive plan that lives inside a public disclosure, sits under board oversight, and will eventually get scored by ISS, Glass Lewis, and a say-on-pay vote. The governance scaffolding is heavy, and it exists to absorb a well-reasoned mid-cycle change without permanent damage.

The employee annual bonus plan has none of that scaffolding. There is no compensation committee that signed off at the start of the year in a formal minute. There is no proxy disclosure that reset expectations. The only people who read the plan document are the employees whose paychecks depend on it, and the only “governance body” that ratifies a change is usually the executive team that proposed it.

That asymmetry matters. When a board quietly revises a CEO’s short-term incentive goal in Q3, the stakeholders most affected are shareholders, and their response plays out in a vote at the next annual meeting. When HR quietly revises the goal behind a supervisor’s bonus plan in Q3, the stakeholder most affected is the supervisor, and their response plays out in a conversation with a recruiter the following Tuesday. In our experience, an employee who believes the bonus plan moved on them once will stop believing the plan next year. And the year after that.

That’s the thing to hold onto before any of the other questions. Whatever the governance question looks like at the board level, the behavioral question at the employee level is larger.

A few principles from the seat we’re sitting in.

1. Treat the bonus plan as a contract, even when it isn’t one.

Employees do not distinguish between “this is a legally enforceable promise” and “this is what the company said it would pay me if I did X.” They live inside the second sentence. A comp committee can defend a mid-cycle goal change to a proxy advisor with a disclosed rationale. The employee cannot defend that same change to a spouse at a kitchen table with anything except “the company decided.” That difference is not rhetorical. It’s the whole difference.

2. Pearl Meyer’s five factors are right. Add a sixth: can the system actually do it?

The Pearl Meyer framework asks whether the change is strategically relevant, externally driven, materially impactful, board-approved, and well-timed. All five are the right questions. The one they don’t need to ask — because they’re writing for compensation committees where the plan is administered on a bespoke spreadsheet by a team of consultants — is the one HR teams absolutely have to ask: can the compensation administration system actually execute the change cleanly, without off-cycle adjustments, without exceptions emailed to payroll, without a reconciliation that someone has to remember to run in February?

This is unglamorous and it is decisive. A mid-cycle goal change that introduces manual workarounds into a three-hundred-person bonus calculation doesn’t just add work. It adds a new category of errors the plan didn’t have before. And every one of those errors will be read by the affected employee as confirmation that the plan is no longer something they can count on.

3. The flexibility was supposed to be designed in, not bolted on.

Most of the reasons companies reach for a mid-cycle goal change — tariffs, a strategic pivot, an acquisition, a product line winding down — are not surprises that arrived on a specific day. They are weather that has been building for a quarter, and a well-designed bonus plan already has instruments to respond to weather.

Performance ranges do this. A plan that pays threshold at seventy percent of target, target at one hundred, and maximum at one-thirty already gives the business air to miss without the goal becoming irrelevant. Weighted metrics do this. A plan that puts forty percent of the bonus on a financial metric and sixty on operating milestones is less brittle than a plan that puts everything on one number. Discretionary modifiers do this, when they are disclosed to the employee upfront as part of the design and not invented in October to fix an outcome.

If the plan is so rigid that the only response to a changing business is to rewrite it mid-year, the plan was under-designed. That’s a next-year fix, not a this-year fix.

4. When a goal really is obsolete, prefer the cleanest path that preserves trust.

Pearl Meyer lays out four methods for adjusting a goal: replace it, remove and reallocate the weighting, remove and reduce the denominator, or rely on discretion. Their analytical preference for reducing the denominator — scoring the remaining goals out of a smaller number rather than redistributing the weight onto metrics that weren’t meant to carry it — is the one that translates best to an employee bonus plan. It’s the method that does the least violence to the contract the employee signed up for at the start of the year. Reweighting changes what people were measured on. Reducing the denominator only changes whether a measurement still applies.

If you are going to touch a mid-cycle plan at all, touch it the way that moves the fewest pieces.

5. The most underrated option is “honor the calendar and fix the next plan.”

In our experience, the best answer to most mid-cycle goal drift is the one least likely to be chosen: let the plan pay what the plan says it will pay, communicate clearly about the business shift, and use the planning cycle you already have to build a better plan for the next year. This is unsatisfying because it requires the company to accept a payout that may feel too high or too low against what the business actually did. It is also the answer that preserves the credibility of the plan across every future year. A plan that pays out what it said it would pay out, even in a weird year, is a plan employees believe in. A plan that got rewritten once will be quietly distrusted forever.

The close.

Pearl Meyer’s framework is the right one if you find yourself at the table. The deeper move, though, is to arrive at the table less often. Build plans that already contain the flexibility you’ll need, invest in the transparency that makes a strange year survivable without a rewrite, and hold the line when the instinct to adjust is really an instinct to protect the business from an outcome the plan is capable of absorbing on its own.

If you’re looking for tools to simplify how you manage and administer variable pay — including the design work that makes mid-cycle changes unnecessary in the first place — let’s talk.