What I've Learned About Rail Supplier Challenges That Actually Deliver

I've helped design supplier challenges for rail organisations over a number of years now. Some of them produced real operational outcomes. Others launched with energy and quietly disappeared within six months. The difference between the two is almost never about the quality of the startups who applied. It's about what happened in the design phase, weeks before anyone pitched.

The pattern is consistent enough to describe. There are six things that, if I see them missing in the planning stage, tell me a challenge is going to underdeliver. None of them are complicated. Most of them get skipped anyway.

The Operational Sponsor Problem

The first question I ask is who, operationally, owns this challenge. If the answer is an innovation team, a communications function, or a strategy unit, with no clear owner inside the part of the business that would actually use the solution, it's already in trouble. The operational team needs to shape the brief from the start and commit to engage with what comes out of it.

Research shows that when there's no person in charge of follow-up, implementation, or strategic continuation, the activities become the goal rather than the outcomes.

Without that, the challenge becomes someone else's project and any output struggles to find a home. This is what separates genuine problem-solving from innovation theatre.

Vague challenge statements attract irrelevant solutions

Even with the right sponsor, a poorly written brief will undo the work. If it reads "we want to improve passenger experience" or "we're looking for digital innovation", you'll get a hundred applications and almost none will be relevant. A good challenge statement describes a specific problem, in specific terms, with enough context for a non-rail company to understand what's being asked.

The discipline of writing it well forces the organisation to know what it actually wants. When I work with challenge setters, I push them to publish the full timeline: entry deadline, shortlist date, pitch session date, decision date, and what the next stage looks like for a successful applicant. That converts the challenge into a sprint, which is how a startup naturally operates.

Equally important is a short paragraph explaining what the organisation is responsible for and what sits outside its remit. The Hitachi Rail Light Rail challenge we ran in March with the Rail Innovation Group did this well. Each statement included context about the operating environment of UK light rail: high-capacity systems in mixed traffic, integrated into urban streetscapes, with specific constraints around maintenance windows and shared infrastructure. The context didn't make the challenge easier but it did make it answerable.

Why curated invitation beats open calls

A well-written brief still needs to reach the right people. There's a temptation to broadcast a challenge as widely as possible, assuming more applications mean better odds. In practice, an open call attracts a high volume of poorly matched submissions, exhausts the assessment panel, and signals to serious companies that the organisation hasn't thought carefully about who they want to hear from.

Curated invitation consistently produces better outcomes.

Curated invitation consistently produces better outcomes. The process starts with technical fit, then maturity. The Hitachi challenge specified TRL 6 to 9, the right range for near-term deployment. A company at TRL 3 might have brilliant science, but they're not ready for the operational conversation buyers want to have.

I'll often have a short call with a company before formally inviting them, to check the timing works and that they'll put a senior person in the room. That five minutes prevents a lot of disappointment on both sides.

Decision-maker presence is non-negotiable

A curated list and a clear brief still won't convert if the wrong people are hearing the pitches. If the people in the room can listen but can't commit to next steps, the energy collapses. Startups can tell within the first few minutes whether they're pitching to people who can move things forward or to people who'll have to take it back to someone else.

When the alignment is strong, the buyers lean in. They're asking follow-up questions that go beyond the slide just shown, glancing at each other in a way that suggests they're already thinking about who internally would need to be involved. The decision-maker's presence has to be locked in before the date is announced, not added as a "we'll see who's free" on the day.

Honesty about constraints saves everyone time

Decision-makers in the room also means the constraints can be named honestly. Every rail organisation has things it can't do: existing supplier relationships, budget cycles, asset ownership boundaries, safety processes. If those aren't shared upfront, the challenge will attract solutions that look promising on paper and turn out to be unbuildable in practice.

Organisations worry that being open about constraints makes them look inflexible. The opposite is true. The companies they want to attract are sophisticated enough to recognise that every organisation has limits. What they're assessing is whether the rail organisation understands its own situation well enough to articulate it. That reads as credibility, not limitation.

I'll work with teams on phrasing so constraints are clear without sounding defensive. "We can't change the asset" sounds closed off. "The asset sits with our leasing partner, so any solution will need to be deployable without modifying the rolling stock" describes the same constraint and reads as a useful design parameter.

The follow-through plan most organisations skip

All of this design work is wasted without a plan for what happens after the session. If the organisation hasn't worked out which budget pays for the next stage, who manages the relationship, and what the route to deployment looks like, the momentum dies in the days after the event.

When I get challenge setters to write the follow-up structure into the brief, it forces them to actually have a plan. "Successful applicants will enter a six-week scoping engagement with a defined budget and a decision point at the end" is something a small company can resource against. "Successful applicants will be invited to discuss next steps" means nothing.

Measuring success beyond the press release

Even with follow-through in place, organisations tend to measure the wrong things. Most assume success means a contract signed at the end. When I push on that, it becomes clear they want several things at once, on different timescales.

Some outcomes are immediate: did the right startups apply, did the pitches surface new ideas. A second set sits in the medium term: did conversations turn into scoping engagements or partnerships. A third is long term: has the session changed how the supply chain perceives the organisation. Press coverage and attendance numbers are seductive because they're easy to count. They don't tell you whether the session worked.

The evidence organisations fail to capture

The piece that almost always gets missed is structured feedback from the startups themselves. Organisations debrief internally but rarely go back to applicants and ask how they found the process. Was the brief clear? Was the timeline workable? Those answers are where the most useful improvements live, and they walk out the door if nobody asks.

A good session produces evidence: which startups are credible, which problems are well-formed enough to attract serious responses, and how the internal team handles unfamiliar suppliers.

The single most important thing to get right

Get the operational sponsor right, and most of the rest follows.

The question I'd ask any organisation before they launch their first challenge is this: when a startup wins, who in your organisation will spend the next twelve months making it work? Not who will manage the procurement. Not who will write the press release. Who will sit with that company, integrate their solution into operational reality, and carry the responsibility if it doesn't deliver.

If the organisation can name that person, and that person is in the room from the start, the challenge has a chance.

If they can't, the challenge is a publicity exercise wearing the costume of an innovation programme.