Summary
How do you create the conditions for delivering a great customer experience on a rapidly changing platform? In 2016, Norway’s national railway company began building a new technology platform. As designers, we yearned to address the customer’s actual needs and desires, not just a fresh look and technical upgrade. But with no process, principles, tools, or internal design resources, where do you start?
Key Insights
-
•
Privatization forced MSB to relinquish control over ticket machines and IT, compelling a new digital-focused strategy.
-
•
Designers initially faced tension with developers due to different paces and priorities within agile.
-
•
Introducing 'waves' as outcome-focused releases helped align design and development processes beyond fixed sprint durations.
-
•
Design sprints kickstarted collaboration and built shared understanding across cross-functional teams.
-
•
Users prefer familiar interfaces, valuing trust and habit over new designs, complicating redesign efforts.
-
•
Simple, quick feedback tools like a 'give feedback' button can generate valuable and actionable user insights.
-
•
Open access to user feedback motivates developers to solve real user problems proactively.
-
•
Ecological validity in user research is critical—testing must happen in users’ real contexts to be meaningful.
-
•
Continuous learning loops enable teams to adapt products iteratively based on real user data and changing business goals.
-
•
Successful design in agile requires processes that create space for designing great experiences rather than forcing designers to keep up with rapid deliveries.
Notable Quotes
"The starting point was a very technical one: please make the user experience exactly the same a year from now."
"It’s not about old versus new. It’s about trust and deeply rooted habits."
"Designers felt like hamsters in a hamster wheel, always reacting, never exploring."
"Waves are defined by the outcome we want to achieve, not just by time frames."
"Google Design Sprint is the best inception strategy I know for design thinking."
"Giving the whole team access to feedback made them feel responsible and inspired to solve user needs."
"Ecological validity means the test must happen in an environment as close to reality as possible."
"We’re not building to build, we’re building to learn."
"How can developers and designers work together to create great products? That’s the question."
"One eye on the horizon and the other on the next wave is the perspective teams need to deliver quality digital products."
Or choose a question:
More Videos
"Diversity is beyond just the right thing to do. Our teams must reflect the world we’re designing for."
Doug PowellClosing Keynote: Design at Scale
November 8, 2018
"Giving parents something meaningful to do during sessions helps keep them engaged and supportive."
Mila Kuznetsova Lucy DentonHow Lessons Learned from Our Youngest Users Can Help Us Evolve our Practices
March 9, 2022
"Backcast from preferred or risky futures to start thinking about what we need to do today to get there or avoid that outcome."
Sarah GallimoreInspire Progress with Artifacts from the Future
November 18, 2022
"We can’t complain about not having a seat at the table if we don’t offer one of our own."
Lada Gorlenko Sharbani Dhar Sébastien Malo Rob Mitzel Ivana Ng Michal Anne RogondinoTheme 1: Discussion
January 8, 2024
"Who deals with chaos, ambiguity, and disruption best? It’s us, design operations humans."
Alnie FigueroaThe Future of Design Operations: Transforming Our Craft
September 10, 2025
"When executives start questioning your research details, that’s a good sign they’re engaged and trusting the process."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"When you’re talking, it’s easier to learn something new, but if you’re shy and don’t talk, you don’t learn anything."
Emily EagleCan't Rewind: Radio and Retail
June 3, 2019
"No two re-platforming journeys are exactly the same, and there isn't one single formula that works every time."
Malini RaoLessons Learned from a 4-year Product Re-platforming Journey
June 9, 2021
"Designers are often seen as bottlenecks because our work is harder to estimate and track than engineering’s."
Asia HoePartnering with Product: A Journey from Junior to Senior Design
November 29, 2023
