Lessons from Building
Experience
Lessons from Building

What Conferences Taught Me About Customer Experience

Customers don't experience your departments. They experience the outcome.

January 19, 2027

For a long time I thought events were about content. The speakers, the sessions, the agenda, the announcements, the keynotes. All of that matters, and lately I've spent real time thinking about it. But the content turns out to be only part of the experience. What people actually carry home is something a lot less tangible than the agenda. It's how the whole thing made them feel.

People experience the whole, not the parts

The most important thing helping with events has taught me is that attendees don't think in departments. They don't separate marketing from operations. They don't distinguish between the registration system, the event app, the website, the signage, the emails, and the logistics. They just experience the result, and to them it's all one thing. That's what makes customer experience both hard and kind of fascinating. The smallest interaction can color someone's sense of the entire event. A confusing check-in line. A question nobody could answer. A hallway where the flow of signage= didn't quite make sense. An unclear next step. None of those seem like much on their own. Together, they shape how the whole thing feels.

The best experiences often go unnoticed

One realization genuinely changed how I approach this work: the best experiences are frequently invisible. Nobody walks up to thank you because registration was intuitive. People don't stop to compliment clear signage. They notice bad communication far more often than they notice good communication. When it's working, success feels almost uneventful. Things just work. The attendee finds what they need, the next step is obvious, the information is there right when it's needed, and the whole thing flows. It feels effortless, and that effortlessness is almost always the evidence of a lot of careful planning nobody will ever see.

Friction is expensive

Every experience is full of little moments where a person has to make a decision. Where do I go? What do I do next? Where do I find this? Who do I ask? How does this work?

Every one of those moments costs attention and effort.

The job of experience design isn't to remove every decision, because you can't. It's to remove the unnecessary ones. That's become one of my favorite ways to judge anything I build. The question isn't how impressive is this. The question is how easy have we made this.

Details matter more than we think

I've become a little fascinated by how much small details drive the overall impression. The timing of an email. The way a webpage is organized. The clarity of a single instruction. Where a key piece of information sits. Whether the messaging stays consistent from one touchpoint to the next. None of these feel revolutionary on their own. Put together, they're the difference between an experience that feels thoughtful and one that feels frustrating. Customer experience is rarely defined by one big moment. It's defined by hundreds of tiny ones.

What building continues to teach me

Seeing our events in person, has taught me that experience is an accumulation of decisions. Not one decision, thousands of them. Small ones, often invisible ones, the choices that make things easier and more intuitive and more human and more welcoming. People may not remember every session they sat through. But they almost always remember how the experience made them feel, and that, in the end, is what customer experience has always really been about. It's a lesson that reaches well past events, into websites, products, support, and just about anything else people move through.

Lessons from Building is an ongoing series on work, craft, curiosity, and the messy middle where ideas turn into things.