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.
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.
Scoped with you · runs on your confirmed graph
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 rest of Transform.
Programmes compound: each one deepens the same graph the next one runs on.
Start with this programme, on one department.
A rightsizing plan you can defend line by line, because every number traces to real work.