Whether designing the rooftop of a building or the rear end of a home or business appliance, sociable design considers how the design will impact everyone: not just the one, intended person standing in front, but also all the rest of society that interacts. One person uses a computer: the rest of us are at the other side of the desk or counter, peering at the ugly rear end, with wires spilling over like entrails. The residents of a building may never see its roof, but those who live in adjoining buildings may spend their entire workday peering at ugly asphalt, shafts and ventilating equipment.
Support for groups is the hallmark of sociable technology. Groups are almost always involved in activities, even when the other people are not visible. All design has a social component: support for this social component, support for groups must always be a consideration.
Sociable design is not just saying “please” and “thank you.” It is not just providing technical support. It is also providing convivial working spaces, plus the time to make use of them.
Sociable technology must support the four themes of communication, presentation, support for groups, and troubleshooting. How these are handled determines whether or not we will find interaction to be sociable. People learn social skills. Machines have to have them designed into them. Sometimes even worse than machines, however, are services, where even though we are often interacting with people, the service activities are dictated by formal rule books of procedures and processes, and the people we interact with can be as frustrated and confused as we are. This too is a design issue.
Design of both machines and services should be thought of as a social activity, one where there is much concern paid to the social nature of the interaction. All products have a social component. This is especially true of communication products, whether websites, personal digests (blog), audio and video postings mean to be shared, or mail digests, mailing lists, and text messaging on cellphones. Social networks are by definition social. But where the social impact is obvious, designers are forewarned. The interesting cases happen where the social side is not so obvious.
Waiting is an inescapable part of life, but that doesn’t mean we enjoy it. But if the lines are truly inescapable, what can be done to make them less painful? Although there is a good deal of practical knowledge, usually known within the heads of corporate managers, very little has been published about the topic. One paper provides the classic treatment: David Maister’s The Psychology of Waiting Lines (1985). Maister suggested several principles for increasing the pleasantness of waiting. Although his paper provides an excellent start, it was published in 1985 and there have been considerable advances in our knowledge since then.
In the PDF file, The Psychology of Waiting Lines, I bring the study of waiting lines up to date, following the spirit of Maister’s original publication, but with considerable revision in light of modern findings. I suggest eight design principles, starting with the “emotions dominate” and ending with the principle that “memory of an event is more important than the experience.” Examples of design solutions include double buffering, providing clear conceptual models of the events with continual feedback, providing positive memories and even why one might deliberately induce waits. These principles apply to all services, not just waiting in lines. Details will vary from situation to situation, industry to industry, but the fundamentals are, in truth, the fundamentals of sociable design for waiting lines, for products, and for service.