Age Predicts Who Adopts AI. Skill Predicts Who Benefits.

Before you decide AI means you should hire fewer juniors, I would look at what those juniors can do with it, and at where your next senior people are going to come from.

Those are two different parts of the same decision. You can save money on the work being done today and still leave yourself with nobody learning how to do the work you'll need later.

What I've watched in service firms is more useful than the story about young people understanding AI and older people not getting it. Some firms are adding juniors and giving them AI for work where mistakes are less costly, while keeping experienced people responsible for the decisions that can do real damage.

So the question I would use to sort the work is how expensive it is to get it wrong. Age can tell you something about who reaches for the tool, but it doesn't tell you who should be responsible for what comes back.

There is research behind part of that distinction. In the customer-support study described by MIT Sloan in 2023, the least experienced workers resolved 35 percent more chats per hour with AI assistance, while productivity was essentially flat for those with the most skill and experience.

That was a finding about particular support work, not a rule that experts get nothing from AI. It does tell you that being the best person at the old version of a task doesn't automatically mean you get the biggest gain when the tool arrives.

A junior can have more to gain because the assistant helps with things they haven't learned yet. And the senior who already knew those things can still benefit on different work, research, preparing materials, pulling together information before a decision, which is what I've watched happen in firms using AI well.

Even the adoption story is less neat than the headlines suggest. Slack's 2025 Workforce Index reported that desk workers aged 28 to 43 were more likely to use AI daily than Gen Z workers in its survey.

That's self-reported use in a vendor survey, not a skills test. I'm mentioning it because choosing the youngest person in the room to lead your AI work isn't a sound way to choose, and neither is assuming your experienced delivery lead won't understand it.

Now look at what's happening to entry-level jobs, because the concern about juniors isn't imaginary. In its August 12, 2026 revision of the Canaries paper, Stanford's Digital Economy Lab reported that employment of workers aged 22 to 25 in AI-exposed occupations stood 19 percent below where it would have been if it had kept pace with their less-exposed peers.

That analysis used payroll data through June 2026, and the authors found no comparable gap for experienced workers. They also found that the change was happening mainly through reduced hiring of young people, rather than more people leaving their jobs.

So don't read that as 19 percent of young workers being fired by AI. It's a relative employment gap between groups of young workers, and the researchers also say they find no evidence of widespread, economy-wide job displacement.

The pattern is consistent with AI affecting some early-career work, but it doesn't settle the cause of every hiring decision. What matters for your decision is that a leaner junior layer can look normal in the market without being the right design for your company.

Think about the usual service-firm setup. A junior prepares the work, a senior checks it, and the firm charges enough to cover both people's time and still leave a margin.

AI changes parts of that arrangement because the first pass can take much less effort. Research gets gathered, a report takes shape, a meeting becomes a set of notes, and the junior can prepare more than before.

But a report that looks finished isn't necessarily ready for the client. If every extra report creates another piece of work for the same senior person to repair, you haven't removed the constraint, you've sent more work into it.

This is the strongest objection to keeping juniors, and I wouldn't brush it aside. You may already have tried junior-plus-AI and found that the senior review hours cost more than the junior hours you saved.

That is a real cost, and giving the junior a better prompt doesn't automatically remove it. You need to decide which tasks can be checked in a clear, repeatable way and which ones still need experienced judgment throughout.

For a first pass at meeting notes, the reviewer can compare the actions with the transcript. For a recommendation that changes the client's tax position or commits your firm to a price, checking the wording isn't enough, someone needs to understand the decision and what happens if it's wrong.

That's the risk line I'm talking about. Work that is expensive to undo, can damage a client's trust or creates legal trouble stays attached to someone with the experience to own it, even if AI helps prepare most of the material.

Below that line, juniors can use AI to handle more of the preparation and routine work, with a named person responsible for how the output gets reviewed. Calling it lower risk doesn't mean nobody checks it, it means the check can be designed without asking a senior to repeat the whole job.

And above the line, the experienced person should get the tool too. They can use it for research, drafts and the routine steps around the decision, so more of their time goes into the part the client needs them to get right.

