Organisations love the idea of shift left. Take work currently handled by L2 specialists, equip L1 with the knowledge and capability to resolve it, and reduce costly escalations.

But there is one uncomfortable question that often gets ignored:

If L1 takes on L2's work, who takes on L1's?

Adding more complex work to an already busy service desk is simply workload redistribution and not shift left. For shift left to work, organisations need to create capacity at the same time they transfer capability. Routine L1 work must increasingly move to self-service, automation and AI, allowing L1 analysts to take ownership of more sophisticated issues.

On paper, the traditional approach to shift left makes perfect sense. Look at the incidents being escalated to L2, identify those that are repeatable and well understood, capture the knowledge required to resolve them and give L1 the training and access needed to take them on. .

The problem is that capability and capacity are not the same thing.

An L1 analyst might now know how to resolve an issue that previously required L2, but that additional knowledge does not create additional hours in their day. If analysts are still spending significant amounts of time on repetitive requests, basic troubleshooting and administrative activities, adding more complex work simply creates pressure somewhere else in the support model.

That is why the shift-left conversation needs to start one step earlier. Before asking "What can we move from L2 to L1?", organisations should ask:

"What work should L1 no longer need to do?"

Routine and predictable work should increasingly be challenged. Does this request really require an analyst? Could the user complete it through self-service? Could a workflow fulfil it automatically? Could AI help diagnose the issue or surface the right resolution? And if the same incident occurs repeatedly, should we continue becoming more efficient at resolving it, or should we focus on eliminating the underlying cause? This is where automation becomes an important part of shift left, but not simply as a cost-cutting exercise. Automation can create the space that makes shift left possible.

If repetitive L1 activities can be removed, automated or moved to effective self-service, the capacity created can be reinvested into the service desk. L1 analysts can develop greater technical capability, gain access to better diagnostic tools and knowledge, and take ownership of issues that previously needed to be passed to specialist teams. In other words, the goal shouldn't be to make L1 more capable with better capacity.

This approach has much bigger impact on the future of the service desk.