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."
Dig deeper—ask the Rosenbot:
More Videos
"I hadn’t realized that we were both going to need that advice."
Randolph Duke IIWar Stories LIVE! Randy Duke II
March 30, 2020
"This is a moment to rethink identity beyond UX and get creative with income streams and career paths."
Corey Nelson Amy SanteeLayoffs
November 15, 2022
"Every board member can interpret an NPS score differently depending on their role and responsibilities."
Landon BarnesAre My Research Findings Actually Meaningful?
March 10, 2022
"There was a founder who said our job was to coach people to not need us anymore, which is the kind of mindset I wish was more common."
Amy BucherHarnessing behavioral science to uncover deeper truths
March 12, 2025
"When you observe a quantum particle, its possible states collapse to one—just like user intent collapses to action."
David SternbergUncovering the hidden forces shaping user behavior
July 17, 2025
"If you dug deeper into feedback, you'd find ways to address issues without a big change."
Deanna SmithLeading Change with Confidence: Strategies for Optimizing Your Process
September 23, 2024
"The establishment mindset is colonialism manifest in the design world."
Jennifer StricklandAdopting a "Design By" Method
December 9, 2021
"Around 14 to 20 designers is usually the tipping point where having a dedicated design ops person starts to make sense."
Rachel Posman John CalhounA Closer Look at Team Ops and Product Ops (Two Sides of the DesignOps Coin)
November 19, 2020
"Therapists create space for clients to reflect and discover insights in a safe environment."
Gina MendoliaTherapists, Coaches, and Grandmas: Techniques for Service Design in Complex Systems
December 3, 2024
