Walk into almost any organization today and you'll hear some version of the same conversation.
AI is changing how work gets done. Customers expect faster responses. Technology is eliminating tasks that once consumed hours. Employees are learning new systems while trying to keep old ones running. Managers are being asked to increase productivity, control costs, and somehow find capacity for the next strategic priority.
Meanwhile, somewhere in that same organization sits a job description written five years ago.
Maybe ten.
The employee occupying that position has gradually absorbed new responsibilities, abandoned others, learned new systems, developed new skills, inherited work from departed colleagues, and created countless workarounds just to keep things moving.
Officially, though?
It's still the same job.
That's a bigger business problem than it might appear.
Organizations are spending enormous amounts of money transforming technology, implementing AI, changing strategy, and improving processes while often leaving the basic architecture of work untouched.
Perhaps it's time to ask a deceptively simple question:
The work changed. Did your jobs?
Jobs Have a Way of Accumulating
Most jobs aren't deliberately redesigned. They accumulate.
A new responsibility gets added because someone leaves. Another appears because of a regulatory change. A system implementation creates several new tasks. A customer wants something different. A manager requests another report. A temporary responsibility quietly becomes permanent.
Very little disappears.
Over time, a job can become a collection of responsibilities created during entirely different eras of the organization.
I think of it almost like the junk drawer in the kitchen. Nobody intentionally designed it to contain batteries, takeout menus, three screwdrivers, rubber bands, a flashlight, and six things nobody can identify. Each item made sense when someone put it there.
Eventually, though, somebody needs to empty the drawer.
Jobs work the same way.
Some of the accumulated work creates tremendous value. Some made sense five years ago but doesn't anymore. And some survives for no reason other than nobody has asked why we're still doing it.
That's not really workforce strategy.
It's organizational accumulation.
Start With the Work, Not the Job
Organizations naturally think in jobs.
We need an accountant. We need a project manager. We need a customer service representative. We need another analyst.
But a job is really just a container for work.
When the work changes significantly, the container deserves another look.
Instead of immediately asking whether we need another position, start underneath the position. What actually needs to get accomplished? What business outcome are we trying to produce? What work contributes directly to that outcome, and what work has simply accumulated around it?
Then the conversation gets interesting.
Some work requires expertise. Some requires judgment. Some requires relationships and context. Some can now be automated. Some could be simplified. Some belongs somewhere else.
And some probably shouldn't exist at all.
Only after understanding the work can we intelligently determine what the job should become.
That sounds like a subtle difference.
It isn't.
One approach maintains positions.
The other designs organizational capability.
AI Makes the Gap Harder to Ignore
For years, organizations could get away with allowing jobs to evolve gradually. Technology has shortened that runway considerably.
Tasks that once consumed hours can now take minutes. Employees can analyze information faster, create first drafts faster, summarize information faster, automate repetitive work, and access expertise in ways that weren't possible a few years ago.
That's creating an interesting question that isn't receiving nearly enough executive attention.
What happens to the capacity technology gives back?
Suppose a collection of tasks that once consumed ten hours each week now takes three.
What happens to the other seven?
Does the employee take on higher-value work? Does the organization increase output? Does the position become broader? Does the person develop new capabilities? Does customer service improve?
Or does everyone simply continue doing the old job slightly faster?
Installing AI isn't the same thing as redesigning work.
And if organizations don't deliberately decide what should happen with newly created capacity, much of the promised productivity benefit may simply disappear into the workday.
Don't Automate Work Nobody Needs
There's another question worth asking before we get too excited about automation.
Should the work exist in the first place?
Imagine a department produces twelve recurring reports. AI could dramatically reduce the amount of time employees spend creating them.
Wonderful.
But suppose only four of those reports actually influence a business decision.
The organization could proudly announce that AI made report production 70 percent more efficient.
Or it could stop producing eight reports nobody needs.
Sometimes the most productive thing an organization can do isn't automate work.
It's eliminate it.
This is why I believe work redesign needs to accompany the AI conversation.
Technology can make a bad process faster.
It doesn't automatically make the process valuable.
Human Work Is Changing Too
There's a tendency to frame AI conversations around what machines can now do.
I'm increasingly interested in the other side of that equation.
What becomes more important for humans to do?
As technology handles more routine execution, human judgment becomes more valuable. Context matters more. Problem definition matters more. Relationships matter. Critical thinking matters. Knowing when the technology is confidently wrong certainly matters.
That means jobs don't simply get smaller as technology improves.
In many cases, they become different.
And that creates a challenge organizations need to think through carefully.
Some of the routine work being automated today is also work through which employees historically learned.
An early-career employee might have developed expertise by researching information, preparing basic analyses, reviewing documents, or creating first drafts. If technology performs much of that work now, how does the employee develop the judgment required for the more sophisticated work later?
That isn't an argument against AI.
It's an argument for intentional workforce design.
We need to think not only about who performs today's work, but also how people develop the capabilities the organization will need tomorrow.
Your Best Employees May Already Be Redesigning Their Jobs
Here's something else worth looking for.
Your best employees may be ahead of you.
High performers naturally redesign work. They find shortcuts. They create templates. They automate repetitive tasks. They build relationships across departments. They stop doing things that don't create much value. They quietly take responsibility for things that technically aren't in their job description.
That ingenuity is valuable.
It can also hide something.
The organization may no longer know what the job actually is.
If the real position exists primarily inside the employee's head, leadership may not understand what capability the business depends upon until that employee leaves.
Then someone pulls out the official job description and discovers it describes a job that hasn't existed for years.
Instead of only asking high performers how they're doing, we might occasionally ask:
How are you actually doing your job now?
The answer could tell us a great deal about how the work itself has changed.
Familiar Titles Can Hide Unfamiliar Work
Traditional organizations tend to organize work into recognizable functional boxes.
Finance does finance. HR does HR. IT handles technology. Operations handles operations.
The boundaries aren't nearly as clean anymore.
A finance leader may need substantial technology fluency. An HR leader may need to understand workforce analytics and business modeling. An operations leader may need to understand AI. A marketer may now perform work that once required several separate specialties.
The title on the business card might not have changed.
The capability underneath it has.
This is one reason workforce planning based primarily on job titles and headcount can miss what is actually happening inside an organization.
You can have the same number of people in the same number of jobs and still have a significant capability gap.
Redesign Doesn't Automatically Mean Reduction
This point matters.
When employees hear words like job redesign, automation, productivity, and AI in the same conversation, it's understandable that they may hear one thing:
Layoffs.
But that shouldn't be the predetermined outcome.
Sometimes redesign may reveal that fewer people are required for certain work.
Other times it reveals enormous opportunity.
Perhaps technology removes administrative work and allows employees to serve more customers. Maybe redesigned positions create capacity for a new service. Perhaps employees can spend more time solving complex problems, developing relationships, improving quality, or generating revenue.
Maybe the organization discovers it actually needs additional capability in an area it has underinvested in.
The objective isn't headcount reduction.
The objective is alignment.
What work does the business need accomplished, and what combination of people, technology, process, structure, and external expertise gives us the best way to accomplish it?
That's a much more useful executive question than simply asking where AI can replace labor.
Watch Where Work Migrates
Work rarely disappears neatly.
It moves.
Someone leaves and their responsibilities are distributed among three coworkers. A department reorganizes and a process quietly lands somewhere else. A new technology changes who performs a task. AI allows one function to do something that previously required another.
Eventually, organizations can reach a point where everyone touches a piece of the work but nobody really owns the outcome.
That creates another kind of friction.
As work moves, accountability needs to move with it.
Who owns the outcome now? Who has authority to make decisions? Where should the work logically live?
Technology can create speed.
But without organizational clarity, speed simply gets us to confusion faster.
A Job Description Shouldn't Become a Museum
Job descriptions have legitimate purposes. But they shouldn't become historical exhibits preserving how work used to happen.
For strategically important roles, leaders should periodically ask a simple hypothetical:
If we were creating this job today, would we design it this way?
Would these responsibilities still belong together?
Would we require the same capabilities?
Would the position report to the same place?
Which tasks would technology perform?
Where would we need more human judgment?
What would we remove entirely?
What outcomes would matter now?
If the answers look dramatically different from the existing job, that's useful information.
The goal isn't to rewrite job descriptions every six months.
It's to make sure the organization isn't building tomorrow's strategy on yesterday's work.
The Bigger Question
AI will continue to evolve. Technology will continue to change. Customer expectations will shift. Business strategies will adjust.
The question isn't whether work will change.
It already has.
The strategic question is whether organizations will deliberately redesign around those changes or simply continue layering tomorrow's work onto yesterday's jobs.
Because eventually the gap becomes expensive.
Employees become overloaded with accumulated work. New technology fails to deliver its promised value. Capability gaps emerge. Accountability becomes fuzzy. Organizations add headcount without understanding why capacity disappeared in the first place.
Before hiring another person, automating another task, or launching another productivity initiative, perhaps executives should ask something more fundamental.
If we were designing this work from scratch today, what would we do differently?
The answer might change far more than a job description.
It might change how the organization works.
