Railway Solutions of the Future: How to reverse 200 years of legacy systems

Recent events have once again reminded us that, despite all of the progress we have made as an industry, risk remains an ever-present reality on the railway. As investigations proceed, it is right that the focus remains on understanding what happened and identifying any lessons that need to be learned. But alongside that important work, I believe there is a wider conversation that the industry needs to have. For years, much of my work has centred on a simple but increasingly important challenge: How do we identify and mitigate risks before they become incidents? Whether looking at overspeeding, Driver Advisory Systems, Traffic Management systems, predictive operational tools or the wider opportunities presented by ERTMS, I have consistently found myself returning to the same conclusion. The railway is still largely built around reacting to developing situations rather than predicting them. That is not a criticism of our people. Far from it. Every day, drivers, signallers, controllers a...

The UK railway can’t wait for AI and Machine Learning to mature before fixing real‑time operations. And yet… too much of the industry is behaving as if “AI will sort it out in five years”. Meanwhile, front‑line staff, controllers, operators, passengers and customers are dealing with the consequences  today . Here’s the uncomfortable truth: We already have the core systems to improve performance dramatically . What we  don’t  have is complete integration. What we don’t have is a single operational truth across the network. What we don’t have is the industry focus to stop working in silos. Traffic Management without real‑time stock & crew data is only doing half the job. DAS without real‑time plan updates can never unlock its full benefit. Stock & crew systems that don’t see operational conflicts will always leave controllers fighting fires. And let’s be honest: “AI isn’t coming to save us - not until we fix the data foundations it depends on.” The good news? Integr...

We've all been there. The pressure is on, project deadlines are looming, and corners get cut. In the world of application development, this often manifests as "technical debt" – the shortcuts in code that save time now but cost more later. But there's another, often overlooked, and equally insidious form of debt accumulating in our applications: UX Debt . Just like technical debt, UX debt refers to the compromises, shortcuts, or deliberate omissions in the user experience that are made during development, often to meet tight deadlines, save resources, or prioritise new features or functions. While seemingly innocuous at first, this debt silently accrues, eventually impacting user satisfaction, development efficiency, and ultimately, your application's success as a commercial and user friendly solution to a given set of problems. What does UX Debt look like? UX debt isn't always a glaring design flaw. Often, it's a collection of issues that erode the user e...

We've all been there.  That project looming, the urge to nail every single detail before unleashing it on the world. You envision a glorious, flawless 100% completion, the ultimate mic drop of productivity. But what if that pursuit of perfection is actually holding you back? Let's face it: 80% completion today, achieved through consistent small steps, is often far more valuable than a mythical 100% delivered after an overly complicated and extended timeline. Think of it like this: Would you rather have a functional prototype you can test and iterate on now, gathering valuable feedback and making necessary adjustments? Or a supposedly perfect masterpiece that finally sees the light of day months later, potentially missing the market window or being completely off the mark? The allure of the grand, all-encompassing effort is strong. We convince ourselves that by pouring in extra time and energy upfront, we'll avoid future headaches. But the reality is often the opposite. Over...

To all Project Managers or even those of you that have been involved in a project delivery, have you ever witnessed: // Work starts without an approved plan. // Tasks have multiple owners, no clear responsibility. // Milestones disappear without discussion. // Meetings are endless debates, no decisions. // Scope creep expands project beyond initial plan. // Unrealistic timelines are set. // Lack of clear project scope. // Insufficient risk assessment. // Poorly defined requirements. // Lack of communication between team and stakeholders. // Ineffective leadership. // Lack of stakeholder involvement. // "No bad news" culture prevails. // Poor resource management. // Lack of accountability for tasks. // Unresolved team conflict. // Insufficient training for team members. // Ignoring feedback from team/stakeholders. // No clear governance structure. // Dismissive culture of challenges to poor project delivery.  Disaster is inevitable if any (or all) of the above elements are tru...

The rhythmic clatter of train wheels, the whistle echoing through the countryside – these are iconic sounds of the UK's railway system. But are these sounds about to be joined by the whir of artificial intelligence, reshaping our travel experience? The potential is immense, but the journey must be navigated with care. Imagine AI optimising timetables to reduce delays, predictive maintenance preventing breakdowns, and personalised customer service enhancing every journey. Yet, this vision hinges on one crucial factor: responsible AI. Can the UK railway system build an AI strategy that's not just efficient, but ethical? According to recent discussions, the path forward requires a structured approach, built on the foundations of responsible AI principles. Let's break down the key steps: 1. Defining the Destination: Clear Objectives. Before any train leaves the station, its destination must be set. The same applies to AI. What are the UK railways aiming to achieve? Are we talki...