The Cost of Entry

Hayden V. is leaning over a small wooden stool in Room 206, his fingers hovering just above the nylon strings of a classical guitar. The air in the hospice wing smells of lemon-scented disinfectant and the heavy, still silence of transition. He has exactly 16 minutes before the medication cycle begins and the room becomes too busy for melody. He reaches for his tablet to check a specific tuning notation he’d saved in a cloud-based app. The screen glows. Instead of his notes, he is met with a full-screen modal: “We’ve updated our Privacy Policy! Please review the 46 pages of changes to continue.” He taps ‘later.’ A second window appears: “Unlock Pro for $26/year to access offline sync!” He taps the ‘X.’ A third prompt: “Rate your experience!”

Hayden closes the tablet and plays from memory, but the rhythm is off. He’s frustrated. In a database somewhere, Hayden’s session is recorded as a ‘bounce.’ A product manager will look at the 66 seconds he spent in the app and categorize him as a ‘casual user’-someone with low engagement, someone who doesn’t really care about the product, someone not worth the high-touch features. But the categorization is a lie. Hayden isn’t casual. He is a professional in a high-stakes environment whose needs were discarded by a system that demanded more than it offered.

The Energy Vampire System

I’ve been thinking about this a lot lately because I spent three hours yesterday untangling a massive ball of Christmas lights in the middle of July. It’s a ridiculous thing to do when the sun is beating down at 96 degrees, but I couldn’t stand the sight of the green wires knotted into a fist in the garage. As I pulled at the loops, I realized that most modern software is built like those lights. We pack them away with the promise of ‘convenience,’ but when we pull them out, they require an hour of frustration before they provide a single spark of light.

I once spent $456 on a project management suite that promised to ‘streamline’ my life. Within 26 days, I went back to a paper notebook. The software wanted me to tag every thought, categorize every deadline by ‘energy level,’ and invite 6 collaborators who didn’t exist. It wasn’t that I was a ‘casual’ project manager; it was that the system was an energy vampire. It demanded a 106% commitment to the process before it would allow me to do the work.

“

A system that interrupts a man in a hospice room with a subscription upsell is a system that has lost its way. It is a system that assumes its own importance is the sun around which the user’s life orbits.

The Wall We Build

This is the great design failure of our era. We pathologize human reluctance. If people aren’t using the feature, we assume they need more education. We assume they need better onboarding. We assume they need ‘gamification’ to trick them into staying. We almost never stop to ask if the system itself is being rude.

I made a mistake like this once. I designed a feedback loop for a small community project that required 16 separate fields of data. I thought I was being thorough. I thought I was giving people the ‘pro’ experience. Out of 356 potential participants, only 6 finished the form. I told myself the community just wasn’t ‘engaged’ enough. I blamed their lack of passion. I didn’t realize that I had built a wall and was now complaining that people weren’t climbing it for the fun of it. I had ignored the reality of the activation tax-the price a human pays just to get started.

The Flypaper Fallacy

There is a specific kind of arrogance in assuming that more features equal more value. We see it in everything from smart refrigerators to social media platforms. They want us to stay. They want ‘dwell time.’ They want ‘stickiness.’ But stickiness is just another word for friction. If I’m trying to walk across a room, I don’t want the floor to be sticky. I want it to be smooth. I want to get to the other side. Modern systems are increasingly built like flypaper, and then we have the audacity to call the flies ‘casual’ because they struggle to pull their wings free.

Designing for the Crisis Moment

We need to stop designing for the person who has nothing but time and start designing for the person who is currently untangling Christmas lights in a heatwave. Design for the person whose kid is crying, whose phone is at 6% battery, and who just needs to find one piece of information before the light turns green. If your system can’t handle that person, it isn’t ‘robust’-it’s demanding. It’s a house guest that refuses to leave and keeps asking for snacks while you’re trying to sleep.

In my work with various technical frameworks, I’ve seen this play out 186 times. A team will build a ‘comprehensive’ tool. It will have 56 different toggles. They will spend $676 on a marketing campaign to explain how it works. And when the metrics come back showing that people only use 6% of the features, the team gets defensive. They say the audience ‘isn’t ready’ for such power. They call them ‘casuals.’ They don’t see that the users were ready for power, but they weren’t ready for the 16-hour learning curve that came with it. They had a job to do, and the tool became the job.

“

He’s the furthest thing from a casual musician. But he uses a clip-on tuner that has one button. It does one thing. It tells him if the string is in tune. It doesn’t ask for his email. It respects the music by getting out of the way of the musician.

From Dwell Time to Time Saved

We need more one-button solutions in a world that is obsessed with 46-function dashboards. We need to stop pathologizing the ‘exit’ and start celebrating the ‘success.’ A successful user isn’t necessarily the one who spends the most time in your app; it’s the one who gets what they need and leaves so they can go be a person. If we shifted our metrics from ‘engagement’ to ‘time saved,’ we would see a radical transformation in how we build things.

If we can’t build that, then we aren’t really building tools; we’re just building more knots for other people to untangle.