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
"Women, people of color, LGBTQ folks, and other minorities are deeply familiar with having to modify bodies and bodily practices as steps for protection and self preservation."
Tamara HaleWar Stories LIVE! Tamara Hale
March 30, 2020
"We should feel empowered to propose research initiatives that stakeholders aren’t explicitly asking for."
Joanna Vodopivec Prabhas PokharelOne Research Team for All - Influence Without Authority
March 9, 2022
"Key is a reminder that these metrics reflect what is authoritative and important to the customer and the business."
Saara Kamppari-Miller Nicole Bergstrom Shashi JainKey Metrics: Comparing Three Letter Acronym Metrics That Include the Word “Key”
November 13, 2024
"I am responsible not just for insights but for my team's well-being, legal commitments, and fiduciary responsibilities."
Nalini P. KotamrajuTwo Jobs in One: Being a “Leader who is a Researcher” and a “Researcher who is a Leader"
March 10, 2021
"We found patterns that product teams didn’t expect or even want to look for."
Ian JohnsonLatent Scope: Finding structure in unstructured data
June 11, 2025
"I know exactly this job, all its problems and dysfunctions, and I don’t want to do that anymore."
Greg PetroffExit Interview #1: Greg Petroff: From Silicon Valley Executive to Sonoma County Possibilitarian
September 24, 2025
"The reason some of these tools aren’t embraced right now is a little bit of fear and lack of understanding."
Frances Yllana Jorge Arango Maria Taylor Briana ThomasThe Big Question about Impact: A Panel Discussion
September 24, 2024
"Change really cannot be done by any individual person. Change is a team sport."
Maria GiudiceRemaking the Making Company: Moving from Product to Experience
June 9, 2016
"If your topic is already tackled exceptionally by a prior book, go deeper or wait until the market shifts."
Louis RosenfeldCoffee with Lou: Should You Write a (UX) Book?
March 7, 2024
