Muscle Memory
In early November, a new interface, information architecture, and workflow blessed the EntryThingy users. Our rebuild was complete. What came after was a bitter lesson: users had spent years building habits around the old design. Those habits didn't care that the new version was better.
§The Emailer Problem
The legacy emailer module was one we needed to fix. To send emails in the previous version, you navigated to your user profile, selected preferences, then emailer, and then composed and sent. That's not where email belongs. It was a silly architectural decision, but the emailer had lived there for fifteen years. Our users knew precisely where to locate it.
We moved it to a tools dropdown. Immediately, 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 logical home. But muscle memory kept pulling people back to the old residence, and when they arrived to an empty room, they assumed the worst: something broke, and the new owners were not taking care of the product.
This created a real support burden. No bugs. No outages. Just hundreds of users who couldn't reconcile the interface in front of them with the one etched into their palms.
§The Diagnostic Question
Every time one of these tickets lands, I 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?
If someone opened this app for the first time today, with no history and no habits, would they find this feature without help? That matters for acquisition, but it wasn't what our current users cared about.
If a fresh user would struggle too, the design needs work. If thousands of long-time users stumble by unlearning what their fingers already know, we're dealing with a transition cost. Real, but temporary.
Muscle memory is a latent form of usability, and we broke it.