I hit the number on a Tuesday. The offer letter sat in my inbox while the kids argued over cereal, and for about six hours I let myself believe the math would hold. By Friday the same leader who’d fought to close me was already floating the next title, the one that would finally let me shape direction instead of just execute it. The compensation target I had chased for years moved the moment I reached it.
The strange part wasn’t the goalpost moving. It was how quickly my own hunger agreed to follow it, a textbook hedonic treadmill. I started measuring my weeks by whether the new scope felt “strategic” enough, even though the actual work—shipping something useful, keeping the team human—hadn’t changed. The compensation target had moved, so my sense of enough moved with it.
Why the compensation target keeps moving after you hit it
John Wesley’s first rule—do no harm—supplies the lens. It is not a sentiment; it is a constraint that forces an actor to examine whether the next action damages the capacity of the people or systems already in motion. Applied to career design, the rule surfaces how chasing the moving target quietly erodes the conditions required for sustained product judgment.
Designing career signals beyond the compensation target
Title inflation is the clearest case. A product manager who moves from senior to lead because the band opened up often inherits meetings that replace the original user research cadence. The harm is not malicious, but it is measurable in the drop of actual decisions that reach shipped code. In one children’s ministry tool, the decision to expand the PM title ladder coincided with a measurable decline in volunteer completion rates because the new leads spent their cycles on cross-functional alignment rather than print-first UX fixes that had previously driven retention. Wesley’s rule would have required checking whether the title change reduced the team’s ability to protect the seven-minute volunteer workflow.
Flow is the constraint that actually produces durable work once external targets lose their pull. The state is not mystical; it is the condition in which a product person can hold the full problem context long enough to make a single, high-leverage change. When compensation conversations dominate attention, the calendar fills with status updates that fragment that context. The practical result is more features that solve for the next review cycle instead of the recurring user friction that only appears after several iterations of the same surface. Teams that redesign their own signals around flow—protecting two-hour blocks without status reporting, for example—ship fewer but more retained updates, which is the metric that compounds. Once the compensation target loses its pull, flow is what remains.
Values function as the veto that prevents the next visible win from overriding the work already underway. Once base compensation security exists, the remaining decisions are almost entirely value-laden: whether to accept scope that inflates headcount without improving outcomes, or to decline a promotion track that requires relocating decision rights away from the users. Without an explicit veto, the default is to accept the signal because it still registers as forward motion inside most organizations. The teams that treat values as operational rather than aspirational are the ones that can decline the moving target without career penalty, because they have already anchored their internal metric to something the organization cannot revoke.
Your Turn: Apply This Today
- Pick one current compensation signal—title, band, or public metric—and write the exact competence behavior it was originally meant to reward, then measure that behavior directly for the next four weeks instead of the signal.
- Block two contiguous hours on your calendar this week labeled only with the name of the user workflow you are responsible for, and decline every meeting that would break it unless the meeting owner can name the specific decision that requires your presence.
- Identify the last three features or initiatives that were accepted primarily because they aligned with a visible career marker, then list the concrete user harm or delay each one introduced; share that list with your immediate team by Friday.
- Define a single internal metric—volunteer task completion, return session depth, or error recovery time—that you will track weekly for the next month regardless of whether it appears in any performance review.
- Write a one-sentence veto criterion for the next compensation conversation you enter, using Wesley’s first rule as the test: if accepting the change would measurably reduce your capacity to protect the core workflow, decline it in writing.
- Replace one recurring status update meeting this month with a written summary sent the day before, then use the recovered time to complete one small product change that directly improves the metric you defined above.
The Director Who Stopped Performing His Title for LinkedIn shows what happens when the signal is removed before the competence metric is in place. The 1997 Lesson AI Product Teams Keep Missing demonstrates how external markers continue to distort judgment long after the original problem has been solved.
I consult with product leaders and ministry technology teams on redesigning career signals around flow and values, and on applying durable constraints to compensation decisions. Let’s talk.