The pathway
How you actually get there, here
How you become one varies far more by country than what one does. This is the UK route. Most people take one of these ways in; the right one depends on where you're starting from.
- 1
From Lead Operations Technology Architect (L4)
2-4 yearsSkills to master
- Moving from designing solutions to leading the people who design and implement them. You'll need to develop strong team leadership, budget management, and strategic planning skills. Less hands-on tech, more strategic oversight.
You're ready to move on when
- You've successfully led multiple complex system integration projects end-to-end.
- You've informally mentored junior team members and shown a knack for developing talent.
- You've demonstrated the ability to influence senior stakeholders and drive consensus on technical decisions.
- You've taken initiative on strategic planning, even if it wasn't formally part of your role.
- 2
From Senior Project Manager (Operations Technology focus)
3-5 yearsSkills to master
- Transitioning from managing specific projects to managing a portfolio of applications and a team of technical specialists. This means developing deeper technical domain expertise, strategic vision, and people leadership skills beyond project delivery.
You're ready to move on when
- You've consistently delivered complex operations tech projects on time and budget, with high user adoption.
- You've shown a strong understanding of the underlying technology and its operational impact, not just the project plan.
- You've proactively identified opportunities for process or system improvement, beyond the scope of your assigned projects.
- You've built strong relationships with technical teams and earned their respect.
- 3
From Operations Manager (with strong tech background)
4-6 yearsSkills to master
- Shifting from purely operational execution to a technology-first approach to solving operational problems. This involves deepening your technical architecture skills, understanding system integrations, and leading a technical team rather than an operational one.
You're ready to move on when
- You've consistently used technology to solve operational problems in your previous roles, not just managed processes.
- You have a strong understanding of the operational tech stack (e.g., WMS, TMS, MES) from a user perspective, and ideally some configuration experience.
- You've shown a natural aptitude for identifying technology gaps and proposing solutions.
- You're comfortable leading and developing technical specialists, even if you're not a hands-on coder anymore.