← All issues
Field Notes · Issue 010

Challenger, Gray & Christmas July 2026 job-cut report (released the week of Aug 3-7, 2026): 33,429 announced cuts, a two-year low; AI the most-cited reason for the fifth straight month at 10,970; hiring up about 25% year over year.

August 3-7, 2026

Five pieces this week, and by Friday they had folded into a single argument. A leader looks at something reassuring on the surface, a calm board meeting or a headcount cut dressed up as strategy, and takes it for the truth sitting underneath. This issue is about the distance between the two.

Field Notes — August 8, 2026
This week's reading
The Field Note

The week, read against the grain

Challenger, Gray & Christmas July 2026 job-cut report (released the week of Aug 3-7, 2026): 33,429 announced cuts, a two-year low; AI the most-cited reason for the fifth straight month at 10,970; hiring up about 25% year over year.

Challenger, Gray and Christmas put out its July job-cut report this week, and the line that traveled was that artificial intelligence led every other reason for layoffs for the fifth month in a row, at 10,970 cuts. Read only that and you get the story a lot of executives have been telling all year, the one where the software is steadily emptying the building. Read the rest of the same report and the story loses its footing. Total announced cuts came to 33,429, the lowest monthly figure in two years, and hiring ran about twenty-five percent ahead of last year. Andy Challenger put it flatly: AI is shifting the labor market, not dismantling it.

Set that next to the week we just spent. One piece looked at boards that watch a leadership team perform cohesion for a single rehearsed hour and then report, accurately, that the team looked sound. Another followed executives forecasting an AI employment collapse after logging about ninety minutes a week with the tool. A third took apart how fast a silent room gets read as an aligned one. What connects them is that the convenient reading keeps getting mistaken for the real one, and the convenience is usually doing the choosing. "AI made us do it" is a cleaner memo than "we were cutting these roles anyway and the moment gave us cover." Reporters have taken to calling that second thing AI washing, and the tell never changes: the reason gets named with far more confidence than the changed work behind it can be shown.

In your last headcount decision that you pinned on AI, can you name the specific tasks a model now does that a person used to, and show that the work itself actually moved?
Sources
  1. Challenger, Gray & Christmas. (2026, August 6). Challenger report: Layoffs fall, hiring picks up; AI leads for fifth straight month [July 2026 report]. (33,429 announced cuts, the lowest monthly total in two years; 10,970 attributed to AI, 33% of the month's total and the fifth consecutive month AI led; 16,095 hiring plans announced. These are ANNOUNCED cuts tracked from public statements, not executed layoffs.) https://www.challengergray.com/blog/challenger-report-layoffs-fall-hiring-picks-up-ai-leads-for-fifth-straight-month/
  2. Built In. Did AI take your job? The truth about AI washing. (Reporting on employers attributing to AI the workforce reductions they had other reasons to make. Secondary source, cited for the term and the pattern rather than for any figure.) https://builtin.com/articles/ai-washing-layoffs
High Road Conversations
Podcast
High Road Conversations

The episode we are pointing people back to this week is Hanna Bauer's, the one we called Declared Dead at 10. Hanna was pronounced dead as a child and built a life on the far side of that, and the conversation is less about the near-death than about what she chose to do with time she was not supposed to have. Watch it here:

Listen →
Lunch and Build
Skool
Lunch and Build

I don't just talk about Agile and leadership, I put it into practice in my Skool, building and shipping real products with Claude every Thursday at 12:30pm EST.

Join us →
From the book
Agile Sucks!

The thread running through this week, mistaking a reassuring surface for the real thing, is the whole premise of the first chapter of Agile Sucks! (When You Do It Wrong). James and I called it the successful failure, the organization posting healthy Agile metrics while producing nothing the business can actually use, everyone admiring a green dashboard that measures the wrong thing. If these five pieces landed, that chapter is where the pattern gets its name.

Get the book →

Get Field Notes in your inbox.

A short read every Saturday morning. No spam, unsubscribe anytime.

Subscribe