Your performance review just came back excellent.

Your raise is 3.2%.

You did the math before the meeting ended. With inflation, 3.2% on your current number gets you somewhere you've already been. The gap between what you're making and what you should be making, the number you carry privately, the one you check against market data late at night when you can't sleep, that gap did not close. It widened. Slightly. But it widened.

You said thank you. You meant it. You went back to your desk and kept delivering.

This is how the most expensive career decision most technology leaders ever make goes unrecognized. It doesn't feel like a decision. It feels like patience. It feels like professionalism. It feels like playing the long game.

It is none of those things. It is a strategy of waiting for a company to self-correct on something companies do not self-correct on without a reason.

The annual raise cycle is a maintenance system. It is designed to keep you in your role at a cost the organization finds acceptable. It is not designed to close a $60K or $80K or $100K gap between what you're earning and what you're worth in the current market. It was never designed to do that. That was never its function.

A way to think about it is a “Patient Professionals Tax”.. And across thirty years of working with technology leaders, it's the most common and most costly pattern I've seen.

Leslie was an individual contributor at an engineering firm when I first worked with her. Smart. Capable. Producing work that was worth significantly more than she was being paid. She had been patient. She had been professional. She had been told to wait. We built a plan together: benchmark the market, position for a move, negotiate from data rather than from tenure. She left for a competitor at a meaningful increase. A few months later, her former employer called to offer her a manager position with a huge number to “get her back”.  Now 3 years later she’s a director.  From IC => Manager => Director.  Boom!

The math of patience is the thing most technology leaders haven't done explicitly. Take your current compensation. Add 3% per year for five years. Now look at what the market is paying for your role and level today, not five years from now, today. The gap you're looking at is not what patience costs you over five years. It's what patience has already cost you over the last five.

The Patient Professional Tax runs on three beliefs that feel true and aren't.

The first: my company will eventually recognize the gap and act on it. Companies recognize gaps when there is a forcing function. An external offer. A visible flight risk. A market-wide retention crisis. Excellent performance is not a forcing function. It's an expectation. It holds your position. It does not move your compensation.

The second: asking for more will make me look ungrateful or disloyal. This belief costs more money than almost any other belief in a technology leader's career. The leaders who close significant income gaps ask. They ask with data, with context, with a clear case. They ask before they're desperate, which means they ask from a position of strength rather than from a position of needing to leave.

The third: patience is a virtue that will be rewarded. In relationships, often yes. In compensation, no. Compensation responds to market signals, not to character traits. Your patience is invisible to the model that determines your raise.

The reason capable, high-performing technology leaders stay stuck paying the Patient Professionals Tax is not weakness. It's a skill gap that looks like a character choice.

Most technically excellent leaders were rewarded for most of their careers by doing excellent work and letting results speak. That pattern worked at every level until it stopped working. The stopping point is usually somewhere around the director level, when the compensation model has fully absorbed their output and recalibrated around it.

At that point, the game requires a different set of skills. Market awareness. Deliberate positioning. The ability to create a conversation your company isn't planning to initiate. These skills feel self-promotional to people trained to be excellent and quiet. They are not self-promotional. They are how compensation actually moves at the senior level.

Three moves break the trap. They work together. Running only one of them produces limited results.

The first move is benchmarking with precision. Not a general sense that you're underpaid. Not a vague awareness of market ranges. A specific, current number for your exact role, level, and geography, sourced from recruiter conversations, compensation surveys, and peer intelligence. You cannot negotiate from discomfort. You can negotiate from a number. Get the number.

The second move is creating market visibility without committing to leave. Take the recruiter call. Have the conversation. Know what you'd be offered. This does two things simultaneously: it gives you real market data, and it subtly shifts the dynamic inside your current organization. Leaders who are clearly aware of their market value are treated differently than leaders who are not. The organization does not need to know you're having these conversations. The market awareness shows up in how you carry yourself and what you're willing to accept.

The third move is making the ask from strength, not desperation. Most technology leaders who finally ask for significant compensation movement do it too late, when they're already emotionally committed to leaving or when they've received an external offer they're planning to accept. That ask carries urgency and often burns goodwill. The ask from strength happens before any of that. It's a planned conversation, with data, framed around your value to the organization going forward rather than the injustice of the past. It's harder to have. It works better.

The gap you have right now will not close on its own. Your company's model is working exactly as designed. The question is whether your compensation strategy is working as designed, or whether it's just a strategy of hoping.

If you've been waiting for the right moment to address this, the moment doesn't come on the calendar. You create it.

If you want to map out what that looks like for your specific situation, this is where we start: https://meeting.techleadership.net/

The raise isn't coming. What's coming is another year of the gap being exactly where it is, unless you decide to close it.

Robert