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
"Explainability requires transparency at every stage with governance ensuring fairness and equity in model building."
Ovetta SampsonResearch in the Automated Future
March 11, 2022
"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
"Design language is probably the worst language possible to speak because it’s so comfortable and confusing."
Deanna Washington Tim Allen Jeff Courcelle John Maeda Matt Raw Erica TjaderScaling Success: Paving the Path from DesignOps to VP
October 4, 2023
"Conflicts caused by layers moving at different speeds actually keep things balanced and resilient."
Brigette MetzlerScaling ResearchOps: Helping Researchers do Their Best Work
March 30, 2020
"Engineers are great at executing code but often lack connection to user experience and design processes."
Kevin M. HoffmanTheme 2: Enterprise Team Journey
June 3, 2019
"Design by means letting the people we serve lead the process and ourselves to drop our egos and let go."
Rachael Dietkus, LCSW Victor Udoewa Jennifer StricklandEverything You Need to Know about the Civic Design 2022 Call for Presentations
May 17, 2022
"Our brains are terrible at operating on only one type of information—object-oriented or context-oriented."
Alëna IouguinaDesigning Systems at Scale
November 7, 2018
"We want to build more social features around insights to encourage community discussion and connection."
Matt DuignanHITS, Microsoft's internal human insight system: From research library to living body of knowledge
July 16, 2019
"AI should be a partner to UX professionals, not a replacement for UX expertise."
Clara Kliman-SilverUX Futures: The Role of Artificial Intelligence in Design
June 7, 2023
