You are introducing AI into a business function where a meaningful share of routine work can now be automated. People are anxious, leadership is tempted to frame the change as labour optimisation, and you need a way to turn that disruption into a more productive operating model rather than a morale problem or a blunt cost-cutting exercise.
Start by acknowledging the real operational gain: if routine analytical work can be automated, automate it. Amelia is not arguing against efficiency. But she insists that leaders must then look at the “other side of the coin” and ask where those freed-up human skills can be redeployed to drive growth rather than simply removed from the system.
The second step is to reframe the change from labour reduction to productivity-loop design. Her mechanism is to redirect human resources, skills, and talent into work that is more strategic, higher-value, and more directly connected to growth. In her example, that meant using automation to remove routine analytical work, then redesigning the role of the team so that the same people could contribute at a higher level.
The third step is to treat this as a leadership transition problem, not a technology rollout. Amelia’s explicit lesson is that it is “not a story about AI versus the people”; it is about whether leaders design the transition deliberately or let it happen to people by default. In practice, that means managing anxiety, redesigning the work, creating mobility, and deciding where human judgment still adds value.
The final step is to validate the redesign through actual role elevation, not rhetoric. In the deployment she describes, twelve months later the same team was doing more strategic work, had internal mobility, and saw their roles increase rather than simply shrink. That is the test: did the organisation merely automate tasks, or did it actually convert the impact of change into new value?
This framework breaks down when the underlying business does not actually have higher-value work ready for redeployment. In that situation, leaders can apply the logic sincerely and still end up with displaced people and abstract promises, because there is nowhere meaningful for the capability to go. The framework assumes there is real growth work, strategic work, or decision-support work that can absorb the freed capacity. That condition is implicit in Amelia’s example.
It also fails when leadership uses the language of redeployment while still primarily optimising for short-term labour reduction. Amelia is explicit that many companies rush toward immediate labour wins and that “you can’t cut your way to glory.” If the real intent is headcount removal, this framework becomes cosmetic language around a different objective.
A third failure condition is when leaders do not redesign the human role clearly enough. Amelia’s wider point is that once work becomes less verifiable and less automatable, human judgment has to re-enter the loop. If leadership does not specify where that judgment matters, people either get bypassed by automation or remain attached to old low-value work.
Executive Leader in AI & Digital Infrastructure, Founder & CEO of U-BI
