Our Take
The headline warns of risk without evidence; Fortune reports a concern, not a measured outcome.
Why it matters
Early-career workers setting work habits now will carry them through decades of employment. If AI use is crowding out skill-building in formative roles, the consequences compound.
Do this week
Managers: audit how your Gen Z team members are using AI this week—not to restrict it, but to identify which tasks should still require manual effort for learning.
The concern: Gen Z may be outsourcing too much
Fortune published a story flagging that Generation Z workers are leaning on AI tools at work in ways that could harm their long-term career development. The piece does not cite specific data on prevalence or measure actual skill gaps; instead, it surfaces an anxiety among employers and career coaches about what happens when younger workers use AI to bypass foundational work early in their careers.
The core worry is straightforward. If a junior analyst uses Claude to write every memo, or a designer uses image generation for early sketches, they may never develop the judgment, craft, or speed that comes from doing the work manually first. The risk is not that AI is bad; it is that using it as a crutch before mastery can atrophy the very skills that make AI use valuable later.
Skill debt accumulates silently
This is not a headline-grabbing crisis with a published body count. It is a structural career problem. A 23-year-old who avoids writing reports because AI does it faster will reach 30 without the instinct for what a crisp memo looks like, or the judgment to know when AI output is half-baked. Employers will notice. Peers who did the work will pull ahead.
The timing matters because Gen Z is still early in their careers. Unlike mid-career workers who built skills before AI was widely available, this cohort is forming professional habits in a world where delegation to a machine is free and instant. The habits they lock in now are the ones they will carry forward.
What to do about it
The answer is not to ban AI. It is to be deliberate about when and how junior staff use it. Some tasks deserve the tool: admin work, routine research compilation, boilerplate that genuinely saves time. Other tasks deserve friction: writing under pressure, debugging, customer communication, anything where the output bears your name and your judgment is the point.
Managers should have explicit conversations with younger team members about which work is meant to be done first without AI, then refined with it. That distinction is not obvious to someone who has never had to live without the tool. Without guidance, the path of least resistance is to delegate everything, and the skill debt gets locked in before anyone notices.