Latent requirements

November 24, 2015

When we design innovative solutions we often have to deal with two types of end-user requirements:

Obvious (explicit) requirements: clearly articulated improvements, amendments or extensions. For example, a faster horse, a cheaper car, more memory, more screens, louder speakers, and so on.

Latent requirements: unmet needs that people find difficult to express, write down or articulate.

Most people, when invited to contribute to the “innovation” of a product or service, end up simply describing an evolution of something familiar – their contribution to the process is limited by what they know. A conversation about the “possible” is difficult enough; and a structured conversation about the “impossible” is, well, nearly impossible. Researchers, designers and other “proxies” intervene to develop an understanding of what people really need. It is this understanding that drives innovation; not the users themselves.

http://blog.tobiasandtobias.com/2014/04/is-it-time-to-put-henrys-horses-out-to-grass/

Advertisements

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s