(ASP) Need Finding Lesson

Need Finding

In the previous lesson, you analyzed different mobile apps. Each of the apps you evaluated started out as an idea. Developers went through the concept selection process of evaluating ideas or concepts with respect to customer needs and other criteria, comparing the relative strengths and weaknesses of the concepts, and selecting one or more concepts for further investigation, testing, or development.

In order for an app to be sustainable, it needs to satisfy a need. To determine users' needs, developers go through a process called Needfinding. Needfinding is defined as the process of understanding users' needs.

There are two basic types of needs.  

Expressed: Needs that the user directly states such as "I need a way to bookmark my resources so I can find them." Latent: Needs the user doesn't know exist. These are needs that are currently filled by other tools but could be made simpler.

Principles of Needfinding

Finding latent needs can be difficult. Luckily, there are a few simple principles that make it easier.

  • Focus on the needs and not the solutions as that will limit opportunities.
    • If a room is too hot, do not say fan, but state that the room is too hot. Go to the customer's environment as it makes the need more specific.
  • Go beyond the obvious problem.
  • Collect different types of data, including notes, photos, video and audio.
    • Interviews and observations and data from objects used can all tell different stories. Make findings tangible so that they may be communicated and presented to others.
  • Iterate the process.

View the learning object below to learn the steps in the Needfinding process.

[CC BY 4.0] UNLESS OTHERWISE NOTED | IMAGES: LICENSED AND USED ACCORDING TO TERMS OF SUBSCRIPTION