Home / Sprint 2 / Demo Design

Demo Design IS AB

Sprint 2 · Due · 5 points

A hiring committee gave you 5 minutes. What do you show — and more importantly, what do you NOT show?

Sprint 2's demo isn't a feature tour. It's showing that you understood someone deeply enough to build something they couldn't have asked for. You need to design this now, while you're still building, so your build decisions serve your demo narrative.

The Demo Structure (Required Format)

  1. "Here's what I learned that they didn't tell me directly." — Show depth of understanding
  2. "Here's what I built and the key decisions I made." — Solution + rationale, not features
  3. "Here's where I was wrong and what I changed." — Iteration from feedback
  4. "Here's what would be worse if I'd handed this to AI." — Your human value

What You'll Design

1. Plan Each Demo Section

For each of the 4 demo sections above: What specific moment, decision, or evidence will you use? You don't need the final version — you need to know what you're LOOKING for as you continue building.

2. Your Core Message

What's the one thing you most want the audience to understand about your process?

3. Partner Validation

What will your partner need to confirm during the demo to validate your understanding?

The best demos don't show everything. They show the moments where YOUR judgment mattered. Start cutting now — you have 5 minutes, not 15.

What to Submit

Upload your demo design plan. This will evolve — the point is to start designing intentionally now.

Format: PDF or text submission
Due:
Points: 5
Submit on Canvas →