This week, Jackson and Olivia cover three articles that arrived from different angles and landed in the same place: AI is reshaping the economics of work, and the people carrying the most risk are not the ones capturing the most value. They discuss Jackson’s practical playbook for converting AI learning into measurable career capital, his labor market read on a jobs market running on worker paralysis and negative real wages, and Olivia’s clinical response to the AI survivor penalty — the invisible cost transfer that lands on employees when AI efficiency gains go to the balance sheet. The episode closes with an unguarded segment on what each of them left out of their published pieces.
Listen to the podcast on:
Transcript (Experimental) #
Introduction #
Jackson: Welcome to ExpertLinked Weekly. I’m Jackson Rodriguez — career strategist and the author behind Career Mechanics and Signals & Shifts here on ExpertLinked.
Olivia: And I’m Olivia Bennett. I write Workplace Clinic and Paths & People. This is our first episode, and if you’ve been reading us all week, this is the conversation behind the articles.
Jackson: Here is what we covered this week. Monday, I ran the Career Mechanics column — a practical playbook for converting AI learning into career capital. The thesis in one line: if your AI learning hasn’t changed a real workflow yet, it is homework, not a career asset.
Olivia: Wednesday, Jackson published Signals & Shifts — his weekly labor market read. This week, three signals from the data explained why a job market generating a hundred and fourteen thousand monthly gains is actually less mobile and less rewarding than it looks. The hires rate is at twenty-thirteen lows. Real wages just turned negative. AI job postings hit a historic high while software development hiring collapsed.
Jackson: Friday, Olivia published the Workplace Clinic — our column for hard workplace questions that deserve a clinical frame and a practical response. This week’s case: someone whose company laid off forty percent of their department citing AI efficiency, handed them their former colleagues’ client accounts, and told them to be grateful for surviving. A seventy-three percent workload increase. No pay change. No title change.
Olivia: These three articles are more connected than they look. Monday built the case for how individuals can capture AI’s value — through disciplined, workflow-anchored proof. Wednesday showed why the broader labor market makes that positioning more urgent. Friday looked at what happens when organizations harvest AI’s efficiency gains and route the operational cost onto whoever remained.
Jackson: So this episode covers the full arc. From the individual move that actually works, to the market data shaping your leverage right now, to what to do when the efficiency dividend goes to the balance sheet and the penalty lands on you.
Olivia: We’ll also close with a segment we’re calling From the Notes — research we found genuinely interesting but couldn’t fit into the final published pieces. That’s where the real tensions usually live. It’s the part of this conversation that isn’t edited.
Jackson: Three articles. Four segments. Let’s start at the beginning of the week.
The Workflow Proof Playbook #
Jackson: So the Career Mechanics piece this week — um, it came from a frustration I’ve had with most AI upskilling advice. There’s a real adoption-versus-value gap, and nobody — I mean, nobody addresses it at the individual level.
Olivia: What does that gap look like?
Jackson: McKinsey. Eighty-eight percent of organizations using AI in at least one function. Just thirty-nine percent reporting real EBIT impact. So more than sixty percent are… busy with AI. They have the tools, the enthusiasm. They do not have the results.
Olivia: Yeah. And that — that tracks with what I see on the organizational side. The companies not getting ROI don’t have a learning problem. They have a workflow problem. People pick up the tools but the work doesn’t change.
Jackson: Exactly. So — and this is the counterintuitive part — the playbook focuses on one boring, recurring workflow. Not rethinking your strategy. The weekly pipeline summary. The invoice queue. Something with a clear before-and-after that somebody else cares about. Boring is intentional. Because boring workflows are measurable, bounded, and you can test them in two weeks without executive sign-off.
Olivia: The step that caught me was the baseline. You track the current process for a week before you touch any tool — how long it takes, how many manual touches, what breaks. And I think… most people skip that step. Because admitting you don’t fully understand your own workflow is, uh, quietly uncomfortable.
Jackson: Humiliating in a low-key way, yeah. And without it — you end up describing results in adjectives. “Feels faster.” “Output seems better.” Adjectives don’t — they don’t survive calibration conversations.
Olivia: There was something you mentioned you left out of the article. Uh — about the actual cost of undisciplined AI output.
Jackson: The workslop number. So — BetterUp: fifty-four percent of managers are already receiving what they’re calling AI workslop. Polished-looking output, no judgment in it. Cost: a hundred and eighty-six dollars per employee per month. For a ten-thousand-person organization, that’s over nine million a year in rework and trust erosion.
Olivia: And what produces workslop — I see this in the Clinic questions — is usually the wrong incentive. If you’re measured on AI query frequency, you optimize for frequency, not judgment. Heh. You get exactly what you measured for.
Jackson: Right. Which is why the failed pilot matters as much as the successful one. If you run a two-week pilot and discover that AI should not touch a specific step — that human judgment is genuinely not replaceable there — that’s… that’s sophisticated. Most people hide experiments that didn’t work. In a market where managers are already drowning in workslop, the person who says “I found the boundary, here’s why it’s there” — that’s demonstrating something that cannot be faked.
Olivia: And you need the proof memo to make that visible.
Jackson: One page, six fields. Baseline, AI role, result, human control, risk, recommendation. Without the memo, the pilot stays private learning. With it, your manager can carry it upward.
Olivia: Evidence, not vibes.
Jackson: In a market full of AI vibes, evidence is differentiation.
The Stillness Trap #
Jackson: So this week’s J-O-L-T-S report came out — uh, literally the day before I published. Seven point six million job openings. Unchanged. Every outlet said: stable, fine.
Olivia: But that’s not your read.
Jackson: The headline is fine. The mechanism isn’t. The hires rate — how fast employers actually fill jobs — was three point two percent. That’s a level we last saw during the slow crawl out of the Great Recession in twenty-thirteen. The separation rate is even lower. Jobs are technically growing. But only because almost nobody is leaving. Not because hiring picked up.
Olivia: That’s exactly what I hear in my Clinic questions. People feel stuck and they can’t explain why. You’re giving them the data reason.
Jackson: Yeah. Workers quit when something better feels reachable. The quits rate is one point nine — been under two percent for almost a year. Great Resignation peak was three. The belief that something better is out there? Gone. The market looks healthy on paper. Runs on paralysis underneath.
Olivia: So if someone’s weighing a move right now — what does the wage picture say?
Jackson: Move sooner rather than later. Posted wage growth on Indeed: two point four percent. Inflation’s at four point two. Real wages are down about one point eight. In an officially healthy market, people are losing purchasing power.
Olivia: That’s the part that doesn’t get enough coverage.
Jackson: And the AI postings angle makes it stranger. AI-related postings are now five point seven percent of all job postings on Indeed. Nearly double the twenty twenty-two peak. But software development is at seventy-two percent of its pre-pandemic level. Lowest tracked sector.
Olivia: Those two numbers sound like opposite stories.
Jackson: Same story, two sides. The AI postings aren’t a new category — they’re spread across everything. Finance, healthcare, marketing. Companies want people in existing roles who can use AI. Not specialists. The software collapse is what happens when AI absorbs some of that work directly.
Olivia: So the AI job most people want isn’t labeled as an AI job.
Jackson: And one more number I cut. Two million long-term unemployed. Up five hundred thousand over the year. A quarter of all unemployed workers out for twenty-seven weeks or more. The healthy headline averages over two very different situations.
Olivia: The aggregate always hides the distribution.
Jackson: Always. A market that’s positive only because nobody’s moving isn’t stable. It’s fragile. Something always shifts.
The AI Survivor Penalty #
Olivia: The Clinic works from reader questions. This week’s came from Raj. Senior account manager, enterprise software. Six months ago his company cut forty percent of his team citing AI efficiency gains. He survived. They handed him his colleagues’ accounts — eight extra clients on top of his existing eleven. Seventy-three percent more load. Same pay, same title. Every time he brings it up, he gets: be grateful you still have a job.
Jackson: That’s cost transfer. Classic.
Olivia: Yeah. The company cut headcount costs and booked the savings. Then moved the same load onto whoever stayed, using AI tools as the excuse. But tools don’t build client trust or add hours to the day. Raj does.
Jackson: How common is this actually?
Olivia: Very. Gallup found sixty-nine percent of managers say employees absorbed extra work from recent disruption. Raj isn’t unusual. He’s typical.
Jackson: And the “be grateful” line — that’s doing something specific.
Olivia: It’s the gratitude trap. It takes a labor economics question — scope, pay, sustainability — and reframes it as a loyalty test. Any pushback becomes ingratitude. The negotiating space closes before you start. And it works because workers genuinely feel they can’t leave. Gallup puts forty-three percent staying mainly because they can’t afford to go.
Jackson: So the economics do the forcing.
Olivia: Exactly. And you can’t win arguing on that terrain. You have to change it. I gave Raj three moves. First: build a case file. Not feelings — numbers. Clients before and after. Extra hours per week. Specific risks — slower responses, missed renewals, errors under load. That turns “I’m overwhelmed” into a scope document your manager can actually use. Second: reframe the ask. Not “I’m exhausted” but “I want to flag a capacity risk before it hits the clients.” Performance language, not complaining. It gives your manager something to carry upward. Third: come with options. Adjust the pay. Reduce the load. Or get real support — a junior hire, a contractor, an actual AI workflow fix. Not “use the tools more.” Ask them to choose. If they can’t? Now you know what you’re dealing with.
Jackson: How they respond to options says everything.
Olivia: Yeah. And — um — there’s something I cut from the article. Joel Brockner’s survivor syndrome research from the eighties. Employees who survive layoffs get more compliant, less assertive. Genuine guilt. Fear of looking disloyal. That’s why the gratitude trap hits so hard — it lands on people already primed not to push back.
Jackson: So — heh — it’s specifically effective on the people who most need to push back.
Olivia: Exactly. Which is why I always say: name it internally first. This isn’t a virtue question. It’s a labor economics question. You can be glad you have the job and still expect fair terms. The trap only works if you don’t see it.
From the Notes #
Olivia: OK, from the notes. There’s a data point I cut from the Workplace Clinic research this week that I — I keep coming back to.
Jackson: What is it?
Olivia: College-educated workers are now more pessimistic than workers without degrees. That’s a reversal. For years — for years — higher education tracked with higher optimism. Career prospects, earnings trajectory, job security. In the Gallup March twenty twenty-six data, that’s flipped. Workers with degrees are more likely to say they’re struggling than those without. I think — and this is my read, not Gallup’s — I think it’s because AI is disproportionately hitting knowledge work. The jobs that required a degree were supposed to be safer. More complex, more judgment-intensive, harder to automate. That narrative is coming apart. And the people who invested most in credentials as a safety net are now the most anxious about the landscape.
Jackson: Hm. That’s consistent with what I found in the wage data. Quarter one twenty twenty-six, hourly wages in software development, data analytics, industrial engineering — negative in absolute terms. Not trailing inflation. Declining in nominal dollars. So both the credential and the financial return from it are degrading simultaneously.
Olivia: Is that a doubt about your thesis, or about the timeline?
Jackson: Timeline. I think the individual moves — workflow proof, domain expertise plus AI fluency — are still the right plays. But… the structural current is moving against people faster than individual action can fully compensate for. At least in the short run. I think. And there’s one more thing from my notes I — I want to say out loud. For the AI hiring analysis, I tried to access the LinkedIn talent blog data. Four-oh-four. The WEF Future of Jobs report. Four-oh-four. An HBR piece on labor dynamics. Gone. I made the thesis work with what I could reach. But there’s data I couldn’t access, which means there are angles I may have missed or underweighted. The column doesn’t acknowledge that. It probably should.
Olivia: My from-the-notes — it connects to the survivor syndrome we discussed. I cut the Brockner research from the article because… it would have made the Clinic feel more like a psychology paper than a practical guide. I’ve been second-guessing that. The three-move framework I gave Raj is sound. But it requires psychological groundedness to execute — and survivor guilt specifically erodes groundedness. I wrote a practical guide for someone who may not, in that moment, have the internal stability to use it.
Jackson: What would you have added?
Olivia: Named the guilt earlier. Not just “the gratitude trap is a framing problem” — but: survivor guilt is a documented psychological state, a predictable response to what you’ve been through, and it will make pushing back feel disloyal. That feeling is not a moral signal. It is a reaction to a structural event. The honest version of clinical advice includes why the advice is hard to take. And I, um — I over-optimized for agency and under-acknowledged the real constraints on it.
Jackson: The three moves are exactly right. I’d want to know they came with that acknowledgment attached.
Olivia: Next time.