My finger is hovering over the ‘Submit’ button, but I am frozen because I cannot remember for the life of me if ‘Submit’ sends the form directly to the supervisor or archives it for 36 hours of mandatory review. It is the same screen I looked at 16 days ago. The same beige background, the same 12pt font, the same vague icon of a folder that looks like it was designed in 1996. Yet, here I am, failing a test I never signed up to take. I am being punished for not having a photographic memory of a developer’s idiosyncratic naming conventions. This is the friction that kills. It isn’t a slow server or a clunky API. It is the sheer, exhausting weight of being asked to remember things that don’t matter.

The Labyrinth of Necessary Recall

Zephyr T. understands this in a way that most UX designers never will. Zephyr is a refugee resettlement advisor, a man who lives in the narrow, jagged gaps between international law and human survival. His desk is a graveyard of sticky notes because the software he’s forced to use is a labyrinth of 56 different sub-menus.

He told me last week that he spent nearly 106 minutes trying to find a specific housing voucher that he knew he had saved, but the system’s search function required a 16-digit case number he hadn’t yet memorized.

“Every time the computer asks me to remember a code,” Zephyr said, his voice dropping into that low, gravelly tone of a man who has seen too much, “I lose the thread of the person sitting across from me. I stop looking at the mother who needs a coat for her son and I start looking at a database error.”

The Modern Pathology of Recall

I’m thinking about this because I just did something I’m slightly ashamed of. I met someone for coffee-a potential collaborator-and the moment I got back to my car, I googled her. I wanted to see her history, her past projects, the things she didn’t mention. I wanted to build a digital map of her so I wouldn’t have to rely on my own porous memory of our 36-minute conversation. It’s a modern pathology, isn’t it? We are so terrified of the blank spaces in our recall that we outsource our social lives to a search engine.

This is why I find the current state of digital design so offensive. It assumes we have the mental bandwidth to learn its specific, quirky language. If you call it a “Bucket” in one version and a “Container” in the next, you aren’t being creative; you’re being a tax collector. You are taxing my memory.

Intuition is Just Familiarity

Designers often talk about “intuitive” interfaces, but intuition is just a fancy word for things we’ve already learned. Nothing is truly intuitive; it’s just familiar. When a system is truly seamless, it acknowledges this. it doesn’t force you to build new neural pathways for mundane tasks. It meets you where your habits already live.

Assuming Infallibility

I once spent 6 hours trying to fix a mistake I made in a spreadsheet. I had deleted a row because I thought I remembered what was in it, but I was wrong. I was off by one digit. That single failure of memory cost the project $676 and a whole lot of my dignity.

The software didn’t warn me. It just let me fail. We are fundamentally unreliable narrators of our own lives. We forget where we put our keys 6 times a week; why would we remember where a ‘hidden’ filter is located?

The Rage of Being Lost

There is a specific kind of rage that comes from being lost in a place you’ve been to a hundred times. It’s a digital vertigo. You know the button is there. You can almost see the ghost of it on the screen. But it’s gone, or it’s moved, or it’s been renamed something like “Discovery Insights.” This isn’t just a nuisance. For people like Zephyr, it’s a barrier to empathy. Minimalism often hides the very things we need, forcing us to remember their locations instead of just seeing them. It’s a visual lie that creates a mental burden.

I remember reading a study-or maybe I just imagined it, which would be fitting-that claimed we lose about 26% of our productivity just to context switching. But context switching isn’t just moving from one app to another. It’s moving from “doing” to “remembering how to do.” Every time you have to recall a shortcut or a path, you are switching contexts. It’s a heavy lift.

The Self We Are Designing For

Sometimes I wonder if we’re building a world that only works for people who are currently caffeinated and under the age of 26. We design for the peak-performance version of ourselves, the version that has 126% focus and no distractions. If your software requires me to be my best self just to navigate it, then your software is a failure. It should work for my tired self. It should work for my distracted self.

The Permission to Forget

Zephyr eventually found that housing voucher. It wasn’t in “Housing.” It wasn’t in “Vouchers.” It was in a folder labeled “Active_06,” a category he had created in a moment of panic months ago and then completely forgotten. That’s the real cost. It’s the erosion of trust between the tool and the user. Once you realize a system won’t help you remember, you go back to the sticky notes.

I’m looking back at that ‘Submit’ button now. I’ve decided to just click it and see what happens. I refuse to let this screen occupy any more space in my head. I have other things to think about. The machine can keep its categories and its labels. I’m done being its librarian. When you finally stop trying to remember, you realize how much room there is to actually breathe.