Travel planner · 2025

Railkind

Travellers could compare tickets, but stitching a realistic weekend together still took too many tabs.

RoleTechnical product lead
TeamResearcher, designer and developer
DurationSeven weeks
Year2025
The brief

Make the next decision easier.

Travellers could compare tickets, but stitching a realistic weekend together still took too many tabs. The work began by following the real task from its first signal to a visible, understandable result.

The fictional engagement focused on one complete path before expanding the surface area. That kept interface, data and operational decisions close enough to test together.

A regional train window overlooking a river valley
Context from the fictional Railkind working environment.
Three decisions

What shaped the release.

01

Plan in whole days

Travel time, check-in and opening hours appear as part of the itinerary.

02

Keep alternatives close

A missed connection can be swapped without rebuilding the whole trip.

03

Save the useful context

Maps, notes and reservations stay attached to the day they belong to.

What the team kept

Useful after handoff.

  • Journey-search adapter
  • Itinerary builder
  • Offline-friendly trip summary
  • Component and content guidelines
“The fictional prototype helped people choose a trip they could actually enjoy, not just one they could technically book.”Placeholder researcher, Railkind · fictional testimonial