Designing Things People Love
Every digital experience is competing for a moment in someone's day. Not their undivided attention. A moment. How you use it is the whole game.
I start most mornings surrounded by objects I love to use. The way they feel in my hand, the way they look sitting on a desk, the way they do exactly what they’re supposed to do without asking anything extra of me. That experience carries into how I read. The publications I reach for first and the ones where the layout, the typography, the visual pacing of the story makes the whole thing feel worth the time.
This isn’t a trivial observation. It’s the one I keep coming back to when we’re deep in a design project at Artversion.
People move through their days collecting small experiences. A morning ritual. A commute. A moment between meetings where they pull out a phone and try to accomplish something quickly. These moments have texture, and they are where thoughtful design quietly does its best work. They have a pace and a feeling. And when someone arrives at a digital experience — a website, an app, a product interface — they bring all of that with them. They bring their Tuesday morning. They bring the fact that they’ve already made fifteen decisions before noon. They bring a very finite amount of patience and attention, and they are offering some of it to you.
The first obligation of design is to honor that by solving the problem. Whatever brought the user there — a search, a form to complete, a product to find, a decision to make — the interface has to work. It has to be accessible. It has to be fast and clear and usable by the widest possible range of people. There is no version of good design that fails at this. Craft without function is just aesthetics, and aesthetics without usability is decoration. We don’t do decoration.
But here’s what I’ve learned from years of designing for businesses that are serious about their audiences: solving the problem is the floor, not the ceiling.
The experiences people return to, recommend, remember — those aren’t just functional. They’re considered. Someone thought about what it feels like to move through them. Someone thought about the person who arrives in a hurry and needs to find something in three clicks. Someone thought about the person who arrives with time and curiosity and wants to be rewarded for exploring. Someone thought about the moment of completion — the confirmation, the next step, the quiet signal that says you did it, you’re done, everything worked.
That layer of thinking is what separates design that performs from design that resonates. And it’s exactly as rigorous as the functional work. It just requires a different kind of attention — attention paid not to the interface in isolation but to the human being on the other side of it, living their actual life.
When we start a project, we think about those small moments. The daily ritual. The fast-paced schedule. The user who is distracted, or tired, or doing three things at once. We think about what it means to earn someone’s attention and then use it well. We think about what it would take for this experience to be the one they reach for first — not because it’s the only option, but because it genuinely feels like the right one.
That’s the work. Solve the problem completely. Then make it worth loving.




