Redesign the work before you redraw the org chart

A role is a bundle, not an automation unit

An “AI can do 40% of this job” estimate hides the decision HR actually needs to make. Which tasks? At what demand and quality? With which exceptions, relationships, controls, seasonal peaks, systems, and failure costs? A job title compresses those differences into one label. Workforce redesign must unpack them before leaders discuss roles, staffing, or savings.

July 2026 research from LHH makes the cost of skipping that work visible. Its survey covered 3,000 HR leaders and more than 8,000 employees across seven countries. LHH reports that 87% of HR leaders said their organization had conducted or planned redundancies in the next 12 months. At the same time, only 30% tracked the number of redeployments, and leaders' belief that mobility programs existed differed sharply from employees' reported experience. The problem is not merely reduction. It is losing skills, trust, and institutional knowledge, then paying to rebuild them.

PwC's current CHRO blueprint begins with task-level decomposition for the same reason. It recommends understanding work before rewriting job descriptions or launching reskilling. CIPD research with more than 1,300 leaders and HR professionals finds confidence falling where AI adoption becomes job redesign: only around one third of HR leaders felt confident estimating future workforce needs arising from AI, 40% felt confident designing reskilling pathways, and 46% felt confident leading job redesign.

Those figures should not become a mandate for one consulting framework. They support a narrower operational claim: workforce change is a design and evidence problem, not a model-output problem. AI can make inventories and scenarios faster. It cannot determine whether the inventory captured invisible work, whether the scenario is lawful or fair, whether employees had a meaningful voice, or whether a future capability is worth losing a current one.

Build one task evidence register before modeling a future state

The register should combine sources that fail in different ways. Job descriptions show intended accountability but may be stale. System logs show transactions but miss judgment and relationship work. Interviews reveal workarounds but may overrepresent memorable exceptions. Manager estimates can omit peak load. Employee diaries can be detailed but burdensome. Triangulation is the control.

Use O*NET task and work-activity data as an external reference, not a replacement for local evidence. It helps challenge a missing task or identify skill adjacency across occupations. It does not know your contracts, service model, technology, customers, workarounds, or current team composition.

Invite employees to correct the map before scenario design. Ask what breaks in peak periods, who handles exceptions, which work is unofficial, where rework originates, what customers refuse to self-serve, and which relationships make the process function. Record disagreement. A disputed task map is a finding, not a reason for the model to choose a side.

Classify tasks without pretending the categories decide the workforce

“Automate candidate” is not authorization to deploy and certainly not authorization to remove a role. It means the task may support a controlled pilot. The pilot must count supervision, exception handling, quality review, integration, governance, training, and failure recovery. A model that completes 80% of cases may increase workload if the remaining 20% are hard to detect or take longer to repair.

Keep scenario assumptions explicit. Separate current facts from vendor claims, internal estimates, model suggestions, and management preferences. A senior leader's savings target does not become task evidence because it appears in a spreadsheet.

The eight-step human-governed redesign workflow

1. Define the service before the structure

State the required outcome, users, demand, quality, speed, risk, and cost. Include current backlogs and unmet needs. If the goal is only “reduce headcount,” stop: the conclusion has been chosen before the work is understood.

2. Inventory and validate the work

Build the task register from multiple periods and sources. Validate it with employees, managers, domain owners, customers or internal users, and control functions. Document invisible work and conflicting accounts.

3. Test the tool on representative work

Use current approved tools and representative cases. Test routine cases, exceptions, incomplete inputs, sensitive contexts, accessibility, outages, adversarial material, and handoffs. Measure review and rework, not only first-pass output.

4. Build three or more scenarios

Always include a baseline, an augmentation scenario, and a redesigned-service scenario. Add automation where evidence supports it. For each scenario show work allocation, service capacity, skill demand, supervision, control ownership, technology cost, implementation effort, risks, and reversibility.

5. Map skills and internal mobility

Identify which skills remain valuable, which adjacent roles need them, what gaps can be closed, how long learning takes, and what trial assignments or vacancies exist. Cornell ILR's 2026 GenAI and HR working-group report includes an example of a skills platform supporting redeployment of nearly 500 employees whose roles were eliminated. The transferable lesson is not the vendor. It is that mobility requires an operational skills system before a restructuring event.

6. Run impact and consultation review

Review equality and adverse impact, disability and accessibility, leave, worker representation, privacy, monitoring, employee relations, safety, customer access, workload, geographic and contractual requirements, and institutional knowledge. Use the applicable legal and collective processes for every location. AI may organize the questions; qualified people determine the answers.

7. Pilot without changing employment status

Run a reversible pilot against the baseline. Keep employees supported and record work shifted outside the measured system. Define stop rules for error, workload, harm, service degradation, data incidents, accessibility failure, hidden manual work, or cost overrun.

