When we start designing an event, one of the first questions we often ask is: Who is our audience?
We look at job titles, career stages, organization types, ages, geographic locations, membership status and whether someone is a first-time or longtime attendee.
All of that information is useful.
But it doesn't necessarily tell us why someone chooses to attend.
And if we want to design events that create meaningful connections, deliver real value and ultimately influence behavior, we need to go deeper.
We need to understand what our attendees value.
Demographics Tell Us Who. Values Help Us Understand Why.
Think about two attendees who look almost identical in your registration data.
They're the same age. They have similar job titles. They've been in the industry for roughly the same amount of time. They even work for similarly sized organizations.
It would be easy to assume they want the same things from your conference.
But one may be attending because professional advancement is incredibly important to them. They're looking for education, new skills and access to people who can help them take the next step in their career.
The other may care most about belonging. They're attending because they want to reconnect with colleagues, strengthen relationships and feel part of a professional community.
Same demographic profile.
Very different motivations.
And potentially very different event experiences.
That's why demographic segmentation can only take us so far.
Stop Asking Only What Attendees Want
One of the easiest traps in event planning is asking attendees what they want and then building an event around the answers.
What sessions do you want next year?
Do you want more networking?
Would you attend another reception?
What topics should we cover?
Those aren't bad questions. But they tend to produce tactical answers.
Instead, we should also be asking questions like:
What are you trying to accomplish by attending?
What would make this event worth your time and investment?
What challenges are you currently facing?
Who do you need to meet?
What would make you feel like you belong here?
What do you hope will be different after you leave?
Those questions help us uncover the motivation behind the request.
Because when an attendee says, “I want more networking,” the solution isn't automatically another cocktail reception.
Maybe what they're really saying is:
I need to meet people who understand the challenge I'm facing.
Or:
I want access to people further along in their careers.
Or even:
I come to this conference every year, but I still don't feel like I know anyone.
Those are three completely different problems—and they require three very different design solutions.
Listen in More Than One Way
Understanding what matters to attendees also means moving beyond the annual post-event survey.
Surveys are valuable, but they're only one piece of the puzzle.
Consider using:
Pre-event surveys
Focus groups
Stakeholder interviews
Registration questions
Mobile app polling
Facilitated conversations
Advisory groups
Empathy mapping
Behavioral and participation data
And don't underestimate the value of simply talking to attendees.
Ask someone why they keep coming back.
Ask a first-time attendee what almost prevented them from registering.
Ask someone who hasn't attended in three years what changed.
Sometimes the most useful event data doesn't come from a dashboard. It comes from a conversation.
Turn Values Into Design Decisions
Gathering insights is only valuable if we're willing to do something with them.
Once we understand what our attendees value, we can begin using that information to make intentional design decisions.
If connection matters, don't just add more networking time. Create structured opportunities to help people find the right connections.
If professional growth matters, consider how sessions connect to one another. Could you create learning pathways instead of a collection of unrelated breakouts?
If belonging matters, look at the entire attendee journey. What does the experience feel like for someone walking into the opening reception alone? How are first-time attendees welcomed? Who gets represented on stage?
If recognition matters, how are you creating opportunities for attendees to contribute their expertise rather than simply consume content?
If impact matters, show attendees what happens because this community comes together.
The answer isn't necessarily to add more.
In fact, understanding what people value may give you permission to do less—but make what remains more meaningful.
Design for Behavior, Not Just Satisfaction
This is where event strategy becomes especially powerful.
A successful event shouldn't only leave attendees saying, “That was great.”
We should be asking:
What do we want people to think, feel or do differently because they attended?
Maybe we want a new member to become actively involved in the organization.
Maybe we want an experienced professional to become a mentor.
Maybe we want attendees to implement something they learned when they return to work.
Maybe we want someone who felt disconnected from the organization to finally feel like they've found their community.
When we know both the desired behavior change and the values motivating that audience, we can design experiences intentionally to help bridge the gap between the two.
That's very different from simply filling an agenda.
Reconnect With What Matters
This week's MPI article featuring David Allison and his work around values was a good reminder that understanding people requires us to look beyond the categories we put them into.
The same is true for events.
Our attendees aren't just registration types, job titles, generations or audience segments.
They're people making a decision about whether your event deserves their time, attention and investment.
Understanding who they are is important.
Understanding what matters to them is where the real opportunity begins.
So before you add another session, reception or networking activity to your next event, ask one more question:
What does our audience truly value—and does the experience we're designing reflect it?
That's where strategy-first event design starts.
