social construction of technology

I just posted an entry about gender, technology and social construction at misbehaving.net, a great little blog that i’m playing at these days.


I have a tendency to point out when interfaces have gender biases in them. Lately, i keep getting asked what it would mean to create a separate interface for women. This question astonishes me, and i keep chewing on how to properly respond.

There are a lot of things that men and women do differently. For example, men are much better at spatial rotation, but their skills at differentiating shades are atrocious. Yet, there are certain tasks in the real world that men are better suited for and certain tasks that women are better suited for. The real world doesn’t have a gendered interface; it simply allows for different readings, different levels of access. For example, we all manage to negotiate three dimensions, but the cues we use to do so differ.

Technology is socially constructed. In other words, technology does not exist devoid of its creators’ prejudices, biases, cultural assumptions, etc. When men design and build toys and then have other men test them, it should not be surprising that the common experiences of those men get imbibed in the technology. (If this seems surprising, imagine what happens when you assume American roads, habits when designing a car for Amsterdam or Japan. Cultural dependence is not that different.)

The trick is not to design a separate interface (remember, separate but equal never really worked). The goal is to incorporate a wide variety of perspectives into the design and creation of a system, to create a system that people can repurpose to meet their needs. The goal is to encourage flexibility of expression, to not project a limited perspective into the technology. Designers must take into consideration the vast array of potential users, experiences, expectations, not simply their own. This is why things get tricky.

Print Friendly, PDF & Email

4 thoughts on “social construction of technology

  1. Izel

    Your average idiot has enough trouble getting used to a standard interface. Do you really want to confuse him / her with the concept of customizable interfaces?

  2. zephoria

    I’m not arguing for customizable interfaces. I’m arguing for interfaces that allow for people to repurpose them as they see fit, to engage in a wide variety of social proactices in. Think in terms of the real world. What does one do in a public park? It’s architected to allow for a variety of behavior, which is a socially good thing. People have a hard time learning interfaces because interfaces are not based on the structures that they normally grapple with; they are based on computer programmers’ ideas of functionality.

  3. Adam

    A random signature on slashdot:
    The only intuitive interface is the nipple, after that it’s all learned.

    Designers should pour more study into the nipple.

  4. Izel

    Software interfaces are intended to bridge the gap between human intent and computer functionality. You can’t use an interface in the same way that you can use a park. Every feature of the interface, and every feature of the program to be accessed by that interface, has to be hard-coded into the program by a programmer. You cannot use features inside a program that the programmers did not explicitly put in there, unless you’re talking about implementing some kind of extensible plugin architecture or scripting engine or what have you.

Comments are closed.