I have watched firms add juniors under that arrangement, because they could take on more of the lower-risk volume while training into the firm's way of working. Those firms were deliberately giving the juniors less of the high-stakes work, not treating a convincing AI answer as a substitute for experience.

There is a limit to how far you can carry that observation. I don't have a staffing ratio that says one senior with AI replaces a certain number of juniors, and the right mix will be different in an agency, an accounting practice and an engineering firm.

But I do think the training question belongs beside this quarter's delivery cost. If the reason your seniors are good is that they spent years doing the simpler work, making mistakes and getting corrected, removing that simpler work changes how the next group learns.

The Harvard Law School Center on the Legal Profession's essay on the training crisis makes that point for law firms, the work at the bottom of the pyramid is also where people learned to reach the top. You can't assume some other employer will keep paying for that training while your firm only hires the finished result.

So I would keep juniors close to the judgment work. Let them review an AI draft, explain what they think is wrong and compare that with what a senior notices, because the difference between those two readings is part of what they need to learn.

That doesn't happen just because the tool saved an hour. Someone has to protect time for the senior to teach, otherwise the junior gets faster at producing things without getting much better at judging them.

And there is another reason to leave room for juniors, they can be the people who find the better way to do the work. I've watched them lean into the tools, try things their seniors hadn't considered and show the rest of the team what was possible.

On one team I watch, a junior handled meeting follow-ups by copying each transcript into an AI chat, asking for a summary and then entering the agreed tasks into the project tool by hand. It took about ten minutes to summarize and twenty minutes to enter the tasks, across about twenty meetings a week.

On the first day the team moved to an agent setup, that junior built a skill that read the transcripts, pulled out the tasks, filed them in the project tool and dated them against what the meeting had agreed. Nobody senior had asked him to build it.

That removed about ten hours of manual work from his week, with fewer mis-dated tasks. That's the observed time saving and the improvement we saw in dates, not a measured claim that every output was correct or that the firm earned ten extra billable hours.

The useful part is that he knew the repetitive work well enough to see what could change. If you only think of him as a cheaper person producing the first draft, you miss that contribution.

Now let me show you where this sorting can go wrong, because judgment can hide inside a task that looks routine. I've watched this in process mapping, inventory and finance, where a junior gets something from AI that looks right until an experienced person reads it.

Take a process map. The junior interviews the staff and gives the transcripts to AI, and the result is a clean account of how the work supposedly happens.

But people have described what they say they do, not necessarily what they actually do. It takes experience to notice that two departments have given answers that don't fit together, before the firm rebuilds the process around a description that was wrong to begin with.

So being easy to undo isn't the whole test. You also need to ask who will notice a mistake, and whether it can keep affecting later work before that person sees it.

In law, tax, healthcare and engineering, more work belongs above the risk line because a plausible mistake can carry a much larger cost. The same sorting idea still helps, but it doesn't give you permission to drop professional review or legal duties.

I would expect sorting recurring delivery work properly to take real time, plan it as work over a quarter rather than something you announce in a memo. Start with the tasks your team repeats, including the boring ones, and sit with the people who do and review them.

For each task, decide what happens if it's wrong, who can check it and who stays responsible. Then give the lower-risk work to the junior with a clear check, and keep the high-stakes decision with the experienced person while helping them with its preparation.

Choose the person who runs this by their knowledge of delivery and their ability to help colleagues change, not their birth year. Give them the authority and time to change the work, because enthusiasm on its own won't clear a review queue.

And make a place for the ideas coming from the team to be tested and shared. The transcript workflow didn't need a company-wide reorganization to teach the people around it something useful, it needed someone to notice it, check it and help it spread.

This assumes your firm actually has a junior layer and someone who can teach and review the work. If everything still runs through you, the problem is how to divide work between you and AI, and that needs a different plan.

Before you remove the next junior role, look at the tasks it contains and the experience someone would gain by doing them. Decide what AI can take over, what the junior should learn instead and who will help them learn it, then make the hiring decision with all of that in view.