Muscle Memory Is the Best UX
We recently overhauled EntryThingy, an app people have relied on for two decades. New interface, new information architecture, new workflows. The rewrite went well. What came after was harder: users had spent years building habits around the old design, and those habits didn't care that the new version was better.
Suboptimal routines baked into muscle memory are harder to change than the software itself.
The Emailer Problem
One of the design decisions we wanted to fix was the old emailer. To send emails in the previous version, you navigated to a user profile. That's not where email belongs. It made no sense architecturally, but it had lived there for fifteen years, and people knew exactly where to find it.
We moved it to a tools dropdown -- a logical home. Immediately, the support tickets rolled in. "I used to send emails from the profile page. Where did it go?" The feature wasn't missing. It was two clicks away in a place that actually made sense. But muscle memory kept pulling people back to the old location, and when they arrived at an empty room, they assumed something broke.
This created a real support burden. Not bugs. Not outages. Just a wave of users who couldn't reconcile the interface in front of them with the one etched into their hands.
The Diagnostic Question
Every time one of these tickets lands, I force myself to pause before responding. The question I sit with: Is this person lost because their muscle memory is steering them to a place that no longer exists? Or is our interface genuinely unclear?
Put differently: if someone opened this app for the first time today, with no history and no habits, would they find this feature without help?
That distinction matters. If a fresh user would struggle too, the design needs work. If only long-time users stumble, we're dealing with a transition cost -- real, but temporary.
We're also shipping faster now. The interface might shift again next month if we find a better pattern. That compounds the problem. Every change asks loyal users to override a reflex they've spent years reinforcing.
Build with Care, Change with Respect
Muscle memory is quietly one of the most powerful forms of usability. People don't just learn a workflow -- they absorb it into their hands. When something lives in the same place for a decade, finding it stops being a conscious act. It becomes automatic. That automaticity is a gift your users gave themselves through repetition, and rearranging the furniture takes it away.
You should generally resist breaking that. When you can't resist, do it knowing the cost isn't just a redesign. It's asking thousands of people to unlearn something their fingers already know.