A successful technology demonstration can make a staffing estimate feel more certain than it is. A document is read faster, information moves without rekeying and a familiar administrative step appears to disappear. The improvement may be real. The difficulty begins when the time saved in that step is treated as a complete description of the work performed by the people around it. A service role often contains conversations, exceptions and decisions that the demonstration has not yet examined.
I do not regard this as an argument against digital investment. It is an argument for being precise about what the investment has shown. Technology leaders should receive credit for the capability actually delivered. Employees should not receive a consequential statement about their roles based on an assumption that has silently expanded beyond that evidence. The people function has a responsibility to notice the gap before a provisional model becomes an employment commitment.
Separate the task from the service
In the fictional Vaurenne Assurance redesign, the initial model assumed that 94 service roles would disappear. The demonstrated document step was quicker, and I accepted the broad direction too readily. A later operating review asked what happened before and after that step. Customers still needed explanations. Some documents raised further questions. Exceptions required someone to understand the case and route it appropriately. The work had changed, but it had not contracted in the same way at every point.
That review produced a different account of the original population: 61 continuing roles, 21 redeployments and 12 agreed departures. The numbers matter because they prevent a vague claim that most people found other opportunities from replacing the actual decision. They also show the limit of the case. We are describing a defined group in a particular redesign, not a forecast of employment across an industry or a promise that the continuing roles will remain unchanged indefinitely.
The review should involve the people who know the work, but it should not ask them to defend every existing task simply because it is familiar. Some activity can disappear without loss. Some can move to another role. Some may become more important when routine processing accelerates. A useful discussion distinguishes those possibilities and considers the customer’s next step. The objective is an operating model that can be explained, not preservation of every current arrangement or achievement of a predetermined reduction.
I also want a clear distinction between an average and a usable allocation of time. Small savings across many activities do not automatically create whole roles that can be removed at a particular location or shift. Managers must consider the distribution of work, the need for availability and the skills required for exceptions. Those are operating questions with employment consequences. The people team should ensure they are answered before presenting a staffing number as if arithmetic alone had settled the decision.
Give revision a place in the business case
Once a reduction has entered a financial plan, revising it can feel like conceding failure. The project team may worry that the technology will be judged unfairly. Finance may need to explain a changed cost trajectory. The people function may be reluctant to revisit an assumption it previously endorsed. These are understandable pressures, but they do not make the original estimate more accurate. A business case should be capable of learning from the work it was designed to change.
We accepted CAD 1.35 million of additional transition cost and a four-month staffing delay. The additional expense was recorded as a consequence of the revised employment arrangement, not disguised as a saving elsewhere. I supported explaining both the useful digital capability and the workforce assumption that had proved too broad. That allowed the organisation to continue with the improvement without forcing the observed work into an earlier commitment that no longer described it.
Revision needs discipline rather than an unlimited invitation to postpone difficult choices. The proposal should identify what new evidence has emerged, which assumption it changes and what decision follows. A manager should be able to distinguish an unresolved question from a preference to avoid change. The same scrutiny should apply to an optimistic reduction and to a request to retain every role. Clear evidence makes the discussion more demanding, but also more useful to the people who must implement the result.
I would build those review points into the project before the first employment announcement. That means agreeing when the operating model will be tested, who can challenge the staffing assumption and what must be known before individual decisions proceed. It is easier to preserve honest uncertainty at that stage than to recover it after a confident number has been communicated widely. A qualified statement can still be a firm management commitment when its conditions are explicit.
Account for the people after the decision
Redeployment is not complete because a report places someone in that category. The receiving role needs a defined requirement, a manager, appropriate support and a realistic account of the transition. An agreed departure has its own arrangements, handled with qualified advisers and respect for privacy. Continuing employees need to understand how their work changes and what authority they retain. The public case can explain those responsibilities without disclosing individual circumstances or claiming that every outcome was easy.
The operating review must also continue after the staffing decision. If exceptions accumulate, the organisation should examine why. If the technology performs better than expected, the account may change again. Neither observation should automatically become another employment instruction. Management needs to understand the evidence and decide through the appropriate process. The value of a more careful first decision is that it leaves a clearer basis for later judgement, rather than a narrative that can only admit success.
This is where I see the people function making a substantial contribution to transformation. We do not need to claim technical ownership to ask whether the employment assumptions are supported. We can connect the business case with the work employees actually perform, the arrangements required for change and the consequences that remain after a project milestone. That contribution is strongest when we acknowledge our own earlier assumptions and are prepared to revise them publicly within the executive discussion.
A faster document can be a worthwhile achievement. It should be described accurately and built into a service model that understands the surrounding work. The customer is interested in an answer, not merely a completed processing step. The employee needs a role that can deliver that answer within a clear scope. When those two perspectives remain visible, the staffing decision becomes an accountable choice about the changed business rather than an automatic extrapolation from a successful demonstration.