There are plenty of big things in the world worth getting annoyed about. This is not one of them. But it still drives me completely nuts.
Walk into a bookstore and look for science fiction, and the sign says Science Fiction & Fantasy. Libraries do it. Online retailers do it. Bookstores do it. And I am convinced this classification system was invented by people who did not particularly care about either genre.
I love science fiction: hard science fiction, speculative science fiction, near-future science fiction. Give me black holes, orbital mechanics, generation ships, artificial intelligence, first contact, terraforming, time dilation and the occasional existential problem involving the future of humanity.
Fantastic.
Fairies? Not so much. Elves? I'm good. Orcs? Hard pass.
This is not a criticism of fantasy. Fantasy has a massive audience, plenty of brilliant writers and people who adore it. I suspect a lot of fantasy readers feel exactly the same way about science fiction. They probably do not walk into a bookstore hoping to find a richly imagined magical kingdom only to think, “You know what this story really needs? A detailed explanation of orbital transfer windows.”
They are different genres. They overlap sometimes, sure, but not enough that shoving them together makes sense to the people who actually care about them.
And yet someone, somewhere, decided:
Space stuff. Magic stuff. Same aisle.
Small thing. Drives me insane.
And then you start noticing these things everywhere
Salsa in the condiment aisle is another one. Ketchup is a condiment. Mustard is a condiment. Mayonnaise is a condiment. Salsa is something I spend ten minutes wandering around looking for before discovering it three shelves below barbecue sauce because apparently everything you put on food eventually ends up in the same philosophical category.
Or the haircut place. You make an appointment for 2:00. You arrive at 1:55. At 2:10, someone walks in without an appointment. And somehow the person with the appointment and the person who just decided they might like a haircut today are now participating in the same queue.
Again, none of these things is a disaster. Nobody is writing congressional testimony about fantasy shelving or haircut scheduling.
But the irritation is real.
More importantly, these small frustrations change behavior. You stop going to that store. You use a different retailer. You make an appointment somewhere else. You do not make a dramatic announcement about it. You just quietly stop coming back.
Events work exactly the same way.
We worry about the big stuff because it is easy to see
When meeting professionals talk about attendee experience, we tend to think about the obvious things. Was the keynote good? Was the food good? Was the hotel nice? Did the technology work? Was the program valuable? Did the event app crash? Was the room too cold?
Those things absolutely matter.
But I think we underestimate the cumulative effect of the small stuff: the little moments where an attendee thinks, Why is this harder than it needs to be?
One moment probably does not matter. Ten of them do. Twenty of them definitely do.
And when the event is over, the attendee rarely fills out the survey saying:
I will not return next year because there were eleven tiny operational annoyances that individually seemed insignificant but collectively made this event feel harder than it should have.
They just do not register next year.
Then attendance drops 4%. The following year it drops another 3%. Everyone starts talking about changing demographics, travel budgets, content strategy, membership trends and competition for people's time.
All of those things may be real.
But sometimes death comes by a thousand paper cuts.
The registration desk is one of the easiest places to see it
You registered six weeks ago. You paid. Your information is correct. You received the confirmation email. You showed up when you were supposed to.
Then you stand in line for twenty minutes because the registration process treats you exactly the same as someone who walked in off the street ten minutes ago and decided to attend.
Why?
Those are not the same transaction.
One person needs a badge. The other person needs to create a registration, enter contact information, pick sessions, select meals, sign something, provide payment, wait for a credit card transaction and possibly ask six questions.
Meanwhile, the pre-registered attendee is standing there thinking:
I already did all of this.
That is not a registration problem. The registration worked.
It is a flow problem.
And the attendee does not care which department owns the problem. They just know they are standing in line.
Speaker management has the same problem
Imagine a five-person panel.
Four speakers submitted everything on time: bio, headshot, presentation, AV needs, release. Done.
The fifth speaker did not.
Maybe the speaker ignored six reminders. Maybe their assistant thought someone else was handling it. Maybe they uploaded the wrong presentation.
Whatever happened, now the entire panel is waiting during rehearsal because one person's deck is being transferred from an email attachment while the AV technician tries to figure out whether there are embedded videos.
The other four speakers did everything correctly.
They still pay the price.
This happens constantly in events. A process designed around the exception slows down everyone who followed the process.
We should notice that.
Food is another one
An attendee tells you months in advance that they have a nut allergy. They did exactly what the registration form asked them to do. They trusted the process.
Then lunch arrives. There is a buffet. Nothing is labeled clearly.
Now the attendee has to find a banquet captain and ask, “Does this contain walnuts?”
Then someone disappears into the kitchen. Maybe they come back with an answer. Maybe they are not sure. Maybe the attendee decides it is easier not to eat.
That moment is tiny in the context of a three-day conference.
But not to the person standing there wondering whether lunch is safe.
To that person, it may be the thing they remember. Not the $100,000 general session. Not the beautiful scenic. Not the closing keynote.
Lunch.
We tend to design for completion instead of experience
This is where I think event operations sometimes go wrong.
We ask: Did registration work? Yes. Everyone got registered.
Did we collect dietary information? Yes. It is in the database.
Did the speakers submit presentations? Mostly.
Did the badges print? Yes.
From an operational checklist perspective, everything is green.
But that is not the same question as:
Was this easy for the person experiencing it?
Systems love completion.
Humans experience friction.
And those are two different measures.
A registration process can be technically successful while still being irritating. A meal function can meet the BEO perfectly and still leave someone uncomfortable. A speaker portal can collect 95% of the files and still create chaos because the last 5% is not surfaced clearly enough.
The event can work and still feel hard.
Small friction also has a multiplier effect
The interesting thing about small frustrations is that they rarely stay isolated.
The long registration line makes someone late to the opening session. Now they enter while the speaker is presenting. That distracts the room. The attendee misses the introduction. They sit in the back because those are the only seats available. Now they cannot see the screen very well.
At lunch, their dietary request is unclear.
The afternoon session runs ten minutes late because one speaker presentation was not ready.
Now they miss the shuttle.
None of those problems is catastrophic.
Together?
That attendee had a lousy day.
And we may not even know it.
The best operational teams remove friction before attendees notice it
I increasingly think this is one of the most important jobs in event planning.
Not adding more.
Removing friction.
Separate pre-registered attendees from onsite registration. Have badges ready. Put obvious dietary labels on the buffet. Surface incomplete speaker requirements weeks before the event. Make room changes propagate everywhere. Give staff the information they need without making them hunt through six systems. Make signage obvious. Make Wi-Fi instructions simple. Make the QR code work. Make the room easy to find. Make the next thing obvious.
None of this is particularly glamorous.
Nobody posts a photo on LinkedIn saying:
Incredible execution today. Our dietary labels were extremely clear.
But attendees notice when these things are missing.
They notice because suddenly they have to do work.
And attendees did not come to your event to troubleshoot your event.
We should probably pay more attention to quiet rage
Every event has it.
The person whose badge is wrong for the third year in a row. The exhibitor who cannot figure out where to ship a box. The speaker who has received four different presentation deadlines. The attendee who registered for a session but cannot get in because someone ignored room capacity. The sponsor who submitted their logo twice and gets another email asking for their logo. The board member who cannot find the meeting room. The person who stands in the coffee line for fifteen minutes and reaches the front just as someone announces the next session is starting.
Nobody flips a table.
They sigh. They complain to the person next to them. They make a mental note.
That is the dangerous part.
Because dramatic failures get fixed.
Quiet irritation often does not.
The fantasy aisle problem
That is why the science fiction and fantasy thing bothers me.
Not because it is important.
Because it is a perfect little example of what happens when the system makes sense to the person organizing it but not to the person using it.
Someone designing the bookstore thinks:
These genres are adjacent. Put them together.
The reader thinks:
I came here for spaceships. Why am I sorting through dragons?
Both perspectives are understandable.
Only one of them is the customer.
Events have versions of this everywhere.
The registration system makes sense to the administrator. The speaker workflow makes sense to the education department. The meal process makes sense to catering. The event app makes sense to the vendor. The room diagram makes sense to operations.
The attendee experiences all of them.
They do not care which department owns which process.
They experience one event.
Maybe attendee retention is an operational metric
We spend a lot of time thinking about how to attract attendees.
Marketing. Email campaigns. Discounts. Keynote announcements. Early-bird registration. Social media.
All important.
But perhaps we should spend just as much time asking:
What makes someone hesitate before coming back?
Not the obvious disasters.
The little things.
The friction.
The confusion.
The waiting.
The unnecessary steps.
The moments where someone did exactly what we asked them to do and still had to solve the problem themselves.
Those experiences accumulate.
And over time, they become part of how someone feels about an event.
Maybe they cannot explain why they stopped attending. Maybe they just say, “I'm not sure it's worth it anymore.”
That should scare us more than a bad survey score.
Because by the time someone decides an event is no longer worth the effort, the problem may have been building for years.
The goal is not perfection
Events involve humans.
Humans are going to change things. Speakers will miss deadlines. Attendees will arrive without registering. Rooms will change. Food requirements will appear onsite. Laptops will refuse to cooperate. Someone will always forget something.
We cannot eliminate every little frustration.
But we can pay attention to them.
We can ask better questions.
Where are people waiting? Where are they confused? Where do they have to ask staff for something that should have been obvious? Where are people being punished because someone else did not follow the process? Where are attendees entering information we already have? Where are our own staff quietly maintaining a workaround because the official process does not actually work?
Those are good places to start.
Not because any single one will destroy the event.
Because fixing them makes the event feel easier.
And easier matters.
People rarely say:
“This conference had exceptional operational friction reduction.”
They say:
“That event was really well run.”
Then they come back.
Which, now that I think about it, is probably the entire point.
And while we're fixing things, somebody please separate science fiction from fantasy.
I have been through enough.
Pull Quotes
Dramatic failures get fixed. Quiet irritation often does not.
Systems love completion. Humans experience friction.
Attendees did not come to your event to troubleshoot your event.
The attendee does not care which department owns which process. They experience one event.
Maybe attendee retention is an operational metric.