Team roles and ownership

Draft status: this is initial content, not reviewed domain expertise yet.

The first principle

Hackathon teams lose time when ownership is unclear. The problem is rarely lack of effort. It is too many people making partial decisions in the same space.

Roles should answer: who decides, who executes, who reviews, and who protects the final story?

Core ownership areas

• Product owner: keeps the problem, user, and scope coherent.
• Build owner: owns implementation path, technical risk, and integration order.
• Design owner: owns flow clarity, visual hierarchy, and demo legibility.
• Pitch owner: owns story, slides, timing, and rehearsal.
• Submission owner: owns final links, forms, video, repo, and deadline checks.

One person can hold multiple roles. The important part is that every role has a named owner.

Decision rhythm

Use short decision moments:

1. Start: choose challenge, user, and claim.
2. Midpoint: cut features that do not prove the claim.
3. Final hours: freeze demo path and pitch story.
4. Submission: one owner checks every artifact.

Draft warning signs

• Nobody can say what the demo must prove.
• Two people are editing the pitch without a final owner.
• The team adds features because the core flow feels weak.
• Submission details are discovered in the last ten minutes.