What’s the best way to contribute to a hackathon as a non-technical team member?
I’ve gathered a few suggestions based on my best collaborative experiences:
Focus on growth.
Join a project that can teach you something you want to learn.
To begin, don’t focus on inventing a product or a feature. Instead, tell a story or identify a problem.
Build a team of diverse talent and thinkers.
Seek out team members who will help you brainstorm and become passionate about executing on an idea.
Think outside the box.
Don’t limit the scope of what you can create to software—film a short video, write a book, or make a work of art.
Identify your minimum viable product (MVP).
Work relentlessly on reducing the scope of your team’s project to a much smaller product.
Empower every team member.
Identify responsibilities that everyone feels comfortable and excited to take on—maybe team members want to explore other interests, like developing graphics or communications.
Establish product-market fit.
Spend time researching other products that deliver similar ideas and help the team make more informed decisions with this data.
Use your domain expertise.
Find experts or find data to support insights to back your team’s project.
Reduce. Research. Recycle.
Not all answers require new code. Reduce your workload by researching the best, most expedient paths into unchartered territory. In some cases, this may mean recycling old code.
Dance your way to the finish line.
Become the choreographer of your technical team for the final presentation—can you make them dance?
Most importantly, have fun and under-promise so you can over-deliver!