- AI doesn't wipe out whole positions. It takes over standardized subtasks, one at a time.
- Break each position into its subtasks before you decide anything. You'll see clearly which parts should go to a system and which need to stay with people.
- The work that gains value is work that calls for accountability, relationships and judgment in situations the manual doesn't cover.
1. Analyze tasks before predicting job titles
A single “sales admin” position is really a dozen or more subtasks. Some are repetitive data entry; others involve calling an angry customer to smooth things over. If you judge the whole position at once as replaceable or not, you'll get it wrong either way.
A “sales admin” role might involve receiving leads, entering data into the CRM, preparing documents, scheduling appointments, chasing status updates and coordinating with customers. Some of these tasks can be heavily automated, while others depend on relationships. If a company assesses the whole position as either replaceable or not, it misses the chance to redesign the work.

Sort tasks into Routine Information, Variable Information, Physical, Relationship and Accountability. Reading, copying, categorizing, summarizing and producing documents are increasingly likely to be taken over by AI. Work that involves answering for the impact, negotiating, being physically present on site and building trust still needs people, though those people will get more input from AI.
2. Work likely to shrink or change shape significantly
The work that shrinks first tends to look alike: reading, copying, categorizing and passing things on. The work that stays is work that requires decisions in situations the manual doesn't cover.
Data administration, such as data entry, filing, format checks and compiling reports, will shrink as agents connect systems and handle a wider range of documents. Standardized content work, such as product descriptions, captions and summary reports, will take fewer people per piece, though someone still needs to set the direction and check the facts.
Status coordination, the job of asking who has got how far and passing information along, will increasingly be replaced by workflows. First-line support will shift from answering FAQs to handling cases that involve emotion, risk or exceptions. Junior analysis focused on gathering data and making slides may shrink in numbers, and newcomers will need new ways to learn through real work.
The shrinkage won't be the same in every industry. Work where the data isn't digital, the rules are complex or regulation applies may change more slowly. Owners need to use data from their own processes, and should never judge people against a list of job titles found on the internet.
3. Work and roles that will be worth more
Domain experts who can teach the system will be worth more than people who follow procedures without being able to explain why, because organizations need to turn knowledge into rules, examples and evaluations. Process designers connect business, technology and customer experience to eliminate handoffs.

For the development team · Technical detail
AI Quality and Risk staff look after test sets, spot checks, incidents and bias. A Customer Specialist takes the situations AI can't resolve and has the authority to decide. A Product Experimenter uses AI to create and test ideas quickly, but chooses among them based on market evidence.
Human skills such as analytical thinking, creativity, flexibility, leadership and collaboration still matter, because as drafts get cheaper to produce, the value moves to choosing which problems to solve, judging trade-offs and taking responsibility for outcomes.
4. Use a workforce matrix instead of across-the-board cuts
| Group | Task characteristics | Strategy |
|---|---|---|
| Automate | Repetitive, rule-based, high-volume, easy to check | Reduce touch time and don't backfill |
| Augment | Requires analysis, but data can help | Train people to use AI and raise output per person |
| Human-led | Relationships, accountability and exceptions | Keep your best people and give them more decision authority |
| New Work | Agents, data, evaluation, governance | Create new roles or new skills |
Have managers estimate how many hours each role spends in each group, then build scenarios in which 25, 50 and 70 percent of the work can be automated, and calculate the resulting capacity and the roles that need to be added. This shows the company both the positions that will shrink and the skill gaps that could block the change.
5. Key skills for people working in 2029
- Problem Framing: turning broad goals into tasks, criteria and constraints a system can understand
- Data Judgment: knowing which sources to trust, spotting missing data and never concluding more than the evidence supports
- Process Thinking: seeing work from start to finish and separating rules, AI and human decisions
- Evaluation: creating good examples, checking quality and classifying errors
- Exception Handling: making decisions when information is ambiguous or the stakes are high
- Customer Empathy: understanding context, trust and needs nobody has written down
- AI Safety Literacy: understanding confidential data, permissions, prompt injection and traceability
Typing prompts is only a basic skill, and tools will increasingly write prompts on their own. What lasts is understanding the business and judging whether a result “fits the context and creates value”.