8. Create a decision record

Present options, assumptions, evidence gaps, employee input, reviewer positions, mitigations, redeployment and reskilling, cost ranges, service consequences, and unresolved questions. Bind the decision to named authorities and exact evidence. Do not let an AI recommendation populate the final decision field.

Worked example: redesign an HR service desk without erasing the work

Suppose leaders believe an HR chatbot can replace a five-person service desk because 60% of tickets ask recurring questions. The role-level conclusion is premature. The task map shows that recurring questions account for 60% of ticket count but 28% of effort. Complex leave, pay, immigration, accommodation, manager conflict, and data-correction cases account for fewer tickets but most handling time and risk. The team also maintains knowledge articles, spots policy defects, coordinates with payroll, and reassures employees who are unsure how to describe a sensitive issue.

The augmentation scenario gives the AI approved knowledge retrieval, translation, draft responses, and ticket classification. It does not answer sensitive categories autonomously. The redesign scenario moves routine self-service into a reviewed channel, creates a knowledge-owner task, strengthens specialist routing, and shifts service-desk capacity toward complex cases and policy feedback.

The evidence may support better service, changed roles, different staffing over time, or no scale-up. It does not identify who should leave. Vacancies, turnover, redeployment, learning paths, and service growth may absorb capacity. If leaders later consider workforce action, that is a new process with its own legal, consultation, equality, and individual-review requirements.

Failure modes that turn redesign into automated justification

Use a 30-day evidence pilot, not a 30-day reorganization

The human review gate

• The service outcome, demand, risk, and baseline are documented independently of a savings target.
• Employees and managers validated the task map, including exceptions, invisible work, peaks, relationships, and accessibility.
• Tool capability comes from representative local testing, not vendor claims or a model's self-assessment.
• Time savings are net of review, rework, supervision, integration, support, and failure recovery.
• Baseline, augmentation, redesign, skills, redeployment, and reskilling scenarios are visible.
• Equality, adverse-impact, privacy, accessibility, legal, labor, safety, and employee-relations reviews are complete where applicable.
• No named employee was ranked or selected by AI.
• Consultation, employee voice, disagreements, and reviewer positions are preserved in the record.
• The pilot has stop rules, retained human capability, rollback, and incident ownership.
• The final decision is made by named accountable humans and tied to the exact evidence version.

If any item is missing, the redesign remains a scenario. It is not a workforce decision.

Frequently asked questions

Can AI decide which roles should be eliminated?

No. It can organize evidence and draft scenarios. Role elimination, redundancy, individual selection, redeployment, pay, accommodation, and exit decisions require accountable human judgment and the applicable qualified reviews and processes.

Why start with tasks instead of job descriptions?

Job descriptions state intended responsibilities. They often miss current demand, workarounds, exceptions, emotional labor, peak periods, system administration, and informal coordination. Combine them with observed work and employee validation.

Does time saved equal headcount reduction?

No. Validate whether capacity is real after review, rework, supervision, adoption, service growth, exceptions, and technology costs. Decide how released capacity supports service, risk, learning, vacancies, redeployment, or other work before discussing staffing.

Should AI match employees to redeployment roles?

AI may help a person explore opportunities using verified skills and transparent criteria, but it should not make or secretly rank consequential individual decisions. Provide correction, accessibility, human review, and a way to express preferences and context.

What if employee and manager task maps disagree?

Record the disagreement and investigate through observation, samples, demand data, and facilitated review. Do not let the model average conflicting accounts into false certainty.

Is this legal advice for a restructuring?

No. It is an operational evidence workflow. Employment, consultation, equality, privacy, labor, collective, records, accessibility, and redundancy requirements vary by location and facts. Use qualified advice.

Sources and reference points

Public sources were checked on August 10, 2026. Survey findings describe their reported samples and should not be treated as universal workforce facts.

• LHH: 2026 Career Redeployment and Outplacement Trends
• PwC: CHRO architectural blueprint for AI workforce transformation
• CIPD: AI, HR capability, job redesign, and workforce planning
• Cornell ILR: Charting the Future - GenAI and HR Working Group
• Generative AI and the Reorganization of Labor Demand
• O*NET Database: occupations, tasks, work activities, and skills
• U.S. EEOC: artificial intelligence and ADA resources
• NIST AI Risk Management Framework
• Academy of Management: Digital HRM as Multi-Level Architecture and Governance
• r/humanresources: current practitioner discussions sampled through last30days

Related playbooks: audit whether AI assistance has transferred managerial judgment, set HR AI data and decision boundaries, review AI-assisted HR outputs before use, and protect identities when analyzing employee voice.