top of page

Wireframe Critiques

Monday, November 5, 2018
3:30 PM to 5:00 PM
Cumnock 102 & 103 ← Note building change!

​Guest reviewers: Richard Banfield, CEO of Fresh Tilled Soil, Amanda Yee, Sr. Product Designer at Drift & Joe Ringenberg , Director of Design at Wistia

You will report directly to your team's room assignment listed here.

We do not have a lab on Nov 7 due to CPD.

Required Reading

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

  2. 23 Questions for Early UI Design

Further Reading for PRD Design Principle work:

Minor Deliverable: By 5pm Friday, Nov 9, please post further lo-fi test proofs and learnings in the “Nov 9 - LF3” tab.

Session Assignment:

Be prepared to present your wireframes as a team in front of the classroom on Nov 5 for about 7 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 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,, Balsamiq, 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.

bottom of page