6. Reskilling has to be tied to real workflows
A one-day general AI training gets people experimenting, but it doesn't change how they work. Pick a real workflow and have the team design the before and after, try out the system and take ownership of the KPI. Learners should use approved data, build evaluations and present the business results, so that what they learn becomes an asset for the company.

For the development team · Technical detail
Set up levels: AI Literacy for everyone, Workflow Practitioner for users, Builder for those who build, and Owner for those who manage the risk. Base internal certification on work delivered instead of hours of study, and build a community of practice to share templates and incidents.
7. Build a scenario-based headcount plan
For the development team · Technical detail
Make Base, Accelerated and Constrained plans. In each one, set out the workload, productivity gain, attrition, hiring freeze, redeployment and new roles. Don't count hours saved as an immediate headcount reduction. You need to see how those hours add up to FTEs and how the company actually captures the value.
Set a hiring gate for routine positions: before an additional hire is approved, the team must show it has adjusted the process and assessed automation. For human-led positions, move quickly to retain people and build their AI skills, because this group will make the biggest difference.
8. A 12-month plan for owners and HR
- Quarter 1: build a task inventory and workforce matrix for your key workflows
- Quarter 2: pilot automation and augmentation in two processes, with training built on real work
- Quarter 3: update job descriptions, KPIs, hiring gates and career paths
- Quarter 4: build headcount scenarios for 2028 to 2029 from actual productivity results
In short: Routine information and coordination work is likely to shrink, while domain judgment, process design, customer trust and AI governance will be worth more. Companies should move from planning their workforce by position to planning it by task and workflow, with reskilling done on real work. This reduces both overhiring and the risk of running short of skills later on.
Turn workforce planning from gut feeling into data you can decide on
The answer to which positions should grow, shrink or change has to come from HR and the line managers who know the actual work. A software company can't supply it. So we start by helping structure what your team already knows: breaking each position into subtasks and recording how long each task takes, what data supports it, how much judgment it requires and what a mistake would cost. Once this data is in the same format across the company, departments can be compared with each other.
A system that gets HR and managers looking at the same picture
What we build next is usually an internal web application for the task inventory and workforce matrix, which each team lead can fill in themselves. Role-based views let HR see the overall picture while each manager sees only their own team, and a scenario module shows what headcount and roles should look like if productivity rises by 20, 40 or 60 percent. We deliver in short cycles, starting with two or three departments before expanding across the organization. If you are deciding on new hires right now without task data in hand, we'd be glad to help you set up your first data set.
SOFTWARE ENGINEERING GLOSSARY
Software engineering glossary
These terms help you talk to the development team precisely about workforce data systems.
| Term | What it is | A simple example | What executives should ask the development team |
|---|---|---|---|
| Role-based View | Showing different data to different users according to their role, within one system | Managers see only their own team, while HR sees the whole company | Who sees which level of data, and how do permissions change when someone moves to a new position? |
| Data Model | The structure that describes what data exists and how it relates | One position has many tasks, and each task has a time and a risk level | If we want to add a new dimension later, will we have to rebuild the system? |
| Scenario Modeling | Simulating outcomes under several sets of assumptions to compare options | Modeling the workforce if 20, 40 or 60 percent of the work can be automated | Which real data do the assumptions come from, and who confirms them? |
| Capstone | A real piece of work learners must deliver at the end of a course, used to measure whether they can actually do the job, beyond having completed the training | Having a team redesign its own workflow and measure the results before and after | Do we measure learning through real work or through tests? |
| Adoption Analytics | Data on how much people actually use a system and what they use it for | Seeing how many managers update the task inventory each month | Are we measuring real usage, or only the number of accounts opened? |
