Hackathon Team Formation

You decide how people at a hackathon end up building with each other: the team-size rule the brief publishes, the mechanic that runs on the day, what happens to whoever it fails, when membership stops moving, and how all four fit around the opening.

This is the participant-to-participant problem. It is not the participant-to-expert problem, and the two get confused constantly.

What you own, and what is already decided

You own:

• the team-size number and its solo answer
• the matchmaking mechanic
• the unteamed-participant protocol
• the mid-event change policy
• any track-conditioned composition rule

Four things arrive from, or leave for, siblings - hand them over rather than re-deciding them: