Product Management

Monday, November 4, 2019
3:30 PM to 5:30 PM <--FULL TWO HOURS
 

Guest reviewers:

• Jeremy Kriegel, UX Lead at the Broad Institute of MIT & Harvard

• Christina Raymond, Director of Product Design PatientPing

• Jocelyn Perron, Director of User Experience and Design at Wistia

• Scott Mackie, Head of Product Design at Indigo Ag

​

You will report directly to your room assignment.

​

We do not have an official lab on Nov 6, but the room is available if you want to use it for teamwork

​

Required Reading

1. Nine Rules for Running a Productive Design Critique - Jake Knapp

2. 23 Questions for Early UI Design - compiled by Eisenmann

​

 Further Reading for PRD Design Principle work:

1. Designing for iOS and Android Design Principles 

2. Julie Zhuo at Facebook, who has worked as a software engineer, UX designer, and product manager, has written a three-part series on what each role should know about the others' priorities and how they can work together productively. These posts will be of special interest to students who plan to work in tech companies big enough to hire designers.

• How to Work with PMs: A Cheat Sheet for Designers 

• How to Work with Designers: A Cheat Sheet for Engineers and PMs (see also Don't Say This to a Designer by Juhi Chitra)

• How to Work with Engineers: A Cheat Sheet for Designers 

​

Minor Deliverable: By 5pm Friday, Nov 8, please post further lo-fi test proofs and learnings in the “Nov 8 - LF2” tab. Your second round of tests should be solution oriented (unless you’re coming off a recent pivot!)

​

Session Assignment:

Be prepared to present your wireframes as a team in front of the classroom on Nov 4 for about 7 minutes, with an additional 7 minutes for feedback.

• Start your presentation with a 60-second intro of what your app will do -- who your target users will be and what problem you will solve for them.

• Be prepared to present the wireframe for one key path scenario you are most interested in getting feedback on for your application (see bullet below for definition). Use wireframes or mocks -- hand drawn, Proto.io, Figma, etc. - either printed for the doccam, pics on g-slides or interactive wireframes you’ll drive from the classroom PC.

• According to Alan Cooper, About Face, p. 133, "A key path scenario describes how the persona interacts with the product. using the vocabulary of the interaction framework. These scenarios depict the primary pathways through the interface that the persona takes with the greatest frequency." Examples from Venmo might be sending someone money OR requesting money from someone. Do not spend time on onboarding, logging in, etc. Assume those steps have already happened (if applicable).

• As backup, bring any additional wireframes/mocks/sketches/storyboards, etc. that you might wish to use to respond to questions/comments.

• Our guests will provide verbal feedback. All students in each classroom will be expected to provide written critiques to their classmates as part of their participation grade.

• These sessions will be recorded.