top of page

Wireframe Critiques

I'm a paragraph. Click here to add your own text and edit me. It's easy.


Monday, November 6, 2017
3:30 PM to 5:30 PM
Hawes 203 & Hawes 201

Guest reviewers: Brian Kalma & Jeremy Kriegel 


We will all meet in Hawes 203 for quick instructions and then half the class will move to Hawes 201

Required Reading

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

  2. 23 Questions for Early UI Design 

  3. You may also wish to re-read Notes on UX Design, assigned for our Sep. 25 session


Recommended 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.



  1. Working as a team, continue to develop wireframes for your app. Consult the required reading 23 Questions for Early UI Design to fine-tune your work. Upload a link to your digital wireframes OR a Google doc with pics of lo-fi mocks to the Assignment Master in the Nov 5 - Wireframes tab by 5PM on Sunday, November 5. 

  2. Be prepared to present your wireframes as a team in front of the classroom on Nov 6 for about 10 minutes, with an additional 3-5 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 two different key path scenarios for your application (see bullet below for definition), spending no more than about three minutes walking through each scenario to allow plenty of time for feedback. Use wireframes or mocks -- hand drawn, Balsamiq, etc. - ideally printed for the doc cam, unless you've created interactive wireframes/mocks and wish to demonstrate them. Start with the scenario for which you are most eager to get feedback in case you run out of time to present both scenarios.

  • 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 and 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.

bottom of page