There’s one comment in particular I’d like to respond to, because it poses a good question about the nature of functionality with respect to design. In the comment, Mark Tuttle argues that the functions offered by a system outweigh design, citing examples of time sharing systems, email, Unix, bitmapped interfaces, MEDLINE, and query languages for early relational databases.
To a large extent, I do agree about the point about the importance of functionality. If we had a system that could predict tomorrow’s stock market prices but was completely unusable, I’m sure we’d still see a lot of people making the effort to learn how to use it.
However, functionality and design aren’t separate things. A large part of design includes understanding what needs people have and what technologies can be applied to solve those needs. Design also isn’t just about the user interface “skin” of graphics, icons, and aesthetics that people see. It also includes the internal “skeleton” of how the application is organized, the conceptual model and metaphors conveyed to end-users, as well as its functionality.
It’s also worth pointing out that in many of the above examples about functionality, the systems were designed by and used by people with intimate knowledge of software. The designers already had a deep understanding of what the problems at hand were and how people did their work. In other words, the designers *were* the users. That’s not really the case anymore, though. Information and communication technologies are pervasive in all aspects of modern society, from finance to manufacturing, from health care to consumer products. We can’t rely solely on our intuitions anymore because the users are no longer like us.
Second, while functionality is a key differentiator for technologies in the very early stages of adoption, it isn’t as strong a draw in the middle and late stages, especially when competitors have arrived that offer products with comparable functionality.
A lot of researchers have developed models of technology adoption. My favorite one is presented by Everett Rogers in the well-known book Diffusion of Innovations, which summarizes the literature in that area. Rogers outlines five major factors that influence whether or not people adopt a given innovation. Note that in Rogers’ book, an innovation can be not only a technology, but also a process or a habit. Here, I will focus only on technologies.
The five factors Rogers identifies are: relative advantage, compatibility (with one’s beliefs and existing installed base), complexity, trialability (how easy it is to try the technology), and observability (how easy it is to see others benefit from the technology). Rogers also presents the well-known technology adoption curve that segments the population based on when they adopt an innovation, labeling people as innovators, early adopters, early majority, late majority, and laggards.
At this point, you can probably see where I’m going. Innovators and early adopters have a higher tolerance for risk and complexity, and often have significant pains that need to be addressed *now*. In these cases, functionality dominates factors like aesthetics, usability, simplicity, and cost. If you’ve ever seen (or worse, had to use) anything created for the Department of Defense, you’ll probably agree it fits this description quite well.
However, the early majority, late majority, and laggards have very different profiles and thresholds for complexity and value. In these cases, the ability to create a product that fits into people’s lives plays a significant role, especially when competing products are available. This is where great design matters a lot, as demonstrated by products like the Nintendo Wii and the iPod. When the Wii first came to market, it was competing against the large and well-established base of XBox and Playstation consoles, and succeeded by dramatically simplifying game play and targeting casual gamers rather than hard-core gamers. The iPod came out a few years after the first mp3 players were already being sold, and made huge inroads by forging a strong emotional connection to people with its sleek form factor and fun user interface.
At its core, interaction design is about understanding at a deep and visceral level the needs, desires, values, and processes of people, and then applying those insights in the creation of technology. It’s about empathy, seeing and experiencing the world from the users’ point of view. And it’s about always remembering the mantra: the user is not like me.