How we won a €1,000 hackathon
The practical lessons I kept from building under pressure, working as a team, and presenting something judges could understand.
A hackathon compresses product work into a very honest format. There is not enough time to hide behind a roadmap, polish every edge, or keep debating the perfect architecture. A team has to choose a problem, build a coherent solution, and make somebody else understand why it matters.
Our team left with the win and a €1,000 prize. The money made the result tangible, but the useful part was seeing which decisions survived the pressure.
We reduced the idea before we expanded it
The first version of an idea is almost always too large for the time available. We treated scope as a product decision, not a list of features we had failed to finish.
We focused on one complete path that could be demonstrated from beginning to end. Anything that did not make that path clearer moved out of the critical build.
Clear ownership beat parallel chaos
Moving quickly does not mean everybody touches everything. The work became faster when responsibilities were visible and each part had a clear owner.
That also made integration easier. Instead of discovering conflicting assumptions near the deadline, we kept checking the boundaries between the parts while there was still time to change them.
The demo was part of the product
Good work can disappear inside a confusing presentation. We designed the demo around the problem, the moment our solution changed the experience, and the result. The judges did not need a tour of every technical decision; they needed a reason to care and evidence that the core experience worked.
Shipping creates a different kind of confidence
Winning was meaningful, but finishing something together was the deeper proof. It showed me that speed, technical quality, and clear communication are not opposing goals when the team is disciplined about scope.
That lesson still shapes how I build products now: find the smallest version that proves the idea, make the important path excellent, and communicate it clearly enough that another person can see the value.