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
"Maturity is not linear; the tanker company had a lot to learn from the speedboat, and vice versa."
John CutlerOxbows, Rivers, and Estuaries: How to navigate the currents of change (without burning out)
December 3, 2024
"By observing Jeff's concerns and asking questions, I was able to show empathy and distract myself from getting defensive."
Darian DavisLessons from a Toxic Work Relationship
January 8, 2024
"Kristen wrote the book Design of Orgs for Design Orgs and her experience partly informed this canvas."
Dave GrayGroup Activity: Making Sense of DesignOps
November 7, 2017
"I never thought I'd say this, but can someone please for love of God, just make a RACI so we can align on who's responsible for things."
John CutlerThe Alignment Trap
November 29, 2023
"Diagrams allow us to emotionally hit pause and come back ready to dig further."
Abby CovertStuck? Diagrams Help
October 27, 2022
"You can see our organization through the homepage of our site — we each owned a rectangle."
Mark InterranteCollaboration Flows in Product Development
June 9, 2017
"The future will be struggle; we need to face that forward, not deny it."
Devon PowersImagining Better Futures
March 9, 2022
"Unbiased qualitative research does not exist. The best we can do is acknowledge and minimize biases."
Prayag NarulaHow to Empower Your Designers to Do Good Research – And Why You Want To
June 10, 2022
"Don’t overcomplicate workflows; the simplest thing that could possibly work is often best."
Peter Van DijckHands on AI #3: Claude Code for UX people
October 22, 2025
Latest Books All books
Dig deeper with the Rosenbot
How can research teams balance the tradeoff between research pacing, speed, and quality?
How should surveys be structured to balance quantitative metrics with qualitative insights?
What strategies help speed up the procurement and legal review of UX research platforms in organizations like LinkedIn?