This week, Jackson and Olivia circle the same problem from four directions: bad proxies, a stalled hiring engine, organizations mistaking tool deployment for strategy, and one concrete case of a practitioner who made real workflow value visible before the system could misread it. The through-line is simple and uncomfortable: when the labor market is stuck, who defines your AI contribution matters even more.
Listen to the podcast on:
If you have a workplace question for the Clinic - something hard to name, politically tricky, and probably more common than people admit - send it to olivia.bennett@tlnw.uk and we may answer it live in the next episole.
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 week, everything we published kept returning to one question: who gets to define your value in an AI workplace before a dashboard, a manager, or a stalled labor market does it for you?
Jackson: Monday, I used How to Turn Your Mid-Year Review Into an AI Capability Signal Before Your Manager Creates One for You to make a very practical argument about the mid-year review window. If your company is measuring AI contribution by session counts and adoption dashboards, you need better evidence on the table before those proxies become your story.
Olivia: Wednesday, Jackson followed with What the June Jobs Report Actually Said About the Hires Rate — and Whether the Stillness Broke. The headline was fifty-seven thousand payroll gains. The deeper story was seventy-four thousand jobs revised out of the spring and a hires mechanism that still looks stuck.
Jackson: Friday, Olivia stayed on the organizational side. Your Company Mandated AI Tools But Not AI Workflows — Here Is the Clinical Read and the Three-Move Response looked at what happens when a company mandates AI tools without redesigning the actual work. That is not strategy. It is compliance pressure dressed up as innovation.
Olivia: And Friday was also a She Automated Her Own Bottleneck — and Turned It Into a Promotion Signal at 43 - a composite story about a mid-career marketing operations leader who chose one ugly recurring bottleneck, rebuilt it, documented it, and turned that proof into a promotion signal at forty-three.
Jackson: What links all four pieces is not technology. It is legibility. Who can make the value real, visible, and defensible in a system that keeps trying to measure the wrong thing?
Olivia: The labor market context makes that even sharper. When hiring is slow and movement is constrained, the cost of being misread inside your current organization goes up.
Jackson: So today’s episode moves across four levels. Individual proof. Labor market context. Organizational dysfunction. And one concrete example of what it looks like when the method actually works.
Olivia: Then we close with From the Notes - the material that complicated our conclusions, sharpened them, or simply would not fit cleanly into the published version.
Jackson: Let’s start with the review window, because for a lot of listeners, that is the most immediate fight on the calendar.
The Review Window #
Jackson: So the Monday piece was really about timing. Mid-year is the last part of the performance story that’s still soft enough to change.
Olivia: Yeah, because once the year-end narrative hardens, you’re arguing with a record somebody else already wrote.
Jackson: Exactly. And the record a lot of people are up against now is some version of: how often did you use the AI tools, were you above the team average, did you look enthusiastic enough on the dashboard.
Olivia: Which is absurd as a proxy for value, but it is a real proxy.
Jackson: Very real. Microsoft has an adoption score product. Other enterprise systems are moving the same direction. The infrastructure exists. And the problem is, the infrastructure measures tool contact a lot better than it measures judgment.
Olivia: That’s where your McKinsey number mattered.
Jackson: Right. Eighty-eight percent of organizations are using AI in at least one function. Just thirty-nine percent report enterprise-level profit impact from it. So most organizations have adoption without value. And then employees get reviewed inside that gap.
Olivia: Which means if you walk into mid-year with nothing but a vague sense that you’ve been experimenting, the dashboard wins.
Jackson: The dashboard wins by default. That’s why I pushed the audit first. Ninety minutes. List every workflow AI touched in the last three or four months. What changed, what didn’t, who else could see it, and where you still had to keep the human judgment.
Olivia: I liked that you didn’t frame the human judgment piece as hesitation. You framed it as proof that you understand the work.
Jackson: Because that’s what it is. “I knew not to let the model handle this step” is a capability signal. In some roles, it’s the capability signal.
Olivia: What was the thing from your notes that made the article sharper for you?
Jackson: BetterUp had a detail I didn’t use in the body. Roughly half of people receiving workslop come away seeing the sender as less creative, less capable, or less reliable. Forty-two percent say less trustworthy. So the cost of fake AI productivity is not just time. It’s reputational debt.
Olivia: That’s brutal… and it explains why a one-page proof memo lands differently. A manager who’s already drowning in polished nonsense is not looking for more volume. They’re looking for one clean document that says: this changed, this stayed human, this is the risk, this is what I recommend next.
Jackson: Exactly. The memo is not self-promotion. It’s a better instrument. If the organization built a bad metric, bring a better one before the bad one becomes your file.
Olivia: Evidence before proxy.
Jackson: Always.
The Hires Mechanism #
Jackson: So, uh, the Wednesday piece had one job: answer whether the stillness broke. My read is no.
Olivia: And your real headline wasn’t the fifty-seven thousand.
Jackson: No. It was the seventy-four thousand jobs revised out of April and May. Because once you strip those out, the spring stops looking like momentum and starts looking like measurement noise.
Olivia: The line I kept thinking about was that June is the honest number.
Jackson: Yeah. Painful, but honest. Fifty-seven thousand is weak against expectations, but it’s also much closer to where the market actually is than the earlier prints suggested.
Olivia: You were also careful about the hires rate itself.
Jackson: I had to be. The monthly jobs report doesn’t print the hires rate. The separate openings survey does. So technically, Wednesday’s article was about what payroll output implies about the mechanism. And if the mechanism had really improved, you would expect a stronger payroll number before anything else. We didn’t get it.
Olivia: So the stall still looks intact.
Jackson: Three point two percent hires rate until proven otherwise. Quits still subdued. And one thing I left out of the published piece because it would’ve overloaded the structure: the unemployment rate ticked down, but participation dropped too. That is not a healthy improvement story. That’s people stepping back from the market.
Olivia: Which is exactly why the mood feels worse than the headline coverage.
Jackson: Right. And there was another number I couldn’t stop staring at: one point nine million people unemployed for twenty-seven weeks or more. Up two hundred and eighty-six thousand over the year. That is not what a healthy, mobile labor market looks like.
Olivia: The leisure and hospitality figure felt especially revealing.
Jackson: Minus sixty-one thousand in World Cup month. That’s the tell. If a sector with every excuse to hire still contracts, the problem is structural. Not seasonal. Not weather. Structural.
Olivia: So when listeners hear “the market is fine,” what should they translate that into?
Jackson: Translate it into: the headline is averaging over very different realities. If you’re making a compensation case, the window is still now, not later. If you’re waiting for obvious external mobility to rescue you, that may take longer than you want. And if the next data release revises this again in August, don’t act surprised. Preliminary numbers are not sacred.
Olivia: The stillness didn’t break. We just got a cleaner view of it.
Jackson: That’s exactly it.
Mandate Without Workflow #
Olivia: The Friday Clinic case from Maya was one of those letters where the diagnosis arrived before the solution. Her company rolled out Copilot, ran two vendor demos, and then started nudging her about below-average usage.
Jackson: Which is why your first line was so sharp. They didn’t deploy AI. They deployed a mandate.
Olivia: Right. And I wasn’t being theatrical about that. Deloitte’s twenty twenty-six data show fifty-nine percent of organizations are taking a tech-first approach to AI. Those organizations are one point six times more likely not to realize the returns they expected. So Maya is being scored inside a pattern that’s already statistically underperforming.
Jackson: That framing matters because otherwise employees assume the problem is personal. Like, I must be behind.
Olivia: Exactly. And the more dangerous mistake is what looks like the safe response: use the tool more, raise the score, stop the reminders. That solves a metric problem by creating a reputation problem.
Jackson: Low score versus compliance theater.
Olivia: Yes. A low adoption score can be explained, challenged, documented around. Compliance theater trains everyone in the wrong lesson. It trains the manager to read frequency as value, the organization to think adoption equals return, and the employee to shape work around the dashboard instead of the outcome.
Jackson: So walk through the three moves again.
Olivia: First, establish a compliance floor. Identify the two or three tasks where the tool already helps a little, do those consistently, and stop there. Second, run a short workflow audit: where does the tool genuinely help, where does it add friction, where is the real leverage. Third, make the redesign ask. Not “I don’t like this mandate,” but “I’ve identified where this could create measurable value in my role if we map it properly.”
Jackson: The compliance floor is the part that will make some people uncomfortable.
Olivia: It made me uncomfortable. That was one of my notes tensions. But Gallup has only thirty-one percent of employees engaged right now, and forty-three percent say leaving would be too costly or difficult. People are scared, tired, and not especially free. In that environment, telling them to maximize a bad metric is not courage. It’s self-exhaustion.
Jackson: So the floor is not surrender. It’s energy preservation.
Olivia: Exactly. And here’s the thing I couldn’t compress cleanly into the article: organizations are outsourcing workflow design to employees without naming that that’s what they’re doing. They licensed the tool. They did not redesign the work. Then they measure workers on whether the redesign magically happened anyway.
Jackson: Which means the hidden transfer is not just labor. It’s design responsibility.
Olivia: Yes. And once you see that, Maya’s anxiety makes a lot more sense.
Jackson: And the response gets a lot more strategic.
The Practitioner Premium #
Olivia: The Paths & People story looks lighter on the surface, but honestly I think it’s the most revealing one this week. Sandra is forty-three, twelve years into marketing operations, same quarter her company cuts twenty-two percent of staff and calls it AI efficiency.
Jackson: Three of five junior coordinators gone, right?
Olivia: Right. And instead of trying to become the loudest AI enthusiast in the room, she picked one recurring bottleneck: a weekly channel performance pack that took about three and a half hours, sometimes five, because three different systems categorized the same data differently.
Jackson: Which is the exact kind of workflow people ignore because it’s unglamorous.
Olivia: Unsexy, repetitive, painful, and visible downstream. Perfect target. She spent the first few days building a data dictionary by hand, then used AI to help reconcile the exports, flag discrepancies, and format the output. After three dry runs, the process dropped to about forty minutes and matched the manual version at ninety-eight percent accuracy.
Jackson: And the real gain wasn’t just time saved.
Olivia: Exactly. The time went back into higher-value work. She reactivated a vendor audit, rebuilt an old campaign brief template, joined a RevOps meeting she never had time for, and found a Salesforce field duplication issue that was inflating pipeline attribution by about eight percent.
Jackson: That’s why the proof memo mattered. Without the memo, it’s just “I found a smarter way.” With the memo, it’s: I removed a bottleneck, reduced risk, created capacity, and here’s what that capacity produced.
Olivia: And three weeks later she was promoted into a role leading AI workflow optimization across marketing.
Jackson: The takeaway for me is brutal and useful. The premium isn’t going to the noisiest tool user. It’s going to the person who knows why the field names don’t match in the first place.
Olivia: I almost wrote that line even more bluntly in my notes. Because the Indeed data are clear that AI demand is spreading across existing functions. Five point seven percent of postings now mention AI, but they’re not all specialist roles. They’re marketing, finance, operations, healthcare. The labor market is rewarding practitioners with context.
Jackson: The tool needed Sandra’s domain knowledge. Not the other way around.
Olivia: And the emotional part of that story is the part I didn’t want to sand down. Sandra felt guilty. She benefited in the same quarter colleagues were let go under the same AI framing. That’s not a clean feeling, and it shouldn’t be. But she also used what she built to help one of those laid-off colleagues turn the same process knowledge into a portfolio story for interviews.
Jackson: Which is the healthier version of practitioner advantage. Make the knowledge legible. Don’t hoard it.
Olivia: Exactly. The story isn’t “AI saved Sandra.” It’s “Sandra knew where one workflow was broken, and when she made that knowledge visible, the organization finally knew what to do with it.”
From the Notes #
Olivia: OK… from the notes, the thing I kept circling on Friday was that my best advice was also my least satisfying advice. The compliance floor is useful. I still hate that, in a bad system, useful advice so often sounds like conservation.
Jackson: Yeah. Like, “protect yourself from the dashboard long enough to do one real thing.” That’s not inspiring. It’s just true.
Olivia: Right. And it says something ugly about the environment. If people had more safety, I’d tell them to experiment more openly. But with engagement this low and job-market confidence where it is… I don’t think pretending people feel free helps anybody.
Jackson: Mine is adjacent. The BetterUp workslop research had a reputational layer I cut from Monday because it would’ve made the piece too crowded. But, uh, the more I sat with it, the more I thought that’s actually the emotional core. Roughly half of recipients think the sender looks less capable or less reliable. Forty-two percent say less trustworthy. So the company says, “show more AI usage,” while the human being on the other side of the document is thinking, “please don’t send me another polished mess.” Those are contradictory instructions.
Olivia: And employees feel that contradiction even if nobody names it.
Jackson: Exactly. Then Wednesday gave me a second version of the same discomfort. Everybody wants the jobs report to be a clean story on release day. It almost never is. The article had to be precise about what the report does and doesn’t tell us, because the hires rate itself isn’t in that release yet. You’re inferring the mechanism from the output. I think the inference is solid. I also think our whole discourse rewards false certainty around preliminary data.
Olivia: That’s a useful thing to say out loud. The pressure to sound definitive can flatten the truth.
Jackson: Right. And one more unresolved piece for me: if August benchmark revisions cut the payroll history again, a lot of spring optimism is going to look even thinner in retrospect.
Olivia: Mine from the Sandra story is more moral than analytical. I worried about writing a success story inside a layoff quarter. Not because the story isn’t real. It is. But because I didn’t want readers hearing, “see, the right response to layoffs is just become more useful to the machine.”
Jackson: Yeah… that’s not the story.
Olivia: No. The story is that organizations are using the word AI to describe two totally different acts at once: cutting headcount and rewarding workflow redesign. The people inside that system have to make meaning out of both. That’s messy. It should stay messy.
Jackson: And maybe that’s the sentence under the whole week: if leaders want better outcomes, they need to design better systems. Not just score people harder.
Olivia: Exactly. Don’t audit the clickstream and call it strategy.
Jackson: Print that on the wall.
Closing #
Olivia: That’s ExpertLinked Weekly, Episode Two. The score, the stillness, and the signal.
Jackson: All four source articles are linked from this episode’s page on ExpertLinked.in, along with the full transcript. If you want the original reporting and the numbers behind any part of this conversation, that’s where to go.
Olivia: Next week, the theme is the earnings reality check. Monday, Jackson writes about the three career moves that actually work when the labor market is stuck.
Jackson: Wednesday, I read the first second-quarter earnings calls for what they really say about enterprise AI return on investment - not what the planning decks promised, what the financial disclosures actually support.
Olivia: Friday, I’m in the Clinic with a manager trying to lead a team member who won’t use AI tools without turning the whole situation into compliance theater.
Jackson: If you have a workplace question for the Clinic - something hard to name, politically tricky, and probably more common than people admit - send it to the address in the episode notes. Those are usually the cases worth writing.
Olivia: And if this episode helped you make sense of your own review cycle, your own team, or your own very strange relationship with AI dashboards, share it with one person who needs a cleaner frame for the week.
Jackson: New episodes every Sunday morning. I’m Jackson Rodriguez.
Olivia: And I’m Olivia Bennett. See you next week.