Design for the moment, not the generation

Read the research without turning it into a persona

In its May 2023 explanation of its research approach, Pew Research Center emphasized comparing generations at similar life stages and accounting for other explanations for differences. Its warning matters for a marketing brief: differences between younger and older people today do not automatically establish permanent generational traits.

There is also fresh material worth questioning rather than copying. Deloitte’s 2026 Gen Z and Millennial Survey announcement, released on May 13, describes respondents’ interest in stability, skills and well-being. These are findings from a work-focused survey, not proof that a particular event format or campaign message will succeed. They can suggest questions to investigate with your own audience.

For example, if a report prompts an interest in skills, ask prospective guests what they hope to become better at. Do not jump straight to an AI workshop. The useful answer might be presenting an idea, choosing a creative collaborator or starting a difficult conversation. External research supplies a starting hypothesis; your program still needs its own evidence.

Start with one decision you want to make easier

Choose a concrete action before selecting a channel or creative concept. For an event, that might be accepting an invitation, arriving with confidence or continuing a conversation afterward. For a content program, it might be using a practical resource. Specify the action and the benefit the participant should receive in return.

Then write down three unknowns: the motivation, the obstacle and the proof required. An illustrative workshop brief could read: participants want to develop a usable creative brief, worry that the session will be too abstract, and need to see a sample exercise before committing. That sentence already points toward a better landing page, invitation and session design.

The discipline is consistent with GOV.UK’s guidance on learning about user needs: investigate what people are trying to accomplish, their current behavior and the problems they encounter. Its guidance treats suggestions not grounded in user evidence as assumptions to investigate. Applying that service-design principle to marketing is an editorial proposal here, not a finding about campaign performance.

Listen for friction, not agreement

Recruit a small, deliberately varied exploratory group. Include people who have declined similar invitations, newcomers and repeat participants. A handful of conversations can help uncover possible problems; it cannot estimate how common they are across an entire market. Keep that distinction in the research notes.

Ask about a recent real decision. What did the person attend? What nearly stopped them? Which detail helped them decide? What was awkward on arrival? Avoid asking only whether your proposed concept sounds appealing. Polite agreement is a weak foundation for committing a venue budget.

Record observations separately from interpretation. “Did not know anyone attending” is an observation. “Needs an introduction before arriving” is a possible design response. Another response could be clear solo-attendee messaging, a hosted opening activity or a less formal seating arrangement. Test the response instead of treating it as the only solution.

• Ask: What would you need to know before saying yes?
• Ask: Tell me about the last time you decided not to attend something similar.
• Ask: What would make the time feel well spent, even if you met nobody new?
• Ask: Which parts would you prefer to observe, discuss or try yourself?

Give people more than one way into the experience

Use the research to create a few participation options without fragmenting the event into a complicated menu. In an illustrative evening for a design community, guests could begin with a short demonstration, choose a small discussion or explore an annotated display at their own pace. The subject stays coherent while participation varies.

Build those options into the invitation. Describe what happens, how long it takes, whether prior knowledge is needed and whether attending alone is normal. A photograph of an impressive room cannot answer those questions. A short, specific explanation can.

At the venue, translate the promise into operations. Brief hosts on welcoming solo arrivals. Make introductions opt-in. Give discussion leaders an opening question and permission to let people listen. Offer a clear way to leave a session without embarrassment. These are proposed design choices to test, not universal preferences of younger adults.

Keep the brand recognizable through the quality of the content, the tone of the welcome and the care taken with transitions. Avoid making every participation route look like a different campaign. A small team can pilot two routes before investing in a larger program.

Ask for the preference you actually need

If a choice would improve the experience, let someone express it directly. Ask which topic interests them, whether they would like an introduction, or which language they prefer for practical information. Explain what the answer will change. Leave optional questions genuinely optional.

Do not infer a desire for public recognition, a preferred communication style or a personal cause from an age group. For an illustrative nonprofit gathering, someone might care deeply about the work while preferring to participate quietly. Offer recognition as a choice rather than treating visibility as the reward.

This is a design recommendation, not privacy-law guidance: collect less when less is enough to deliver the experience. Define who uses each answer and when it is no longer needed. If the team cannot explain how a field improves the guest journey, remove it from the pilot.

Measure whether you delivered the promise

Choose a primary measure tied to the original decision. If the promise was practical learning, ask whether participants can identify a technique they intend to use, then offer an optional later check on whether they used it. If the promise was useful conversation, ask whether they had one and whether they want help continuing it.

Track the operating cost alongside the outcome. A carefully hosted format may require more staff time. Record preparation hours, attendance and the number of follow-up requests the team can actually fulfill. A program that creates more promises than the team can keep needs redesign even when satisfaction looks encouraging.

Where volume allows, compare one meaningful change at a time, such as two invitation descriptions with the same audience and offer. Do not call an increase causal when the venue, guest list and program all changed. Small samples, self-selection and enthusiastic respondents limit what an event survey can establish.

Segment findings by expressed needs where possible. Did first-time participants find it easy to join? Did people seeking practical learning leave with something usable? Report counts with percentages, and preserve uncertainty when a group is small. Age can be an additional lens if it answers a specific question, rather than the default explanation.

Make the next brief small enough to learn from

For the next campaign cycle, choose one audience decision, conduct exploratory conversations and revise one part of the journey. Set a baseline, agree on a useful outcome and reserve time for a short debrief. Document the assumptions that survived contact with participants and the ones that did not.

Do not promise a formula that works for every younger audience. Geography, language, familiarity with the subject, accessibility needs and available time can all change the design question. Ask which of those conditions matters here and make the next test specific enough to answer it.

A useful final brief might say: help first-time participants feel prepared to join a conversation they care about. That gives a writer, designer, host and event producer a shared job. It also gives the team something concrete to evaluate after the room empties.