Why Rail Innovation Dies Without Community

Rail innovation rarely fails because the technology is wrong. It fails because the trust and the translation needed to move an idea into service aren't there, and most of the sector has no reliable way to build them.

Building that trust is most of what we do at the Rail Innovation Group. A recent Supplier Challenge we ran is a good example of what it takes.

A few weeks before the pitch session, we recorded a podcast with the operator's leadership. Nothing elaborate. The point was to give the startups who'd be applying some context: what the operator actually did, what sat outside its control, and what kind of partnership it was looking for.

People assume that sort of thing is marketing. It isn't. It's the part of the work that decides whether the event produces anything at all.

Without it, the startups would have turned up carrying every assumption they'd picked up from the rest of the rail sector. They'd have pitched at the wrong scope, built their case around the wrong commercial driver, designed for a buying environment that didn't apply here. The operator's team would have spent the day nodding politely at solutions that missed the point, and everyone would have gone home thinking it had been a reasonable use of time.

Doing that translation up front changed what was possible on the day. The startups arrived knowing the operator's remit and the commercial logic of the service. They knew which problems they were actually being asked to solve. The operator's team didn't have to spend the morning working out which pitches were even relevant, so they could get straight to the substance.

The Assumptions That Kill Innovation

Any startup that's spent time in rail picks up a kind of learned wariness. They've heard "really interesting, do send me more" often enough to know what it means. They've watched a conversation grow quieter and less engaging with each stakeholder workshop, until it fades out altogether. They've worked out that the person they're pitching to usually can't buy anything.

So they hedge. The first assumption they carry is that the operator can't act. They've been taught that the real buying authority sits elsewhere: the ROSCO, Network Rail, the DfT, a procurement framework two levels up. So they soften the commercial pitch, on the basis that nobody in the room can sign for it anyway. The conversation turns informational, and the energy goes out of it before the second slide.

The second assumption is that everything takes years. They walk in having already written off the next eighteen months, and it shows. That framing kills the urgency a commercial buyer responds to. What the operator hears is a supplier who plans to be slow and expensive, and they adjust accordingly.

The third assumption is that safety and assurance will swallow the whole discussion. So the startup front-loads it, spending its best minutes answering concerns nobody in the room has raised. Meanwhile the buyer is waiting to hear the one thing they actually care about, which is whether this can move the operational needle inside a year.

The translation work we'd done beforehand was aimed squarely at those three assumptions. The startups arrived knowing this was a different kind of room, with a buyer who could act, and that they should bring their strongest commercial pitch rather than the cautious rail version they'd learned to use everywhere else.

When Authority Becomes Action

Having the authority to make a decision and actually using it are two different things. Plenty of people with the formal power to act sit on it, because the cost of getting it wrong feels heavier than the cost of doing nothing.

A few things tipped the balance the other way here.

The operator was competing for passengers in a live market. They didn't have the luxury of standing still. If they stopped improving the proposition, they'd lose ground to other modes, and they knew it. That pressure was in the room before we'd said a word.

Leadership had backed the format, and the people attending had a clear mandate. That sounds obvious, but it's where most innovation events come unstuck. They're run by someone who hasn't actually secured permission to act on whatever comes out of them. The team listens, takes it all away, and hands it to a senior group who weren't there. In this case the people in the room had been told to evaluate, decide, and follow up. They didn't have to go and ask afterwards.

We'd also been honest about what the day was for. Everyone, including the operator's own team, knew this was a commercial conversation and not an exploratory one. Nobody arrived confused about what was being asked of them.

None of that is about authority on its own. It's about building the conditions where a good decision is straightforward to make. Curating the room, framing the conversation, setting the expectations: that's the community work, and it's what makes the decision possible.

Challenge Statements That Produce Action

Most challenge statements are written as briefs. They set out what the operator wants and ask people to respond. The ones that lead somewhere are written as commitments. They make clear to everyone reading, the operator's own team included, that something specific will happen once the pitches are done.

The brief that produces a polite meeting and nothing else reads something like "we are interested in solutions that improve passenger experience during disruption." There's no buyer in that sentence. No timeline, no success criteria, no sense of what happens next. It's an invitation to send thoughts, so people send thoughts. The team reads them, holds a pleasant meeting, and that's where it ends.

