Improving Legacy Software: How Much Better Does it Have to Be?
Summary
Feature improvements to software that has been around for while often results in frustration for the users because of resistance to change. Even if the new experiences are proven to be better, old habits and biases interrupt adoption speed. In this talk, Paula will explore strategies for proving out where legacy software needs improvement and where research can guide and debunk myths about legacy software and legacy users.
Key Insights
-
•
Legacy habit paths form over years and become deeply ingrained through frequent and complex workflows.
-
•
Breaking established habit paths in software can cause cognitive overload and reduce productivity.
-
•
Windows settings navigation evolved through nine different habit paths over 27 years, with some changes improving and others worsening user experience.
-
•
Measuring before-and-after effects on habit paths is crucial to determine if a change is better, worse, or the same for users.
-
•
Multiple methods exist to evaluate habit disruption, including time on task, cognitive load, emotion tracking, and telemetry.
-
•
Telemetry is often missing or insufficient for tracking habit paths, requiring manual analysis or enhanced tooling.
-
•
Smaller user bases, such as enterprise teams with fewer than 20 users, have an advantage in deeply understanding and managing habit formation.
-
•
Different user populations may face varying levels of pain when habit paths change, making user segmentation critical in design decisions.
-
•
Consistency must be balanced between respecting legacy habits and aligning with newer interaction patterns from other platforms.
-
•
There is an opportunity for the industry to collaboratively track common habit paths to unify user experiences across products.
Notable Quotes
"People form habits on software that become efficient, so they naturally resist changes that force new habits."
"Breaking a habit path can cause users to repeatedly retry workflows, leading to frustration and cognitive overload."
"From 1995 to 2012, Windows users had a consistent start button habit path to reach settings; Windows 8 broke that 15-year habit."
"If we don’t respect legacy habits, we risk interrupting workflows and causing users to have a bad day."
"Measuring changes before and after is key because you can’t know the impact without a baseline."
"Collecting habit path data in every study over time builds a data set that informs product decisions."
"In the small enterprise user base scenario, you can get down and dirty to know exactly how people use the software and how habit changes will affect them."
"Consistency with legacy habits versus new platforms depends on knowing your audience and the likelihood of pain from breaking habits."
"Breaking habits for new users, such as Mac users switching to Windows, requires mapping mental models carefully to reduce pain."
"Habit changes sometimes must happen, but measuring and designing to respect them avoids mortifying changes."
Or choose a question:
More Videos
"Civic action as proof of concept to get government moving, to get the wheels turning was really interesting."
Sarah Auslander Betsy Ramaccia Gordon RossInsights Panel
November 18, 2022
"We need to factor in the specifics of the social situation when designing interaction models and gestures for smart glasses."
Lukas Moro“Feels Like Paper!”: Interfacing AI through Paper
June 11, 2025
"I’m most excited to get back in the office because I miss that culture and feeling like I’m working with friends every day."
Andreas Huebner Amy Takata Craig BrookesWhat Is It Like To Be Part of The UX Team at Compass?
March 11, 2021
"We were lost in the forest and you come across this compass, maybe all time rusty, but still something a little bit useful."
Benjamin RealMaturity Models: A Core Tool for Creating a DesignOps Strategy
October 1, 2021
"Connection is the energy between people when they feel seen, heard, and valued without judgment."
Alla WeinbergDesign Teams Need Psychological Safety: Here’s How to Create It
September 8, 2022
"Hiring is hard, but firing the wrong person is harder — so we must be thoughtful and deliberate."
Meredith BlackScaling Design Culture
November 6, 2017
"It’s those value propositions that need to be decoded at the human level and then coded back into the data, not vice versa."
Jill FruchterInconvenient Insights: The Researcher's Role is to Stay Curious
March 29, 2023
"I love getting other people in there. Shared ownership means people are going to reference it more often."
Gabrielle VerderberDocumentation Your Team Will Actually Use
October 3, 2023
"If you don’t need a designer to create designs, what happens to designers?"
Llewyn PaineDay 1 Using AI in UX with Impact
June 10, 2025
