Updates
Three Months Later: Why We Check In On Every Project
Every HackVillage project gets a check in three months after the hackathon. Here is what we ask, and what your answer changes.
By HackVillage Team · · 3 min read
Most hackathon projects stop the moment the demo ends. The laptops close, the repository goes quiet, and nobody ever finds out what happened next. We think that is a waste of good work, so every HackVillage hackathon ends with a small promise to come back.
A Check In, Three Months On
When a hackathon's winners are announced, we schedule a check in for every submitted project, not just the winners. About three months later, each team gets a short prompt asking where the project stands.
Four Honest Answers
- Still a demo. It works, but it hasn't gone further yet.
- In production. Real people are using it.
- Pivoted. The idea changed into something new.
- Abandoned. The team moved on, and that is fine to say.
Any team member can answer, and can add a short note about what happened. It takes about a minute.
Why Your Answer Matters
Your answer updates the project on your Proof of Work portfolio, so a project that shipped is shown as in production and an abandoned one is archived. Over time, these answers also show which hackathons lead to real products, which helps organizers and sponsors design better challenges.
Gentle Reminders
If a check in goes unanswered, we send a reminder when it is due and one more two weeks later. After that we stop asking and mark it as unanswered. No nagging beyond that.
Every project deserves a second chapter. Find a hackathon and start the first one.
