As Yogi Berra said, you can observe a lot just by watching. Watching how people do things is a great way to learn their goals and values, and come up with design insight. We call this needfinding. This assignment helps you train your eyes and ears to use the world for inspiration, instead of your own thoughts and opinions. Your goal is to uncover unmet user needs, breakdowns, clever hacks, and opportunities for improvement.
Read the design brief for your studio. While you are reading through the briefs, think about anything in your daily life or in the life of your community that you can apply to that brief. Your brief will serve as a theme and yardstick for your work throughout the project sequence.
Make a list of types of people you might interview and situations you might observe to come up with design insights. Think about different types of everyday users, marginalized users, and extreme users. Also think about other stakeholders in the ecosystem. Think about the characteristics of these users.
For example, this IDEO design team was asked to redesign the grocery shopping cart. Their interviewees included not just everyday users, but also extreme users like professional shoppers and other stakeholders like store managers. Often, lead users or extreme users have come up with better solutions and creative tricks. Interviewing and observing marginalized users not only helps us create more inclusive designs, it also often highlights issues that everyone has to varying degrees.
Select three people to observe. Choose people who are not similar to yourself in some way (for example, they are studying different discipline, working a different type of job, have a different family situation). Your goal is to observe the successes, breakdowns, and latent opportunities that occur when computers are used, not used, or could be used to support your chosen activity. Ask them to participate in this assignment and get permission from them. Be sure you coordinate with your participants to select a time that will be rich for observations.
Your three individuals do not, however, need to be representative of "the general public". It is perfectly valid to limit your observations to a specific niche or user group, if desired.
Tell the participants to perform the task as realistically as possible, while communicating to you as appropriate. Utilize the strategies we talked about in lecture to help you. Take detailed notes and use digital photographs or sketches to document activities, but do not use a video camera. Try to understand why people are doing things the way they are by asking questions like, "Are there existing solutions that people aren't using? If so, why?"
Remember, your photos or sketches are meant to highlight specific breakdowns or design opportunities (what people "usually" do doesn't count). A breakdown is when a user tries to do something and fails or does not know what to do. Breakdowns include slips, which are accidental; mistakes, where users have the wrong mental model; awkward or long interactions that just take too many steps. To effectively do this, caption each photo to explain what is being observed and describe the breakdown or design opportunity. Keep in mind that your TA will be evaluating you on these photos and captions; ask yourself if they will be able to understand what is going on without having observed with you. Note: Using stock photos/art is plagiarism and is unacceptable.
After each observation, ask the participant questions about what you observed. It should take you approximately two hours total to make all three observations if you have planned carefully. It will take longer if you haven’t!
Use your observations and findings to brainstorm a list specific user needs: opportunities for design innovation that would enable computers to better support the activity you observed. Think back to when you asked yourself, "When, where, how, or why can’t someone use what is out there already for this activity?" What does this tell you about the unmet needs that they have? Come up with as many user needs as you can that are based off your observations--feel free to brainstorm with anyone around you to generate as many interesting ideas as possible.
After you've generated a large brainstorm list, narrow down your unmet user needs to at least 15 most insightful ones. We strongly encourage you to submit more than 15, in case some of them are not really needs. Each idea should be able to become the basis for a design project.
Your list should be articulated as user needs. You are not looking for solutions yet: focus on user needs and goals only. An example of a need might be "Sometimes, when Scott takes the Caltrain home, there is no room for his bike and he has to wait for the next one. Scott needs a way to plan what train to take based on how much room is available in the bike car". On the other hand, the user need: "Amazon users need a way to check if their order has shipped properly" is not a good user need, because it focuses on a specific solution rather than a problem. Good user needs can be fulfilled by multiple solutions.
It is helpful to use the phrases "needs a way to" or "needs to be able to" as you list your user needs.
|Too vague||Just right||Too specific|
|Citizens need a way to access the news||Citizens need a way to stay up to date with current country affairs because they have to be informed during elections season||Citizens need a mobile web app that provides the latest news about the elections|
|Students need more information about courses||Students need the ability to achieve a course load that fits their goals||Students need information on how much time COGS 120 will require on week 10|
Based off the unmet user needs you found, write a point of view that describes a core problem in relation to a design theme. It should address a deep user need and take on a high-level design strategy without offering any concrete solutions. A bad POV is often too long or too vague: "Ease of accessibility will accomplish the task at hand." This POV is too vague and does not present a core problem.
Point of views stimulate creativity by focusing your design work. Solutions should immediately come to mind when you hear them. Imagine them as your overall vision of your app, or your mission statement. In some cases, you may need to contextualize your POV, but the best ones are less than 10 words. A POV summarizes how you think about the problem, not how you will solve it. Write yours in 10 to 20 words.If your task was to redesign the experience of waiting in line, examples of POV are:
Prepare a 1-minute talk about your needfinding approaches and results to be presented in studio. What activity did you choose to examine? How did you examine it, with what methods? What major insights or breakdowns did you discover? What promising unmet needs were identified as a result? Do not print out your sketches or pictures, just use words so as not to consume time explaining a complicated scene or sketch.
by Mike Davison, Community TA and UX Project Manager
Needfinding is probably the most important part of any UX Designer's arsenal. Without it, your design team could spend months designing a solution that completely misses the point. You will be surprised at how much you can learn, especially when you vary the audience.
Take the smartphone In all likelihood, you will have seen an elderly person press the screen harder and more slowly when it does not respond as they had expected. Needfinding research has suggested that this relates to 50s, 60s and 70s technology - the technology this age group are familiar with...this technology often does yield a different result if you press harder.
Why is this useful? Well perhaps we could develop interfaces that took into account the pressure the user applies, and not just where they apply it? How could we make the interface itself easier for the elderly user? Needfinding is a very powerful way to generate ideas.
Examples are a great way to learn, but they are not a gold standard for this class, especially as it evolves over the years. Use these examples as a reference, see where they succeeed/breakdown, and make sure your final submissions adhere to the rubric items.
Submit a single formatted pdf file with the following items concatenated within it (see the Student Examples section for how to format each item):
Submitted in studio, you are responsible for giving a prepared 1 minute summary of your findings.. Submit your formatted pdf here
Students earn one point for each binary criterion met.
Yes, your assignments for the rest of the quarter have to relate to your studio theme. Two reasons for this: designing for a brief is how the real world works, and you will benefit much more in your studio when multiple teams work on related projects.
Yes. Each person will need to submit their own assignment, on an activity related to their studio theme.
Submit at least 15 needs (more is fine) selected from your brainstorm. This list of unmet needs is based on the three user interviews you conduct.
Finding and interviewing people in this way can be daunting at first, but it is necessary in avoiding assumptions and in getting data about real people that exist in the world. As such, learning to recruit users to interview is a key goal of this assignment, as it will be important in the real world and research. You are free to come up with whichever methods or incentives for recruiting, but we suggest that you reach out to your friend group or other students in your studio to participate in your interviews.
In general, you should be observing three people performing the same activity. This can sometimes vary, depending on if your three participants are performing three different but thematically related activities.
See the example assignments to give you an idea of the appropriate scope of the activity.