Not a Refrigerator

Watching someone use your product for the first time is painful in a very particular way. You sit next to them, try not to breathe too loudly, and watch the cursor. You expect them to move through the screens the way you designed them. Instead the cursor just hovers and wanders around, and you can tell they have no idea what they're looking at. That was me with my friend Erin, when she tested the very first version of Mint. I thought I'd built something really well thought out. It had configuration panels, detailed onboarding docs, and a pretty solid architecture for organizing files on macOS. I was proud of it. Erin just froze. While she was stuck, I remembered a podcast I'd heard about "dark patterns" in customer service design. Telecom companies and gyms bury the "cancel subscription" button in a maze of menus so you give up and stay. I used to laugh at how hostile that was. Sitting there, it wasn't funny anymore. I wasn't trying to trap anyone, but my ego as a developer had done the same thing. I'd put my user inside my own complicated logic and she was stuck in it. Eventually Erin took her hand off the mouse, turned to me, and gave me the feedback that changed where Mint went from there. "Look," she said. "If I'm paying for a tool like this, I'm buying it to save time. I want to be in and out in three seconds. But I open this app, I see all these documents and settings, and it feels as clunky as a massive refrigerator. I came here to clear my mental load, and your tool just added to it." A refrigerator. Honestly, that was the right word for it. A fridge is heavy, takes up space in the room and hums all the time, and to get anything out you have to open the door, dig around and move things. Mint was supposed to feel light, and I'd built a household appliance. After that conversation I went back to the code and threw out the whole UI. I stopped working out how to show all the features and started working out how to hide them. I cut the redundant steps and made the entry point so small and fast that using it barely felt like doing anything. I think the root of it is that builders care a lot about the process. We spend weeks on the logic, and without really noticing, we want the user to see the gears turning. We want credit for the work. Users only care about the result. They want a clean desktop and one less thing on their mind, and how it all works inside doesn't matter to them. A few weeks later, I handed Erin the rebuilt version of Mint. She ran it, the files got sorted right away, and the window was gone about as fast as it showed up. She didn't have to read any documentation. She smiled at me and said, "Finally. Not a refrigerator." --- I think good design should save people time and stay out of their way. If someone has to learn how to use your tool before it takes any friction off their plate, you've just given them a different kind of chore.