The reason the job numbers look calm is that jobs are the wrong unit. Nothing about automation has ever eaten a job. It eats tasks, and a job is just a bundle of tasks with a title stapled to the front.

Take any role you know well and pull it apart. An accountant isn’t doing accounting, they’re doing eleven different things: pulling data, checking it against something, formatting a report, explaining the report to someone who won’t read it, chasing a person who owes an answer, judging a gray case where the rule doesn’t quite fit, and so on. A lawyer, a designer, a nurse, a sales rep, all the same structure. The title is a marketing summary of the bundle. The work is the list.

Automation arrives at that list one line at a time. It takes the pulling and the checking and the formatting, because those have clear inputs and clear outputs and lots of examples. It leaves the gray case and the awkward conversation, because those don’t. And here’s what makes this invisible to every measurement we have: the title doesn’t change. The headcount doesn’t change. The person still comes to work, still says accountant when asked, still appears in the statistics as one employed accountant. What changed is the inside.

What does hollowing feel like from inside? Not like unemployment. Two things happen, and they pull in opposite directions, which is why nobody agrees about whether this is good. The first is relief, and it’s real. The tedious portion shrinks, you spend your day on the parts that need a person, and for a while that’s the best your job has ever been. The second is that the volume goes up, because the work you’re now able to do in a day is the work that used to take four days, and no organization has ever responded to that by asking for less. So the bundle refills, with more of the hard part, at a higher tempo, permanently.

Then a third thing happens, later, and it’s the one that matters for this series. When enough tasks come off the list, the remaining tasks stop justifying the same number of people. The team doesn’t get fired, it stops getting replaced. Someone leaves and the role isn’t backfilled, and the work is absorbed, and nobody experiences a layoff. Attrition is how organizations do this, because attrition is quiet, costs nothing, and requires no announcement. If you’re looking for the news story, the news story is a job posting that never gets written.

This is also why the public argument about it is so unproductive. One side points at the employment figures and says nothing is happening, which is true of the figures. The other side points at their own hollowed-out week and says everything is happening, which is true of the week. Both are describing the same process from different distances, and the figures are simply blind to changes inside a bundle. We built the statistics to count people with titles, in an era when a title told you what someone did.

Now the honest counterweights, and there are several. Task automation has been happening continuously for two centuries and the bundles keep refilling with new tasks, which is why we have jobs our grandparents couldn’t have described. The parts that are hardest to automate, judgment, relationships, responsibility, physical dexterity in messy places, are also the parts most people say they value in their work, so a hollowed job can be a better job. And plenty of current claims about what these systems can do collapse on contact with a real workflow, where the input is a badly scanned document from a supplier who ignores your file format.

What I’d hold against all of that is the shape of what’s being taken. Previous waves took a category and left the rest of the bundle standing, because a loom does one thing. A general system takes items from every bundle at once, and it keeps coming back for more of them each year, which means the refill has to outrun a moving line rather than a fixed one. That may still happen. It’s just a different bet from the one the last two centuries won.

Tonight’s exercise, and please do it with your actual week rather than your job description. Write down every distinct task you performed in the last five working days. Aim for fifteen lines. Now mark each one with whether a machine could do a passable version today, a rough version today, or nothing. Count the marks. The percentage you get isn’t a prediction about your employment, and I’d distrust anyone who told you it was. It’s something more useful: it’s the shape of your job, and you’ve probably never looked at it directly. Tomorrow we look at what happens to the people who were supposed to learn that job by doing its easiest parts.