Hackathons have become a cornerstone of innovation, offering a platform for creative minds to develop solutions, collaborate, and network. Whether it's a university-organized event, a corporate-sponsored challenge, or an open community gathering, the success of a hackathon is often gauged by the level of participant engagement, the quality of the projects, and the overall experience. However, to get a quantifiable measure of your hackathon's success, using a Net Promoter Score (NPS) survey can be highly effective.

In this blog, we'll explore what NPS is, why it's valuable, and how to implement it to measure the success of your hackathon.

What is NPS?

Net Promoter Score (NPS) is a widely used metric that assesses customer loyalty and satisfaction by asking one simple question:

"On a scale of 0 to 10, how likely are you to recommend this event to a friend or colleague?"

Based on their responses, participants are categorized into three groups:

• Promoters (9-10): These are your enthusiastic participants who had a great experience and are likely to recommend the hackathon to others.
• Passives (7-8): These participants had a satisfactory experience but aren't likely to go out of their way to promote your event.
• Detractors (0-6): These are participants who were dissatisfied and could potentially discourage others from attending.

Why Use NPS for Measuring Hackathon Success?

NPS provides a straightforward and easily interpretable metric that reflects participant satisfaction and loyalty. Here are some reasons why NPS is particularly valuable for hackathons:

1. Simplicity: The NPS survey is short and straightforward, which ensures higher response rates. Participants are more likely to complete a single-question survey than a lengthy feedback form.

2. Actionable Insights: NPS isn't just about the score; it's also about the qualitative feedback that often accompanies it. Asking participants why they gave a particular score can provide deep insights into what worked well and what didn't.

3. Benchmarking: NPS allows you to benchmark your event against others in the industry or even against your previous events. This helps in tracking improvements over time.

4. Focus on Experience: The NPS focuses on the overall experience rather than just the outcomes (like the number of projects submitted). This holistic view can help you understand how your event is perceived.

How to Implement an NPS Survey for Your Hackathon

1. Timing is Key

To get the most accurate reflection of your participants' experience, timing your NPS survey is crucial. Ideally, send out the survey within 24-48 hours after the event concludes. This ensures the experience is fresh in their minds, leading to more accurate and detailed feedback.

2. Crafting the Survey

While the core of the NPS survey revolves around the single question mentioned above, it’s a good idea to include a follow-up question such as:

"What was the primary reason for your score?"

This open-ended question encourages participants to provide qualitative feedback, which can offer valuable insights into specific aspects of the hackathon.

3. Distributing the Survey

There are several ways to distribute your NPS survey:

• Email: The most common method. You can use tools like SurveyMonkey, Typeform, or Google Forms to create and distribute the survey.
• Event Platform: If your hackathon used a platform like Devpost or HackerEarth, check if they have built-in survey features.
• Social Media: For a more casual approach, you can share the survey link on your event's social media channels, though this might result in a lower response rate.

4. Analyzing the Results

Once you've gathered the responses, calculate your NPS using the following formula:

[
NPS = \text{Percentage of Promoters} - \text{Percentage of Detractors}
]

For example, if 70% of your respondents are Promoters, 20% are Passives, and 10% are Detractors, your NPS would be:

[
NPS = 70\% - 10\% = 60
]

An NPS score can range from -100 (if every respondent is a Detractor) to +100 (if every respondent is a Promoter). Generally, a positive NPS is considered good, and a score above 50 is excellent.

5. Interpreting the Feedback

Beyond the numerical score, pay close attention to the qualitative feedback. This feedback can help you identify specific areas of improvement, such as the venue, the structure of the event, the quality of the judging process, or the level of support provided to participants.

6. Closing the Loop

One of the most important steps after gathering NPS data is to close the feedback loop. This means:

• Acknowledging Feedback: Thank your participants for their input, and let them know how you plan to use the feedback to improve future events.
• Taking Action: Implement changes based on the feedback. For example, if multiple participants highlight issues with the Wi-Fi, ensure that it's a priority for your next event.
• Communicating Improvements: When you host your next hackathon, communicate the changes you've made based on previous feedback. This shows participants that their opinions are valued and can increase their likelihood of recommending the event.

Conclusion

An NPS survey is a powerful tool to measure the success of your hackathon. It provides a clear, actionable metric that reflects participant satisfaction and loyalty. By carefully crafting, distributing, and analyzing your NPS survey, you can gain valuable insights into how your event was received and identify areas for improvement. Remember, the ultimate goal of any hackathon is to create a positive, impactful experience for all participants, and an NPS survey is one of the best ways to ensure you're on the right track.