We celebrate when a feature works perfectly. The demo succeeds, the interface looks polished, the API returns the expected response and the happy path passes QA. But what happens when the user has no data, hits an error, lacks permission or needs to recover from a mistake?

Real people rarely follow the journey we demo in meetings. Product teams often find the gaps only after a feature reaches users.

In this interactive session we take a familiar experience, booking a train ticket online, and break it: the payment app says the money went through, the booking page still says "Processing", and the user wonders whether to pay again. Through a live show-of-hands challenge and a before-and-after redesign, we look at how product, design, engineering and QA each shape that one moment.

Attendees leave with the 5-State Ship Test, a practical checklist for first use, no data, failure, restricted access and recovery that fits into requirements, design reviews, sprint planning, code reviews and QA planning.

No design background or special tools needed. The goal is to help everyone who builds technology look past "does it work?" to "can people succeed when reality doesn't follow the demo?"