Create a rightsizing plan mapped to your processes
Rightsizing without a process map is guesswork with a spreadsheet. This programme builds the plan from how work actually flows, so every capacity decision traces to real workflows, not benchmark ratios.
06TransformScoped with you · runs on your confirmed graph
Benchmark ratios are how good teams get cut and bad decisions get defended.
The standard rightsizing playbook starts with a number that came from somewhere else: a benchmark ratio, a competitor's disclosed headcount, a percentage that survived a steering committee. Then the organisation is trimmed toward the number, evenly, as though every team were equally automatable and every hour equally disposable. Neither is ever true, which is why the same playbook so reliably produces service failures, counter-offers for the people who mattered, and a quiet rehiring wave eighteen months later.
The defensible alternative starts from the work. Each process in scope has a knowable answer to two questions: how much capacity does it actually consume today, and how much will it need once AI absorbs the automatable steps. Model that, step by step, and the number per team stops being a target and becomes a finding, one you can trace to real workflows when finance, the workforce or a works council asks how it was reached.
A defensible plan is not one with a smaller number. It is one where every number traces to real work.
Sequencing matters as much as the number. A capacity finding becomes a humane and durable plan through order: what reduces through natural attrition, what redeploys into the growth areas the same analysis revealed, what retrains, and, critically, what gets protected because what looks like slack is actually load-bearing institutional knowledge you cannot rebuild at any price. Plans that skip the risk register save money for two quarters and pay it back with interest.
This programme builds the plan that survives scrutiny: capacity modelled per process, changes sequenced by quarter, risks flagged where the plan is fragile, and every line traceable to how work actually flows.
What this programme does.
Each process in scope is analysed for the capacity it actually consumes versus what it needs once AI absorbs the automatable steps, giving a defensible number per team rather than a top-down target.
The plan sequences changes so service levels hold: what reduces through attrition, what redeploys into growth areas, what retrains, and where cutting would destroy institutional knowledge you cannot rebuild.
From kickoff to landed.
Scoped with you · runs on your confirmed graph
The plan's boundaries, agreed
No-redundancy commitments, union agreements, service levels, budget: the constraints go in first, so every scenario the model produces is one you could actually run.
Capacity per process, evidenced
Each process in scope is analysed for the capacity it consumes today versus what it needs once AI absorbs the automatable steps: a defensible number per team, not a top-down target.
Reduce, redeploy, retrain, protect
The plan sequences changes by quarter so service levels hold, with the risk register flagging where knowledge, coverage or morale make the plan fragile.
Finance and HR walk the plan
We walk the plan line by line with the people who must defend it: where each number came from, what it assumes, and what the tracking programme will watch once it runs.
What you get.
Living documents, not slideware: every deliverable stays connected to the graph and updates as the analysis moves.
Capacity model per process
Current versus required hours, step by step, with the evidence.
Rightsizing plan
Sequenced by quarter: reduce, redeploy, retrain, protect.
Risk register
Where the plan is fragile: knowledge, coverage and morale risks flagged.
What you need.
- Mapped processes for the areas in scope, or run Process Mapping first
- Your constraints: no-redundancy commitments, union agreements, service levels
- Finance data for the affected teams
The questions teams ask about this programme.
Is this just a politer word for a layoff plan?+
No. Rightsizing here means matching capacity to how work actually flows, and the plan explicitly sequences redeployment, retraining and attrition before reduction, plus a protect list for teams whose apparent slack is load-bearing knowledge. Where reduction is the right answer, the plan makes it defensible; where it is not, the plan says so.
How is this different from a benchmark-driven consulting study?+
Benchmarks tell you what other organisations look like. This models what your processes actually need, step by step, once AI absorbs the automatable work, so every number traces to your workflows rather than to an industry ratio. That traceability is what makes the plan survive finance review and workforce scrutiny.
We have made no-redundancy commitments. Is the programme still useful?+
Arguably more so. Within that constraint the plan works entirely through attrition, redeployment and retraining, and the capacity model shows where freed hours should flow. Knowing your real capacity picture matters most when your levers are limited.
What do you need from us?+
Mapped processes for the areas in scope, or run Process Mapping first, plus your constraints and finance data for the affected teams. The modelling then runs on your confirmed graph.
How do we know the plan is actually working once it runs?+
The Rightsizing Tracking programme watches the plan against reality: milestones landing, capacity actually freed, and early strain signals like overtime creep and backlog growth, so corrections happen while they are still cheap.
Programmes compound.
Each programme deepens the same graph the next one runs on: nothing is re-gathered, nothing starts from zero.
The natural next step · Programme 10 · TractionTrack rightsizing progress
A plan is a set of predictions. Track them against reality from the first milestone, while corrections are still cheap.
View programmeExplore next
Transform
Redesign the org around what AI now does.
Read moreConsolidate your tool and vendor stacks
Fewer tools, lower spend, no broken workflows
Read moreRedesign your org to be AI-first
Roles, teams and structure, rebuilt around AI
Read moreThe Enterprise AI Transformation Roadmap: From Audit to Adoption
Most enterprise AI transformations stall because they skip the hard work of understanding their own workforce. Here's the three-phase roadmap that actually works.
Read moreMeasuring AI Transformation ROI: Beyond Adoption Metrics
Most AI ROI models track the wrong things. Real transformation ROI measures capacity freed, roles redesigned, and capability uplift.
Read moreEngagements
How an engagement runs, week by week.
Read more
Start with this programme, on one department.
A rightsizing plan you can defend line by line, because every number traces to real work.