Open your feed this week and you'll find two competing panics: Today, its AI is about to take everyone's job and previously it was that companies suddenly need everyone back in the office. We had that second argument for three straight years before AI showed up. I want to set the headlines aside and look at this the way an economist would: what is a salary actually buying, and does AI change the answer. That's a more useful question than either panic, and it's the one that actually determines what happens to anyone's pay.
You're Paying for Time, Outcomes, or Units. Pick One.
Hourly pay is honest about what it is: you're buying a block of a person's time at a given skill level. There's no ambiguity to resolve when a tool makes that person faster. Fewer hours, less pay, full stop, assuming the work still gets done to standard.
A salary is a different contract, whether anyone wrote it down this way or not. It's closer to fixed-price consulting: I'm paying you a set amount to deliver a set scope of outcomes, and I don't particularly care if it takes you thirty hours or sixty (at least in concept). The problem is that almost nobody treats salaried pay this way in practice. Employers rarely define the outcome with enough precision to know when it's been delivered faster, and employees don't think of themselves as fixed-price contractors. They think of salary as time, just paid as a fixed amount per week. Many managers would be quite angry if their salaried employees did "get their 40 hours."
There's a third model, mostly extinct in white-collar work but worth remembering: piecework, pay per unit produced. A seamstress paid per garment, a machinist paid per part, a translator paid per word. Piecework forces the measurement question that salary has always avoided, because you can't pay per unit without first defining the unit. Salaried knowledge work spent decades refusing to do that definitional work, and that's exactly why the AI conversation feels unresolved. We're trying to apply outcome logic to a system that was never built to measure outcomes in the first place.
If you can't answer "what outcome am I actually paying this salary for," you have no principled basis to adjust it when AI changes how that outcome gets produced. That's not a reason to avoid the conversation. It's a reason to fix the measurement first.
How You'd Actually Measure Knowledge Work
This is the part most comp discussions skip past, and it's the part that actually matters. A few measures that hold up better than "seems faster now":
- Cycle time on comparable work: time from assignment to accepted completion, tracked against a baseline, not a guess.
- Rework and defect rate: speed that creates more correction downstream isn't speed, it's deferred cost.
- Outcome against committed scope: did the thing you asked for get delivered, not just activity that looks like progress.
- Judgment calls under peer or stakeholder review: the part AI doesn't touch, and the part salary was always supposed to be paying for.
None of this is exotic. It's the same discipline fixed-price consulting firms use to know whether a project made money. Most internal functions have simply never had to build it, because nobody was asking the question hard enough to require it. AI is now asking.
Enterprise vendors are finally racing to build that measurement layer. SAP just agreed to acquire TechWolf, a Belgian workforce-intelligence startup whose entire product is a continuously updated model of the tasks inside a job, the skills applied to them, and how that compares to the external labor market. SAP's own term for it is an "evidence layer," and the plan is to fold it into SuccessFactors and Joule so hiring, redeployment, and pay decisions get made from that data instead of a manager's impression of who seems faster (SAP News, 2026). That's an acquisition, not a thought experiment: someone just bet real money that this measurement problem is the one worth solving.
As a side note, are you thinking about your latest goal setting session? How pointless does that seem to you right now? I bet your boss asked you to define your own performance goals when it should have been the other way around. Setting your development goals, sure, but an organization should be telling you how they plan to measure your performance.
The Market Doesn't Care Which Argument You Find Persuasive
Strip away the fairness debate and a company is left with one hard number: the relative cost per unit of work. There are exactly two ways to produce a unit of output, and the market prices both whether you like it or not.
- Option A: the market price of a human with the right skill, in the right geography, doing the work the old way.
- Option B: the fully loaded cost of the automation, AI, or software that produces the same unit.
When B gets cheaper than A for a given task, the economics push toward B regardless of anyone's intentions. That's not new. It's the same substitution logic that moved manufacturing, then call centers, then basic bookkeeping. What's new is the speed: the data so far shows AI cutting labor costs on applicable tasks by roughly a quarter today, with estimates running toward 40% as the tools mature (Nexford, 2026). A survey this year found more than half of companies are already reducing compensation specifically to fund AI investment (CFO Dive / ResumeBuilder, 2026). The market is answering the "should I" question with "I already am," whether or not any individual manager has thought it through.
What's Actually Happening to Pay Right Now
The honest picture is messier than either "AI is taking everyone's job" or "AI is a non-event." Research out of the Dallas Fed this year found AI is simultaneously augmenting some roles and substituting for others within the same labor market, and the wage effect depends entirely on which side of that line a given task falls on (Dallas Fed, 2026). Roles where AI mostly automates discrete, well-defined tasks are seeing real wage compression, estimated around a 6.7% decline in wage growth relative to pre-ChatGPT trends for highly exposed roles. Starting pay for junior and mid-level employees in AI-exposed functions has already fallen 5-6% since ChatGPT launched. Meanwhile, roles where AI mostly augments judgment, tacit knowledge, and experience are holding steady or improving, and senior compensation in those same companies has stayed flat or risen (CNBC, 2026).
Translate that: if AI replaced the mechanical part of someone's job and left nothing harder in its place, the market is already pricing that role down. If AI removed the mechanical part and freed the person to do the judgment work you were previously too short-staffed to get to, their value just went up, not down. Same tool, opposite outcome, and the difference is entirely about what you ask the person to do with the time it freed up.
The Floor Under Any Negotiation
Before any of this gets near a comp conversation, check what you're legally allowed to do, because it varies more than most executives assume. In the US, exempt employees are, by definition, not paid for hours, and the FLSA's salary basis rules restrict how and when you can dock an exempt employee's pay at all. Non-exempt and hourly roles are a different animal: fewer hours worked, legitimately, is fewer dollars paid, and overtime rules still apply the moment they cross 40 hours a week (Paycor). Layer on locality: some jurisdictions and most union contracts specify compensation structures, job classifications, and pay bands that have nothing to do with how fast AI lets someone work, and changing them unilaterally because a tool sped someone up is a fast way to find yourself in front of a labor board or an arbitrator, not a performance review.
There's also an economic floor under the legal one. Every employee has some minimum number of hours, or minimum total earnings, below which they stop negotiating and start job hunting instead. Economists call it a reservation wage. Cut comp too aggressively, even inside the law, and you don't get a leaner, more efficient employee. You get a resignation letter, a open seat, and a recruiting cost that usually dwarfs whatever the cut saved.
Part-time work is the other side of this coin, and it predates AI by decades. Several countries built part-time and reduced-hours arrangements into labor policy deliberately, as a form of job-sharing, long before anyone was worried about AI. It's a real model. It also only works where the cost of living leaves room for reduced hours to mean reduced income rather than financial crisis. A four-day week funded by AI productivity gains is a reasonable idea in a market where people can absorb that trade. It's a nonstarter where they can't.
The Burnout Nobody's Measuring Yet
There's a quieter effect showing up inside teams that have adopted AI fastest. The person who gets good with the tools first doesn't usually end up with more free time. They end up as "the fast one," and the backlog finds them. Managers reallocate work toward whoever can absorb it, and the AI-fluent employee ends up doing the equivalent of two or three people's output at one person's pay, with no corresponding increase in hours worked. That's a different kind of burnout than the overtime-driven kind. It's overload per hour, not overwork by the clock, and most organizations aren't watching for it because their systems are still built to measure hours, not throughput. Left unmanaged, it means your best AI adopters burn out first, which is exactly backward from what you'd want.
Three Questions Before You Touch Anyone's Pay
I'd work through these in order, before a single comp conversation happens with HR or an employee:
Who's paying for the AI? If the employee is covering the cost of the tool themselves, out of their own pocket or their own time learning it, there is no argument for a reduction. They invested in their own productivity; the company didn't earn a discount on that. (I'm setting the security argument against shadow-AI tools aside here. That's a real issue, but it's a different conversation.) If the company is paying for the license, the training, and the integration work, that's a legitimate cost the company gets to weigh against the output. That's where a tradeoff conversation can start, not end. Any tool deployment should start and end with measurement in order to understand the outcome.
What filled the freed-up time? If you handed the person new, higher-value work commensurate with the time AI freed up, you are not paying less for the same output. You're paying the same for more output, and the conversation should be about whether that new scope deserves more pay, not less. If there genuinely isn't more work to give them and the role now takes less time to do, there's a real argument for adjusting the arrangement. But be honest with yourself about whether you're also prepared to give some of that time back to the person, in flexibility or reduced hours, rather than just taking the gain in one direction. For those readers coming from the HR world, we saw a similar transition there as improved self-service tools transformed HR Business Partners from transaction managers to strategic advisors.
Can you actually prove the outcome changed, or just the activity? Don't cut pay based on a vibe that someone "seems faster now." If you can't measure the outcome you were buying before AI, you have no baseline to compare against, and you're not making a compensation decision, you're making a guess with someone's paycheck. With immature AI deployments, often the work of the human evolves from one shape to another. As the AI deployment on that task matures, the human role will continue to change. This assumes that the organization is actually investing in continuous improvement, a discipline that is critically lacking in many organizations.
Where the Economics Actually Land
Strip the panic out of either headline and the logic is the same whichever direction it points: who's bearing the cost of the tool, what new value the freed-up time is producing, what the law and the local labor market actually allow, and whether the person doing the work is quietly absorbing more of it for the same pay. Fix the measurement problem AI exposed, and the questions start to answer themselfs, because by the time you can answer it honestly, you already know whether you were buying time, outcomes, or units all along. Skip that work, and you're not managing compensation. You're reacting to a tool, and you're probably about to lose the person who got good at it first.
If you've found a measurement that actually holds up here or are working on this problem, I'd like to hear it. Leave a comment.
Comments
Post a Comment