About this product
Most teams don't lose because of a bad idea. They lose because the team was built wrong.
"1 frontend, 1 backend, 1 AI/ML, 1 presentation" sounds perfect. But nobody's skills overlap, so nobody can check anyone else's work. If one part breaks, only one person can fix it.
This 2 page guide is the strategy I use instead, from Ep. 02 of Breaking Hackathons Down with Hema.
What's inside:
• Why the usual team advice fails
• My rule: every person brings 2 skills, every skill is covered by 2 people
• A sample 4 person skill table you can copy
• How to cross-verify each other's work before submission
• Why you shouldn't team up only with close friends
• 4 questions to ask before someone joins your team
• A blank team sheet and a quick checklist to fill in before you register
Who it's for: college students and first-time hackathon participants (SIH, college hackathons, online hackathons).
Format: PDF, 2 pages. Free to share with your team.
Try it in your next hackathon and share your results with me!