Scenario

DJ MackVibes has been commissioned for one of the largest parties of the year, 'All Gold Everything'. When he gets to the venue, he sets up his dj equipment, checks the sound levels, and gets ready to begin his set. Around 10pm (the starting time for the event), guests begin to trickle in. When each guest enters, they are checked for id and given a bracelet if they are over 21.

When the clock strikes 10, DJ MackVibes begins DJing. As the party progresses, DJ MackVibes employs many different hacks for assessing crowd involvement. He asks the crowd to scream if they are having a good time, looks at how many people are dancing, and gauges the overall volume of the crowd.

Individual Designs

Group Designs

  • No labels

1 Comment

  1. Hi guys,

    Thanks for all of your hard work on GR2! Below are my notes from grading feedback. Grades should be up soon.

    Scenario: Your project/problem statement is really tightly focused, pretty much just on the task of getting DJs better feedback. Make sure you keep in mind all of the things you learned from GR1 in that process, including some of the stuff that came up in class, like how patrons like to feel involved, but also how the DJ needs to have ultimate control.
    Preliminary designs: These are really slick, but I would have loved to see something hand drawn, here. Focusing on just pen and paper can lead to some really interesting ideas, and helps keep you focused on high-level elements. I'd also really like to see you think a bit more outside the box for how you're going to present engagement to the DJ. Bars just showing +/- are kind of boring. In what ways might you surface all of that information to DJ quickly, while maybe also providing some more detailed information? Keep thinking about it going forward, and really try to draw on your GR1 interviews.
    Overall: Extra points for the design for visually impaired DJs!

    A few things to note going forward, for all of the groups:
    - Try to make sure your wiki is organized. Don't be afraid to create a table of contents, for instance.
    - You may want to refine your scenario for GR3. Note that you're going to be using your scenario to brief your users, so you may want to make it a bit more task-oriented.
    - Login and basic account creation are not a good use of your time for prototyping, unless you're planning on doing something really interesting with it. You can assume that basic signup flows work fine. 

    Good luck! Let me know if you have any questions.