Daily Archives: April 5, 2022

Apr 5

via GIPHY

PROJECT 1: Humanizing Product Design (Etsy) (Alaska)

Go through each task/deliverable below together in class.

Work in class today on How Might We’s, Goals, Product Statement, and possibly get to Scenarios/User Task Flows. Schedule time with team to meet for completing other tasks for next Tuesday.


DUE THURSDAY (NO CLASS MEETING)

TASKS 8-11 Deliverables

Turn deliverables into Team folders on Google Drive found on Slack #0_classinfo. Label each file accordingly by task number and name. Product statements will also be turned in on #project1 Slack Channel.

TASK 8 – HOW MIGHT WE?

More Info: How Might We Process, Tips, and Examples

For this task you will be writing and clustering “how might we” questions to help you zero in on your approach to improving/redesigning your product based upon your assigned prompt. By reframing your discovered pain points and insights from all of your research as “How Might We” questions, you’ll set yourself up for an innovative solution. You want to turn insights, themes or problem areas from your research into opportunities or alternatives. Asking “How Might We” questions and grouping the answers should then lead to your prioritized goals in the next step. 

How to Turn In:

  1. Clustered groups of “How Might We” questions. 
  2. Format is up to you: Can turn in a clear photograph of your hands-on process, or a Google Doc, or link to Figma, Figjam or Invision Freehand board, or designed in Illustrator or Google Slides? Whatever makes the most sense for your team!

TASK 9 – GOALS

More Info: How to Develop and Prioritize Goals + Examples

For this task you will be writing and prioritizing 3-5 goals each for the User, Brand, and Business. Your goals should arise from the “How Might We” process. You will try and answer those clustered and prioritized “How Might We’s” from the last step and translate those answers into goals. These solutions/goals ideally should stem from previous research you conducted as well and not just be made up. You will still have the opportunity however in later phases to test out your ideas to validate them – if you are still trying to prove earlier hypotheses.

How to Turn In:

  1. List of at least 3-5 goals for each: User, Brand, and Business.  
  2. Priority Pyramid or Priority Matrix (choose one method to demonstrate the prioritization of your goals) 
  3. Format is up to you: Can turn in a clear photograph of your hands-on process, or a Google Doc, or link to Figma, Figjam or Invision Freehand board, or designed in Illustrator or Google Slides? Whatever makes the most sense for your team!

TASK 10 – PRODUCT STATEMENT

More Info: How to Write a Product Statement + Examples

For this task you will be writing a product statement. In one sentence describe: What is your main product redesign solution according to your assigned prompt? Who is it for? and How are you meeting the goals that you set?

How to Turn In:

  1. One written product statement posted to the #project1 Slack Channel. Also turn into your Google Drive to keep track of it.
  2. 2 Peer Reviews of other teams’ product statements. Leave them feedback on Slack on how to improve the statement. Ask yourself if you understand what they are trying to do, for whom, and how they are going to do it, but all in a succinct manner.

TASK 11 – SCENARIO(S)/USER TASK FLOW(S)

More Info: How to Develop Scenarios and User Flows + Navigation + Examples

Write brief scenario(s) that describe the user (your personas), their needs, and goals in relation to your product redesign. Write a scenario for each new feature or adjustment you are making to the product. 

Create user task flow diagram(s) alongside each of your scenarios, which are highlighting the changes and adjustments you are making to your product. The user task flow should help you understand each screen and action that is necessary for you to create in your next step. You are also making sure the flow is logical, easy to understand, and seamless.  

How to Turn In:

  1. Scenarios for each of the new features or adjustments you are implementing in your product redesign. These scenarios should be addressing your user personas.
  2. User Task Flow Diagrams for each scenario. (You can use InDesign, Illustrator, Power Point, Google Slides, or Invision Freehand or Figma – whatever you feel most comfortable in.)
  3. Format is up to you: Can turn in a clear photograph or scan of your hands-on process, or link to Figma, Figjam or Invision Freehand board, or designed in Illustrator or Google Slides? Whatever makes the most sense for your team!

DUE NEXT TUESDAY

TASKS 12-13 Deliverables

Turn deliverables into Team folders on Google Drive found on Slack #0_classinfo. Label each file accordingly by task number and name. Lo-Fi prototype link will also be turned in on #project1 Slack Channel.

TASK 12 – WIREFRAMES

More Info: How to Create Wireframes + Examples

Create numerous wireframes for various screen types in your user flow. For example, this could be the main screens from your primary navigation, such as the home screen, a profile screen, browse screen, and so on… whatever is unique to your product redesign. Do at least a few variations for each of the relevant screens. Depending on your solution, your device choice may vary. You might be doing wireframes for either mobile or desktop. I would probably just pick one for your product redesign, unless you want to demonstrate their relationship. I would lean more towards focusing on mobile, unless your research made a strong argument for desktop.

Feel free to do the Crazy 8’s exercise for this task. See the Help link above for more information.

How to Turn In:

  1. Wireframe sketches for various screen types in your user flow. Sketch several variations for each screen type to explore different layout ideas. You are welcome to use the Crazy 8s method.  
  2. You can use a sketchbook or whiteboard and take a high quality photo or scan of them. OR you can create them in a tool like Figma, Figjam, Invision Freehand, OR whatever software you feel most comfortable in.

TASK 13 – LO-FI PROTOTYPE

More Info: How to Create a Lo-Fi Clickable Prototype + Examples

For this task you will be a creating a clickable interactive lo-fi prototype that will be tested by your peers during Tuesday’s class.

How to Turn In:

  1. Lo-Fi (or Mid-Fi) Prototype link posted to #project1 Slack Channel and in a Google Doc in your Google Drive.
  2. This interactive prototype is clickable and navigates through all your different screens to achieve various tasks in your product redesign.
  3. Use Figma or Adobe XD.