Railway · Strategy · Senior · 45 to 60 minutes

Which bets should Railway make next?

Railway is a cloud platform that helps developers deploy and run applications and related services. Answer this product management case and get it graded line by line against a weighted rubric.

Strategic prioritization
Platform product sense
Tradeoff analysis
Roadmapping
Executive communication

The situation

Railway has grown quickly over the past year and is seeing strong adoption, but recent reliability problems have damaged customer confidence. The CEO and product leadership want a recommendation for the next planning cycle on which company-level bets to make now, and which to delay. The candidate set of work includes a second generation hardware platform, more data center capacity, backups, a native CDN, compliance work, and improvements to the core developer experience. The tension is that each path helps a different goal. Reliability and capacity work may repair trust, but much of it is not immediately visible to prospects. Product improvements may help adoption and retention, but can look tone-deaf if service quality remains uneven. Compliance could matter for larger customers, but it competes for the same engineering attention as foundational platform work. Leadership is also debating how public to be about the roadmap, knowing that missed promises could further erode trust. You are the senior PM asked to recommend a plan that is strategically sound, sequenced, and credible to both customers and the team.

What to produce

A 1 to 2 page strategy memo.

Your answer must

Define 3 to 5 decision criteria and use them to compare the candidate investments.
Recommend the top 2 major bets for the next 6 months and explain why the other options should wait.
Lay out a sequence across the next 2 planning cycles, including key dependencies between infrastructure, compliance, and product experience work.
Propose 3 to 5 metrics or signals to track service health, customer trust, and business impact.
Include a communication approach for customers and internal teams, including what you would and would not commit to publicly.

Constraints

You can prioritize only 2 major company-level bets in the next 6 months, routine maintenance still continues.
The plan must work while Railway continues serving a rapidly growing user base.
Stay within Railway's current business, do not assume acquisitions, new product lines, or a major pricing change.
Any public commitments must be specific enough to build trust and conservative enough to be credible.

Format

Use headings for decision criteria, recommended bets, sequencing, metrics, and communication.

How Railway actually played it

Railway's team reflects on a year with a million-plus new users and real product wins, but with reliability stumbles that cost customer trust, and sets two priorities: rebuild trust and polish the core product loop. It lists concrete work such as a second-generation hardware platform, more data center capacity, backups, a native CDN and compliance work. A candid example of a strategy reset published for customers.

Admit where reliability hurt trust and prioritise fixing it ahead of new features.
Pick two themes for the quarter and list the work under each.
Keep the roadmap public so customers can hold the team to it.
Balance foundational work with visible product improvements.

Built from Where Railway is, and where it's going (Summer 2026) by Angelo Saraceno, Railway.