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 of Norway’s railways forced MSB to relinquish core IT assets, challenging design teams to deliver digital services without full system control.
-
•
MSB’s designers initially faced pressure to replicate an old user experience, despite technical backend changes requiring significant redesign.
-
•
Users often resist change because they trust familiar interfaces, equating stability with reliability rather than prioritizing modern design.
-
•
Introducing ‘waves’—value-focused releases—helped bridge designers’ need for exploration and developers’ need for speed.
-
•
Google Design Sprints proved effective for cross-functional alignment and rapid, inclusive ideation despite tight deadlines.
-
•
Simple, lightweight feedback mechanisms like in-app buttons and Trello boards can generate rich user insights if effectively managed.
-
•
Opening user feedback channels to the entire product team fosters ownership and encourages developers to solve user problems proactively.
-
•
Ecological validity in research—testing in realistic user contexts—is critical to understanding the true impact of product changes.
-
•
Continuous design requires balancing the company’s long-term vision with short-term iterative delivery and frequent learning loops.
-
•
The key challenge is not integrating design into agile, but enabling designers and developers to collaboratively create excellent user experiences through appropriate processes.
Notable Quotes
"We were told, can you please make the user experience exactly the same a year from now."
"Our users like their old house—they don’t necessarily want to learn something new, they want trust and familiarity."
"Designers felt like hamsters on a wheel, always reacting and never able to explore or refine ideas."
"A wave is really just a sprint but defined by the outcome we want to achieve, not just a time frame."
"Google Design Sprint is the best inception strategy I know for design thinking because you learn without thinking about learning."
"Opening the feedback board to the whole team made developers feel responsible and inspired to solve user needs."
"What users say they want and what they really need can be very different; you need to be careful about how you interpret feedback."
"When you do a release, you’re really saying, here’s what I’m thinking: how does this work in your world?"
"We need processes that accommodate design instead of designers becoming the hamster in the agile wheel."
"One eye on the horizon and the other on the next wave—that's the perspective product teams need to deliver quality digital products."
Or choose a question:
More Videos
"If you are silent about your pain, they will kill you and say you enjoyed it."
Zariah CameronReDesigning Wellbeing for Equitable Care in the Workplace
September 23, 2024
"The top priority is often the lack of a priority, resulting in teams spending 50% of their time jumping between priorities."
John Cutler Harry MaxPrioritization for designers and product managers (1st of 3 seminars) (Videoconference)
June 13, 2024
"Working in enterprise can feel like chaos with unclear directions and too much noise from new initiatives every six months."
Nick CochranGrowing in Enterprise Design through Making Connections
June 3, 2019
"You should assess feedback before making decisions; implementing feedback right away can cause the wrong solution or disruptions."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"We started the Digital Service as a subsidiary company of the government, not just a government unit."
Magdalena ZadaraZero Hour: How to Get Far Quickly When Starting Your Digital Service Unit Late
November 16, 2022
"We didn’t exploit the knowledge gap. Everyone was willing to say I don’t know. Can you help me?"
Nova Wehman-BrownWe've Never Done This Before
June 4, 2019
"We need to learn the domain, the technology, the algorithm, and the data—not enough to code, but enough for meaningful discussions."
Liwei DaiThe Heart and Brain of the AI Research
March 31, 2020
"My phone buzzed again. I have a job this weekend for you and your team to help on the COVID response if you’re available."
Gordon Ross12 Months of COVID-19 Design and Digital Response with the British Columbia Government
December 8, 2021
"The doing is the same; the being is entirely different."
Tutti TaygerlyMake Space to Lead
June 12, 2021