The commitment version is much tighter. It names a specific problem. It describes the cost of that problem in terms the operator already tracks. It says what a good response looks like, including how mature the solution needs to be, and it spells out what follows the pitch: the next step, the budget behind it, and who will be involved.

The most valuable effect of writing it this way shows up on the operator's side. Once the commitment is named in public, with the follow-up and timeline visible, the work has momentum behind it. The wider community has seen what was promised, and that creates a quiet, healthy pressure that helps the team carry it through rather than letting it drift.

The Infrastructure of Accountability

For accountability to mean anything, the community has to be there before the event, not conjured up around it. Most innovation programmes try to build a community for a single initiative. It has no memory, no track record, and nothing at stake. Accountability in that situation is just a word.

What was already in place here was a network of people who knew each other, who shared a sense of who was credible and who wasn't, and who had ways of passing that information around. The Rail Innovation Group has spent close to a decade building that. Events, podcasts, newsletters, and the informal conversations that happen around all of them.

So by the time we ran the Supplier Challenge, the operator was stepping into something with established norms. There were startups in the room who already knew other operators, who'd been to previous events, who knew which questions to ask. Whatever happened next would be visible.

What gives that its weight is choice. The startups who applied had other places to spend their time. They were here because the community had signalled this was worth doing.

None of that can be built in the run-up to a single event. The accountability that made this challenge work rested on relationships and reputation that were already in place long before anyone wrote the brief.

The Typical Failure Mode

The way this usually goes wrong looks tidy enough from the outside. An operator decides to take innovation seriously. They set up an internal programme, maybe a dedicated team. They run an open call, or put on a demo day. Applications come in. A few pilots run. Six months later the programme has quietly wound down, and the verdict inside the organisation is that rail innovation is just hard, or the supply chain isn't ready, or the technology hasn't matured. None of those verdicts are right, but they're all comfortable enough to believe.

What really happened is that the operator tried to do, on their own, work that only holds together when there's a community around it.

The open call brought in a pile of applications, most of them a poor fit for the operator's actual situation. With no curation and no prior sense of which suppliers were credible, the team had to sort through all of it themselves, without the sector knowledge to do it well. The good companies were in there somewhere, but so was everything else.

The pitches were polite and went nowhere. Startups turned up with the defensive assumptions I described earlier, because nobody had done the translation work in advance. The follow-up was slow, because nothing had been committed to in public and no community was watching to see whether it happened.

The pilots that did get funded tended to stall at the same point. There was no funded route from a successful pilot into actual deployment. The team that ran the pilot didn't hold the operational budget. The team that held the budget hadn't been part of the pilot. So a pilot could report good results and still have nowhere to go.

What's absent in all of this is anything connecting the operator's good intentions to the rest of the sector. Without an external community to hold the memory, do the translation, and keep things moving, the operator is trying to innovate alone. That's the hardest possible way to do it.

What Changes When Operators Join

How do you tell genuine engagement from the performative kind? A few things give it away.

The clearest is whether the operator shows up when they want nothing. Sending people to events where you've got nothing to launch. Joining conversations that aren't about your own organisation. Sharing what you're learning, not just what you've achieved. That's the behaviour of someone who's part of the community rather than passing through it.

Who you send matters too. The operators who engage well send the people who actually do the work: operational leads, commercial managers, innovation leads with a real mandate. The community can tell within minutes which kind of person has walked in, and responds accordingly.

So does what you do afterwards. Genuine engagement means the learning goes back into the organisation and changes something. If you've spent a day at an event and nothing inside your business is different a month later, you were a spectator.

Then there's reciprocity. Communities run on contribution. You can't keep taking without putting something back, whether that's hosting an event, sharing data you'd normally keep close, or backing a smaller initiative that does nothing for you directly.

And there's how you handle the things you can't do. Every operator has constraints. The ones who engage well name them openly: "we can't sign a procurement contract until the next financial year, but here's what we can do in the meantime." The community has heard enough vague promises to value the honesty.

What connects all of it is a simple distinction. The operators who succeed treat the community as something they're joining, not something they're using. They put time in before they ask for anything back. They send the right people, follow through on what they said, and contribute.

That's where the real shortcut sits. It doesn't let an operator skip the work of being a credible member. What it saves is building the community from nothing, which takes years that almost nobody has. The infrastructure is already there in the sector. The price of using it is genuine membership, and that's the same work whether you built it or joined it.