Presenting

Submissions close at 4:00 · Demos 4:15–5:15

Every team gets 2 minutes to show what they did. That's short, so aim for one clear point.

What to cover

1. The problem	What were you trying to solve, and why does it matter for people biking in DC?
2. What you built or found	Show it: a map, a chart, a screenshot, a finding. What does it tell us?
3. Next steps	What would you do with more time? What should RideScore DC do with this?

Add your slides to the shared demo deck by 4:00: RideScore DC Demo Deck. Duplicate the two template slides at the front, move them into your track's section, and fill them in. We'll run every demo from this one deck.

Community Research groups: your two slides already cover these three points. See Submitting Your Findings.

Tips

• Two minutes goes fast. Pick your single most interesting result and lead with it.
• Use screenshots, not a live demo. Wi-Fi and laptops fail at the worst moment. If you want to show something live, have a screenshot as backup.
• Show your evidence. One real example beats a general claim.
• Say what doesn't work yet. Honest limits are useful to the team, and they aren't a weakness.
• Put your names on the first slide, along with a link to your code or notebook if you have one.
• Choose one presenter. It saves handoff time.