How to Plan a Successful Event: Insights from Event Review

For event novices, coming up with a creative event idea is not difficult. However, it takes experience to think through all the details, clarify the approach and process of event operations, and avoid redundant work. A key methodology in event operations is working backward. Let's adopt this approach and look at how to run a successful event from the perspective of writing an event review.

Event Overview

This section mainly serves to review the background of the event and check whether the event has deviated from its original intent. Additionally, providing the event background facilitates documentation and sharing with a wider audience.

It includes the event name, event time, event objectives, event rules, and promotional channels.

Event Name: Simply put, it should be interesting, engaging, and substantive. "Interesting" means users can tell at a glance what the event is about; "engaging" means it brings a smile; "substantive" means it highlights benefits relevant to users. Use numbers whenever possible. Keep it focused and concise.

Event Time: Set based on the objectives of each event. For short-term events, 5-7 days is generally reasonable; too short or too long is detrimental to promotion.

Event Objectives: Avoid being greedy or wanting too much. The more specific and singular the objective of a single event, the better. The more targeted and simple the message, the easier it is for users to accept. For example, if the objective is "user acquisition," it can be broken down into "new registrations" or "new transactions." If the objective is "increase user ARPU," it can be refined to "increase the ARPU of users whose purchase amounts are concentrated in the 2000-3000 range to 5000."

Event Rules: They should be written concisely and clearly. A simple test: can you explain them in one sentence and have the other person understand?

Additionally, note that promotional channels are a crucial part of the review. Often, an event fails to take off not because it was poorly executed, but because of a lack of good channels! "Good wine needs no bush" is a myth. Therefore, in the event review, we can list the specific promotional plans for each channel, including design images, copy, channel user segmentation, etc. This also facilitates listing data for each channel in Part 3, allowing horizontal comparison of channel performance.

Event Cost and Expected Outcomes

There are two main ways to estimate event costs: per-person cost (i.e., how much you are willing to spend per user) and total budget control (the total budget for each event; if the event causes a user surge, the company may not be able to bear the cost pressure, which is also quite daunting).

Total cost needs to consider labor costs + promotional costs + reward costs, etc. Labor costs include the time spent on planning, design, and development; promotional costs include the costs of each channel.

When setting expected outcomes, avoid vague statements like "increase exposure" or "raise brand awareness." Set goals with objective data! For example, if the objective is user acquisition, you can use installation activations as the performance metric. How do you set reasonable goals?

First, you can refer to similar or past events, or baseline data, and scale up accordingly.

Second, you can break down the monthly operational goals and determine what proportion of the target this event should bear. The minimum requirement for an event is that the output should cover the cost.

For example, if your event requires a total of 10,000 yuan in labor and reward costs, and the normal cost per installation activation is 10 yuan, then your event should bring in at least 1,000 installation activations to be considered a reasonable outcome.

Event Performance Evaluation

Performance evaluation should be based on your expected outcomes. If the event data meets the expected goals and the results cover the costs, the event can basically be deemed successful.

In addition to the hard metric of data, you can evaluate performance from multiple dimensions, such as user feedback, event flow, visual design, team collaboration, and cost-benefit ratio.

If the event did not achieve the desired results, we will reflect on it in Part 5.

Event Highlights

This section can record the standout points in event planning. For example, innovative event formats, excellent user feedback, compelling sharing copy, effective sharing mechanisms, etc. If the overall event effect is good or user feedback on a particular aspect is positive, we can record it and reuse it later with a different page.

Additionally, you can record excellent team collaboration during the event. For example, quick page design, good dynamic effects, high front-end development adaptability, sufficient lead time before launch, etc.

Remember to thank your team; every event's success is the result of collective effort!

Event Reflection

I believe this section is the focus of the event review. It can be summarized in three sentences: identify problems, find causes, and propose solutions.

What if the event did not meet its goals? First, break down the event objectives. For example, if the goal is the number of transacting users. Work backward to identify the path to a transacting user: browse product page - add to cart - generate order - pay for order - complete transaction. Along this path, we can collect conversion rates at each key step and use data to identify problems. To assess whether the data is healthy, you can refer to similar products' purchase conversion rates (e.g., e-commerce funnel models). If you find low page views, consider whether the entry copy is not attractive enough, the design emphasis is not prominent, or the promotional channels have issues. Additionally, you can compare the conversion rates of users from different channels to identify high-quality users.

If the product has multiple dimensions, you can also compare data across dimensions. For example, if six funds participate in the event, you can create a table to analyze the relationships among fund returns, minimum purchase amounts, page positions, button clicks, and number of buyers. Operations professionals must be adept at using data.

Furthermore, consider event optimization. For visual optimization, on a small scale, you can consider aesthetics and adaptability to different screen sizes; on a larger scale, you can run an A/B test to measure the impact of page layout on the event. For example, a lucky draw page can bring a lot of traffic, and you want to convert that traffic into sales. Then you need to carefully think about the page layout, align with users' visual starting points, and make users notice associated products while drawing. These small changes can have a significant impact on sales.

We can also reflect on the event flow and interface. The ideal flow and interface should allow users to complete the most important part with a few blind clicks without reading or thinking, and then they can decide whether to continue or share. Event operators often tend to be greedy and want to put all important information and functional entries on the main page, making it cluttered. But users' attention is usually focused, and WAP pages have limited space. In most cases, it is best to highlight one piece of information. If you try to highlight 2-3 pieces of information on one page, users may get lost. At this point, you must know how to make trade-offs.

Additionally, does your event experience align with user habits? Previously, my team ran a voice recording activity. We used a click-to-start recording method with text prompts. However, during testing, we found that almost all users instinctively long-pressed to start recording (thanks to WeChat). So we changed the recording rule. This illustrates that when your product habits conflict with mainstream product usage habits, you must respect user habits while ensuring functionality is not affected.

Beyond these user-facing aspects, we can also evaluate whether any issues occurred during execution and how well the team collaborated. For example, did the design images come out with an unsuitable style? Did you discover poor adaptability across devices during the slicing phase due to the design framework, resulting in a terrible visual experience? Did development inform you of a bug risk just before launch? Were the event platform rules unclear? Did the event traffic explode, forcing the page offline? Almost every issue mentioned here involves redoing previous work. Therefore, during the event planning phase, after the lead has drafted the initial plan, it is essential to organize an evaluation meeting with relevant personnel (design, slicing, development) to understand the event's purpose and assess whether the workload and output are proportional. If the output can cover the cost, the event can proceed. Then, discuss and refine the details thoroughly. Additionally, write a detailed requirements document, including design style, event flow, event logic, etc., for development, testing, and troubleshooting.