How to Plan a Successful Event: Insights from Event Review

For event novices, coming up with an event idea is not difficult. However, thinking through all details, clarifying the operational approach and process, and avoiding redundant work require experience. A key method in event operations is backward planning. Let's adopt this approach and look at how to run an event well from the perspective of writing an event summary.

Event Introduction

This section mainly serves to review the background of the event and check whether the event has deviated from the original intention. Additionally, providing the background facilitates documentation and sharing with more people.

It includes 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 know at a glance what the event is about; "engaging" means it brings a smile; "substantive" means highlighting benefits relevant to users. Use numbers whenever possible. Keep it prominent 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 unfavorable for promotion.

Event Objectives: Avoid being greedy or excessive. The more specific and singular the objective, 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 amount is concentrated in 2000-3000 to 5000."

Event Rules: They should be written concisely and clearly. A test for clarity: try to explain it in one sentence and see if the other person understands.

Additionally, pay attention to promotional channels, which are an important part of the summary. Often, an event fails to explode not because the event is poorly done, but because of a lack of good channels! "Good wine needs no bush" is a myth. So in the event summary, we can list the specific promotional plans for each channel, including design images, copy, channel user segmentation, etc., which also facilitates listing data for each channel in Part 3 and comparing channel performance horizontally.

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 brings a user explosion, the company may not be able to bear the cost pressure, which is also quite scary).

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

Note that when setting expected outcomes, avoid vague phrases like "increase exposure" or "enhance brand awareness." Set goals with objective data! For example, if the objective is user acquisition, then installation activations can be the assessment metric. How to set reasonable goals?

First, you can refer to similar or past events, or daily data as a baseline, 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 output should cover costs.

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

Event Effect Evaluation

Event effect evaluation should be based on your expected outcomes. If the event data meets the expected goals and the effect covers costs, the event can basically be judged successful.

In addition to data as a hard indicator, you can also evaluate from multiple dimensions, such as user word-of-mouth, event flow, visual effects, team collaboration, and cost-output ratio.

If the effect is not achieved, we will reflect on it in Part 5.

Event Highlights

This section can record the standout points in event planning. For example, novel event formats, excellent sharing copy with good user feedback, effective sharing mechanisms, etc. If the overall effect is good or user feedback on a certain 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, page design took less time, dynamic effects were good, front-end development had high adaptability, and there was sufficient time for launch, etc.

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

Event Reflection

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

What if the event effect does not meet the target? We can first break down the event goal. For example, the goal is the number of transaction users. The path to obtain transaction users is: browse product page - add to cart - generate order - pay for order - complete transaction. For this path, we can collect the conversion rate at each key step and use data to identify problems. Whether the data is healthy can be compared with similar products' purchase conversion rates (refer to the e-commerce funnel model). If page views are low, we can infer whether the entry copy is not attractive enough, the design emphasis is not prominent, or there are issues with promotional channels. Additionally, we can compare horizontally the conversion rates of customers from different promotional channels to discover high-quality users.

If the product has multiple dimensions, we can also compare data across dimensions. For example, if 6 funds participate in the event, we can create a table to compare the relationships among fund yield, minimum purchase amount, page position, button clicks, and number of buyers. Operations must be good at using data.

Furthermore, consider event optimization. For visual optimization, on a small scale, 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 point, and let users notice related products while drawing. These small changes are highly correlated with 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 decide whether to continue or share. Event operators often tend to be greedy and want to put all important information and function entrances on the main page, making it dazzling, but users' attention is usually focused, and WAP pages have limited space. In most cases, it is only suitable to highlight one piece of information. If you try to highlight 2-3 pieces 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 did an event for recording voice, using a click-to-start recording method with text prompts. However, during testing, we found that almost all users unconsciously long-pressed to start recording (thanks to WeChat), so we changed the recording rule. This is when your product habits conflict with mainstream product usage habits; while ensuring functionality is not affected, you must respect user habits.

Beyond these user-perceived parts, we can also evaluate whether any issues occurred during execution and how well the team cooperated. For example, did the design images come out with an inappropriate style? Did you find poor adaptability across devices during slicing due to the design framework, resulting in a terrible visual experience? Did development tell you about 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 person drafts the initial plan, they should 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 costs, the event can be confirmed. Then discuss and revise the details thoroughly. Additionally, write a detailed requirements document, including design style, event flow, event logic, etc., for development, testing, and troubleshooting.