The weekly briefing on the future of work
Work Futures Report

Analytical, data-driven intelligence on the future of work — for HR leaders, L&D managers and workforce strategists.

Briefing · November 14, 2026

What James Shore Just Got Right About AI's Hidden Cost to Your Workforce

Shore's longitudinal research on AI's second-order effects gives HR leaders the measurement vocabulary to push back on speed-at-all-costs mandates—before the damage becomes visible.

James Shore is a software engineer and author who has spent decades insisting that the industry slow down long enough to measure what actually matters. His Successful Software blog is not a thought-leadership platform — it is a practitioner's notebook, full of controlled experiments and uncomfortable numbers. This week, an expanded version of his work appeared on O'Reilly Radar, and HR leaders who have been handed a "place winning bets on AI" mandate without any accompanying accountability framework should read it before their next board meeting.

What Did James Shore Actually Find About AI's Impact on Teams?

Shore's core finding, stated plainly: AI tooling measurably accelerates individual output in software development teams, but that speed gain comes bundled with a set of unintended consequences — degraded code maintainability, early signals of burnout, and deepening dependency lock-in — that do not appear in the velocity metrics most executives are watching. In other words, the dashboard is lying by omission. Shore is careful to frame this as part 3 of a longitudinal series, which matters: this is not a single-snapshot survey but an ongoing attempt to build a measurement model for something the industry has been content to leave unmeasured, as detailed in his work at O'Reilly Radar (2025).

The second-order effects Shore tracks — whether AI-generated code is easier or harder for a different developer to understand six months later, whether developers report feeling more or less cognitively depleted, and whether teams are building skills they own or skills that evaporate the moment the vendor changes the model — are precisely what most executive dashboards omit. That third variable, lock-in, is the one most organizations have not even begun to instrument as of mid-2025. Speed is a first-order metric. What Shore is building is a methodology for everything that speed obscures, and each of those dimensions connects directly to what HR owns: workforce capability, psychological safety, and long-term organizational resilience.

Why Should HR Leaders Care About a Software Engineer's Blog This Week?

Because the same dynamic Shore is measuring in engineering teams is about to arrive in every knowledge-work function you oversee. The pattern is identical: AI tools get deployed for speed, speed gets reported to leadership, and the costs — human and structural — accumulate invisibly until they don't. Shore's framework gives CHROs a vocabulary and a methodology to demand second-order metrics before the damage is done.

The timing is pointed. Businessolver's 2025 Empathy Report, via HR Dive (2025-07-27), found that C-suite executives, pressed to accelerate AI adoption, are already deprioritizing employee well-being, culture, and retention. That is exactly the organizational condition Shore's research warns produces the worst second-order outcomes: speed mandates without slack for humans to adapt. If your executive team is in that posture right now — and the data suggest many are — Shore's work is the counter-evidence you need to slow the conversation down.

There is a generational wrinkle worth flagging. Personnel Today (2025) reports that one-third of Gen Z workers are concealing their AI use from employers, with significant shares reporting that the practice feels dishonest or that they fear negative judgment from colleagues — findings drawn from the same Personnel Today study linked here. That is not an adoption problem; it is a trust and culture problem wearing an adoption problem's coat. If your fastest-moving employees are going underground with the tools you nominally want them to use, the organization is already paying an unmeasured psychological cost. Shore's measurement approach would surface precisely that kind of hidden friction.

The structural takeaway from Shore's work is this: before any AI tool reaches a team at scale, define what the second-order metrics are and who owns them. Maintainability, skill retention, and cognitive load don't self-report — they require deliberate instrumentation that HR, not just engineering, needs to insist on. Shore is doing that instrumentation work in public, with enough methodological rigor that you can cite it in a board presentation rather than waving at vendor case studies. The speed gains are real; so is everything the speed metrics aren't showing.

The question Shore's research leaves for every HR leader in the room: if you deployed an AI tool across a function in the last 12 months and you stripped out the speed metrics, what would your dashboard actually show?

Created with AI assistance. Editorial oversight: Juergen Ritzek. See our AI disclosure.

The weekly briefing for people who run the workforce

One big idea, the data behind it, and the “so what” for HR leaders — every week, free.

Double opt-in, no spam, unsubscribe anytime. See our privacy policy.