• casual and fun playtest environment (with snacks)
• students invited visitors, such as officers from Stanford transportation
• after an introduction from ariam, guests had an opportunity to play and test the prototypes
• Scoot Secure
  • bridge the gap between students and stanford transportation
  • stanford transportation is old school
    • expects phone calls
    • expects community
  • current solution - drone view gamkified learning
  • chat bot - don’t need to interact with scary deputies
    • maybe table to show students that transportation is just people
  • not trying to replace current solutions but trying to support the current solutions
  • handed out the business card - old school
  • don’t know where building is
    • on the far side of campus
  • safe zone app - just stanford
  • students don’t know where to call public safety
  • sounds like pub channels are misaslgiend

Debrief

• thought we would go through full presentation
  • ended up just showing prototype
  • people will disrupt the plan
  • use the pieces that will be really important, but don’t worry about getting every detail
• figure out how to cater your prototype to your audience
  • important to be adaptive in response to how different people interact
• didn’t spend that miuch time on the solution, ended up talking about many other different things
• surprised by the ideas that feedback generates
  • invite others in from different perspectives
• challenging to not guide the user
  • users didn’t know either - asking if they are doing it right
• easier to let go if you share earlier and often

Documentation - why is it important

• helps you understand your own thinking
• helps others better understand your thinking and design work
• invites others into your work through artifacts (show vs. tell)
• document a little bit every week

Reflections