Event experiment

We're building a comprehensive knowledge library about product development as part of our mission. The library is for anyone looking to make better decisions — primarily decisions about product development. Whether you're an inventor, a product manager, or a Chief Product Officer, using the right research methods and experiments increases your chances of building the right things for the right audience. Today we'll introduce the Event validation method.

When to Use This Experiment?

An Event is the right choice when the goal is to confirm that the target audience genuinely feels the problem and is willing to spend time, and possibly money, on it. All before the product itself exists.

• The target audience can be reached through communities, meetups, or social media.

• The final product is content or education (a course, book, or program), or it can first be delivered live.

• One-on-one interviews have already been done and a larger sample is needed.

• Willingness to pay needs validating, not just stated interest.

Basic Experiment Principles

A live event is organized around the problem the product is meant to solve: a meetup, webinar, workshop, or small conference. The time and money people invest to attend serve as measurable evidence of demand.

• Define the hypothesis and success threshold. Before launch, decide what the event should confirm (that the problem exists, willingness to pay, a working channel) and which numbers will count as success. Set the threshold in advance so the data isn't bent to fit the conclusion afterward.

• Choose the format by signal strength. A free webinar is a low barrier and weaker evidence. An in-person event takes more time but yields more reliable data. A paid ticket also tests willingness to pay.

• Build the program around the problem. The title, description, and content promise a solution to a specific pain, not a product pitch. Only then do registrations measure interest in the problem rather than in the brand or the speaker.

• Promote through the future product’s channels. Spread the event through the same routes that will later be used to acquire customers. Event platforms such as Luma, Meetup, or Eventbrite help distribute invites, handle registrations, and track conversion out of the box. The experiment then also tests how reachable the target audience is and what a registration costs.

• Run the event and use the breaks. During the program, watch how the audience reacts: questions, engagement, requests for a follow-up. Breaks are ideal for short unstructured conversations. At the end, offer a next step, such as a presale, a waitlist, or a paid follow-up.

• Collect and evaluate the data. Track registrations, invite-to-registration conversion, show-up rate (the share of registrants who actually attend), tickets sold at the target price, and the share of attendees who take the next step afterward. The decisive signal is the comparison against the baseline. If the topic draws several times more people than the community's usual events, most registrants show up, and some of them pay or sign up for the next step, the problem is validated and it's time to move on to an MVP. A full room with no interest in the next step, on the other hand, points to an interesting topic but weak willingness to buy a solution.

• Identify the risks. An Event measures interest in the topic, not in a specific solution. A well-known speaker, an existing audience, or free food can inflate the results. An aggressive pitch at the end makes it hard to tell whether interest is real. Preparing an event costs more time and money than a landing page or customer interviews.

Real-World Experiment Example

Link to research: Rent the Runway case study

The idea came when Jennifer Hyman's sister spent all her savings on an expensive Marchesa dress for a wedding, despite owning dozens of others. She had already been photographed in all of them. Jennifer Hyman, then a Harvard Business School student, and Jennifer Fleiss turned this into a hypothesis: women want a different dress for every occasion but don't need to own them. Before building anything, they broke the idea down into three risky assumptions and tested each one separately.

• Willingness to rent: At Harvard, they rented a room, displayed donated designer dresses, and let women try them on. They asked whether the women would rent a dress for a tenth of its price. 35% said yes, confirming core demand.

• Renting without trying on: An online model doesn't allow fittings, so they repeated the event at Yale, where the dresses could only be viewed. Based on the Harvard feedback, they added a wider selection. Willingness to rent rose to 55%, so the missing fitting didn't put customers off.

• Choosing from a photo alone: The final test simulated a website. In New York, they asked 1,000 people from the target audience whether they would rent a dress based only on a photo in a PDF. About 5% said yes, which was enough proof of a viable market for the founders.

The tests also revealed the value of photos of real customers wearing the dresses, which help others picture how a dress will fit them.

What Can Be Tested With This Experiment?

The main value of an Event is that it measures behavior instead of words: people give up time, travel, and often money. It's strongest in the early stage, when the problem and demand are being validated.

• Existence and intensity of the problem: whether a topic built purely around a specific pain draws registrations and attendance well above the community's usual level.

• Willingness to pay: whether tickets sell at a price close to the planned product price.

• Acquisition channel: which channels bring in registrations from the target audience and at what cost.

• Target segment: whether registrants have the role, company size, and needs that match the assumed persona.

• Content product: whether live delivered content sparks follow-up questions, engagement, and requests for more, signaling demand for a course, book, or program.

• Presale of a follow-up product: what share of attendees preorder the product or join the waitlist after the event.

Other Names for This Experiment

1. Event Smoke Test