Third project milestone: Ideate

This deliverable asked you to consider, what are people going to do with your design, and how to use this information to refine your design direction, generate requirements for the proposed system, and begin to sketch out how it will look and function.

We will do a series of in-class activities to allow teams to do some hands-on work with the components of this milestone. This will allow you to experiment and get some feedback, and to refine your ideas to come together in the deliverable.


Deliverable #1 – Tasks, Requirements & Personas Report

The report should be 4-5 pages in length (+images, figures if appropriate), 11-12-point font, 1.5 spacing.  Submit a pdf of the report, filename: “Ideate-part1-report-<team name>.pdf”

The report should consist of the following elements:

1. Personas:

  • Identify the people who you will be designing for by creating personas. Each team must create two personas that communicate different types of users and their needs. (Normally you would create more personas, often 4-5, including an anti-persona.)
  • Each persona should be derived from your qualitative research. Your personas should represent the diversity of observed motivations, behaviours, attitudes, aptitudes, constraints, work or activity flows, environments, and frustrations around either the activity you intend to support or when using relevant current products or systems.
  • Clarify briefly how each persona came from the data. You can optionally include an appendix with further details about how your data supports the persona, if needed.

2. Tasks and Task Analysis

  • Construct a scenario to situate your tasks.
  • Describe 3 representative tasks that you are trying to support. (Remember, task descriptions should be interface independent – more than one system could be used to execute the task.)
  • For each task, identify the extent to which it is currently supported or not supported by an existing technology or non-technological means.
  • For each task, craft task goals, steps involved (motor, cognitive), and the positive and negative aspects, i.e., what is currently going right and what could go wrong?
  • Supporting sketches, images and figures may be used to support conveying and analyzing the tasks.

3. Requirements

You will not be able to design a prototype for all users or all activities, so you will need to prioritize what requirements are most important to support based on your literature review, fieldwork and personas.

  • Decide upon 3 major requirements for your system.
  • For each requirement, briefly discuss why you have prioritized it. You may find it useful to refer to your personas (and possibly other stakeholders) in your discussion.
  • There should be alignment between the tasks users need to perform with your system.


Deliverable #2 – Conceptual models and sketches

1) In-class activity: Individual preliminary conceptual model + sketch + group assessment

  • Come up with a conceptual model independently prior to class. The goal is to do this entirely on your own in order to come up with as diverse a set of conceptual models as possible.
  • Think about the following items as appropriate for your conceptual model: metaphor, concepts, relationships, mapping, terminology, interaction types, and interface types
  • Create a rough sketch of your model
  • Bring your model to class on Oct. 21.
  • Come together as a team to walk through each conceptual model + sketch and discuss their strengths and weaknesses.

2. Deliverable: Final conceptual model + storyboard Report

  • Create a final conceptual model by either refining one team member’s or a combination of the individual ones.
  • Describe the conceptual model and why you elected to go with this one as opposed to others you might have considered.
  • Identify each of the following items as appropriate for your conceptual model: metaphor, concepts, relationships, mapping, terminology, interaction types, and interface types.
  • Create a storyboard for your conceptual model. You can use whichever storyboarding technique you want. Your storyboard must be 8-12 panels.
  • Identify its strengths and weaknesses of the model (bullets are fine).
  • Place the individual conceptual models + sketches of each team member in an Appendix.
  • Length: 1- 2 pages + storyboard (no page limit) + appendix with team members’ conceptual models
  • Submit a pdf of the report, filename: “Ideate-part2-report-<team name>.pdf”