Team
Joanna,
Let’s take a few minutes to review some of your mockups, wireframes and diagrams from last week. Classmates, do the diagrams clearly describe the flow of the presenting team’s concept? How could they be improved?
“Measure twice, cut once”, “Fail Fast”, “First one’s for the trash”
Could be paper, cardboard, a sketchup model, 3D print, styrofoam, etc.
When creating a process, having each team member act out a role in the process can be an effective prototyping approach.
An extension of wireframes, click dummies can really help identify help map out how a website or mobile app might “feel” – helping to validate content and identify alternative approaches .
Especially useful for film, animations, VR, music, etc. Think garage band “demo tape”.
Create a new Google Document on Google Drive and title it “Style Guide”
“Usability Plans”, Chapter 11 in Communicating Design
*Assignments are due before class begins on Thursdays. Be prepared to present your work in class for discussion.
Let’s take a few minutes to review some of your Design Briefs.
Why use diagrams?
Organize into your your teams and consider your project. What types of diagrams would be useful for documenting the organization of your content, flow of your process, or sequence of your users’ interactions?
Pick one of the tools above and try diagraming one aspect of your project. Keep in mind that your project may have multiple sub-projects (a video sub-project and a website sub-project).
Why use mockups?
Organize into your teams again and discuss what aspects of your project need mockups. What types of mockups would help begin to prototype your project?
Pick one aspect of your project and create a mockup for it. Keep in mind that most of your projects have multiple sub-projects. Which one most fully identifies the ‘gist’ of your project? Using one (or more) of the tools listed above, create a mockup for that one.
Creating Style Guides in A List Apart
*Assignments are due before class begins on Thursdays. Be prepared to present your work in class for discussion.
Let’s take a few moments to review some of your Design Notebook entries from last week.
User Personas are a technique for capturing information about the different types of “users” for whom you will be developing your projects. In essence, User Personas help you to define your your audience(s).
Let’s take a look at a User Persona Template example.
Now, let’s create our own example together on Google Drive.
Working together with your team, take 1/2 an hour to create at least three User Personas:
User Stories are a technique for identifying specifically what each user type wants to be able to accomplish using your system. User Stories give you a checklist of features you’ll need to implement in order to fulfill the needs of your different user groups.
Let’s take a look at an example of how to implement User Stories.
Let’s create a couple of example User Stories on Google Drive.
Working together with your team, start a new Google Drive Spreadsheet and take a 1/2 hour to create at least two User Stories for each user type you identified with your User Personas.
Each User Story should follow this formula:
“As a user type X, I want to be able to Y, so that I can Z“
Design Briefs are a technique for capturing the basic requirements of a project, including target audience, message & content, project architecture, budget and timeline.
Let’s take a look at a template Design Brief.
Create a new slide in your Design Notebook and name it “Project Design Brief” and today’s date. Write a two or three sentence description of your project and provide a link to your team’s Project Design Brief.
*Assignments are due before class begins on Thursdays. Be prepared to present your work in class for discussion.