How do we encourage participants to go through and create a free account on our platform?
Posted: Mon Feb 10, 2025 4:36 am
Whether that's 24 hours or a few business days, you want to make sure that you're taking the time to connect with participants, build meaningful connections with them, and answer questions they have. Participants are much more likely to submit a project if they have had their questions answered.
Another thing to note is that if people submit early, they can continue to make changes, edits, and modifications to their submission until the deadline. If you're the hackathon manager and you see a couple of submissions come in early, there's no problem in reviewing them and reaching out to participants to let them know what they might be missing or if there are additional aspects of the submission that aren't clear enough.
You're much more likely to be satisfied with the results when you're communicating exactly what you're looking for.
Michelle: I would highlight some latvia telegram screening specific resources to use to set expectations for the participants. Give them some example project ideas.
That will help them gauge the stage they should get their project to. Give them example project code and ideas to get them passed those first few really hard moments of a hackathon of figuring out where to start.
Michelle: Making it a requirement is a big one. It goes back to helping participants submit. Make sure those resources are really clear and that you're communicating with them that they need to create an account. It sounds like that's their first step in your hackathon, to go create a project, so have that everywhere and remind them throughout. You can also show them the benefits of your platform.
Dani: There are also ways of including it within the actual submission flow, like making sure that you ask them to provide the email that they used for signup or some other verification so that participants can demonstrate that they were able to create an account.
Another thing to note is that if people submit early, they can continue to make changes, edits, and modifications to their submission until the deadline. If you're the hackathon manager and you see a couple of submissions come in early, there's no problem in reviewing them and reaching out to participants to let them know what they might be missing or if there are additional aspects of the submission that aren't clear enough.
You're much more likely to be satisfied with the results when you're communicating exactly what you're looking for.
Michelle: I would highlight some latvia telegram screening specific resources to use to set expectations for the participants. Give them some example project ideas.
That will help them gauge the stage they should get their project to. Give them example project code and ideas to get them passed those first few really hard moments of a hackathon of figuring out where to start.
Michelle: Making it a requirement is a big one. It goes back to helping participants submit. Make sure those resources are really clear and that you're communicating with them that they need to create an account. It sounds like that's their first step in your hackathon, to go create a project, so have that everywhere and remind them throughout. You can also show them the benefits of your platform.
Dani: There are also ways of including it within the actual submission flow, like making sure that you ask them to provide the email that they used for signup or some other verification so that participants can demonstrate that they were able to create an account.