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
"Tags are a balance; project tags are wild and flexible, global tags must be controlled to avoid chaos."
Taylor Jennings Joe Nelson Alex KnollRepository Retrospective: Learnings from Introducing a Central Place for UX Research
March 9, 2022
"Hope generates optimistic momentum towards a possibility becoming real."
Nicole AleongFuture Orientations to Everyday Life: Futures Anthropology as a Methodology
March 26, 2024
"The team that comes up with the winning idea leaves the studio with equity and carries the idea forward."
Jeff GothelfInnovation Studios: the Engines of Enterprise Experimentation
May 14, 2015
"Leadership needs to be just as behind accessibility as the designers and professionals doing the work."
Saara Kamppari-MillerDesignOps for Inclusive Design and Accessibility
May 26, 2022
"Design ops folks meet the habit of catering so much to everybody’s increasingly trivial whims that it takes us away from the real meaty ops work."
Tess DixonC'mon Get Happy
September 29, 2021
"Being intentional about how we spend our time is the purest manifestation of our values and our value."
Liam ThurstonWhy Your Design Team Is Quitting, And How To Fix It
June 10, 2022
"Careers as ladders are what HR wants, but careers aren’t linear; they should be a jungle gym."
Ian SwinsonDesigning and Driving UX Careers
June 8, 2016
"One researcher per team for at least three days a week was considered an outrageous luxury at GDS in 2013."
Leisa ReicheltOpening Keynote: Operating in Context
November 7, 2018
"It depends was the most common answer to how do you know what you’re doing is working."
Rachael Greene Alison DavisBuilding a Design Ops Practice that Really Works (Most of the Time)
October 2, 2025
