I once spent three weeks meticulously calculating the throw and lux-levels of twelve specific Soraa lamps for a minimalist gallery in Brooklyn, only to realize on opening night that I’d accidentally created a path that forced people to look at the shadows of the pedestals rather than the sculptures themselves.

I was so obsessed with the “perfect” visitor journey-a sequence of visual cues that would guide the eye with mathematical precision-that I turned the art into a series of obstacles to be navigated rather than objects to be seen. It was a failure of efficiency. I had optimized the movement of the human neck so well that the actual experience of discovery vanished.

I made it impossible for the visitors to be wrong, and in doing so, I made it impossible for them to be present. We are doing the same thing to our digital spaces, and it’s making us all a little bit stupider.

The Social Contract of the Parking Space

Earlier today, I watched someone steal my parking spot. I’d been waiting with my blinker on, positioned perfectly to swing into the space as the previous car backed out. A silver SUV, driven by a man who looked like he’d never had a thought that didn’t involve a spreadsheet, zipped in from the opposite direction, ignoring the unspoken choreography of the lot.

He followed the “onboarding” of the parking lot perfectly: find empty space, drive into empty space. He was efficient. He was conversion-optimized. He was also a complete idiot who had no understanding of the social contract or the informal “feel” of that specific street. He got the result, but he failed the environment.

This is exactly what happens when we over-optimize onboarding flows in software. We celebrate when the completion rate jumps from 62% to 84%. We high-five over the “time-to-value” metric dropping by thirty seconds. But we are graduating users who arrive at the dashboard competent at nothing but the tutorial itself.

They know how to click the blue pulsing button. They know how to follow the white glove that points to the “Settings” menu. But they have no mental map of the house. They are guests who have been led by the hand from the front door to the couch and told to sit down, without ever being shown where the bathroom is or how the kitchen floor creaks if you step on the wrong tile.

In my world of museum lighting, how this actually works is a balance of three distinct layers. When I’m lighting a gallery, I’m not just aiming a beam at a painting.

The Anatomy of Ambient Presence

• 1

  The Ambient Layer

  Usually provided by wall-washers-which defines the boundaries of the room. It tells your brain where the walls are so you don’t feel like you’re floating in a void.

• 2

  The Accent Lighting

  This hits the art directly. It is the target, the objective, the conversion event.

• 3

  The Spill

  The light that bounces off the floor or the ceiling. It’s technically “waste.” It’s unoptimized light. But without that spill, the room feels clinical, eerie, and artificial. You need the waste to make the space feel real.

When you take a new user and force them through a linear, “frictionless” path, you are effectively turning off the ambient lights. You are saying, “Don’t look at the architecture. Don’t poke around the edges. Just look at this one button we’ve highlighted for you.”

The result is a user who can perform the task but doesn’t understand the tool. They haven’t formed a mental model. Real understanding-the kind that turns a “user” into a “power user”-grows from unstructured exploration. It grows from getting a little bit lost, clicking a button that does nothing, and wondering why.

I remember the old forums, the clunky interfaces of the early 2000s where you had to wander around to find anything. It was frustrating, sure. But by the time you found the “post” button, you already knew who the moderators were, what the “vibe” of the community was, and where the archives were hidden. You absorbed the culture of the platform through the soles of your digital feet.

Today, we optimize that “waste” away. We want the user to post within three minutes of signing up. So we point them directly to the box, give them a template, and tell them to go. Then we wonder why the quality of discourse is so shallow.

There is a specific kind of fluency that only comes from “poking around.”

In a regulated digital gaming hub like

rca 77,

the engineering is often focused on speed and security-getting the deposit done, making the withdrawal fast, ensuring the balance is transparent. That’s the infrastructure. It’s vital.

But the reason people stay in a space like that isn’t just because the transaction took 40 seconds instead of 60. It’s because they eventually feel “at home” in the interface. They know where the live tables are relative to the slots; they understand the rhythm of the fish-shooting games. If you over-optimize that journey so that they never have to look left or right, they never develop that feeling of ownership. They are just clicking where the light tells them to click.

The GPS of Onboarding

If the “silver SUV man” had spent five minutes just wandering the parking lot, he might have seen how the traffic flows. He might have noticed the hierarchy of the regulars. But he was on a guided mission.

We’ve become terrified of “friction.” In product meetings, friction is treated like a leak in a dam. We have to plug it. But some friction is productive. It’s the texture on a staircase that keeps you from slipping. When you remove all friction from a learning process, you remove the “grip” that allows the information to stick to the brain.

Think about learning a new city. If you always use a GPS that gives you turn-by-turn directions, you can live in a neighborhood for three years and still not know which way is North the moment your phone dies. But if you spend your first week getting lost, taking the wrong bus, and having to find your way back by looking for landmarks, you develop a permanent, visceral map of the streets.

I think about this every time I see a “new and improved” dashboard that hides all the advanced features behind a “Simple Mode.” It looks clean. It’s A/B tested to death. But it denies the user the chance to see the complexity of the tool they are using.

It treats them like they’re fragile. It assumes that if they see too many buttons, they’ll get scared and leave. Maybe some do. But the ones who stay-the 2,143 users who would have become your most loyal advocates-now have no path to mastery. They are stuck in the “Simple Mode” of their own understanding because the onboarding never taught them how to be curious.

It’s a hollow victory. It’s like the gallery I lit. The completion rate was 100%. Every single person walked past every single sculpture. But when I talked to people at the after-party, nobody could remember the texture of the clay or the way the light hit the curves of the bronze.

They just remembered that it was easy to walk through. They had “converted” through the exhibit, but they hadn’t experienced it.

I’m still thinking about that silver SUV. He probably thinks he won. He got the spot. He saved four minutes of his life. But he’s currently sitting in his car, likely unaware that he’s blocked the entrance to the alleyway, making it impossible for the delivery truck to get through. Because he only looked at the “empty spot” (his target), he failed to see the context. He didn’t see the spill. He didn’t see the room.

We need to start building “spill” back into our designs. We need to stop being so afraid of a user who stops to look around. If someone takes ten minutes to finish a three-minute onboarding flow because they were clicking on things they weren’t “supposed” to click on, that shouldn’t be a red flag in our analytics.

Next time I’m designing a lighting rig, I’m going to leave one corner intentionally dim. I’m going to make people work just a little bit harder to see the detail. I’m going to let them get a little lost.

Because the moment they find their way back-the moment they find the art on their own terms, without me pointing a 15-watt LED at it-is the only moment that actually matters. That’s when the “user” becomes a person. And that’s when the software becomes a home.