Illustration:

Share This:

Job Board

Published in 1977, Christopher Alexander’s A Pattern Language: Towns, Buildings, Construction, contains the collective wisdom of world cultures on centuries of building human housing. It had a resounding effect not only on architecture and urban planning, but also on software design. In it, Alexander and his co-authors explored 253 architectural design patterns. For example:

203. Child Caves

Conflict: Children love to be in tiny, cave-like places.

Resolution: Wherever children play, around the house, in the neighborhood, in schools, make small “caves” for them. Tuck these caves away in natural leftover spaces, under stairs, under kitchen counters. Keep the ceiling heights low—2 feet 6 inches to 4 feet—and the entrance tiny.

Every pattern explores ways of designing space to meet human needs and promote happiness. It doesn’t take great imagination to apply these architectural principles to information architecture—taking them out of the real world and into the digital world.

Humans can behave in surprising ways when you bring them together. In an information space, a human’s needs are simple and his behavior straightforward. Find. Read. Save. But once you get a bunch of humans together, communicating and collaborating, you can observe both the madness and the wisdom of crowds. Digg, an online news service in which the top stories are selected by reader votes, is as likely to select an insightful political commentary as it is an illegal crack for a piece of software as their top story. This unpredictability makes architecting social spaces the most challenging work a designer can take on.

While your designs can never control people, they can encourage good behavior and discourage bad behavior. The psychologist Kurt Lewin developed an equation that explains why people do the crazy things they do. Lewin asserts that behavior is a function of a person and his environment: B=f(P,E). You can’t change a person’s nature, but you can design the environment he moves around in. Let’s explore some of Alexander’s patterns I’ve observed in my work and the design work of my fellow practitioners.

Indentity

Conflict: Who can you trust online?

Resolution: Give each user an identity, and then allow him to customize it as he sees fit. The identity allows the user to express his personality, and is typically accessed and protected via a unique log-in. Participation is rewarded by enhanced reputation and the ability to collect items in the system (bookmarks, history, relationships, and so on).

If you were going to build a piece of social software to support large and long-lived groups, what would you design for? The first thing you would design for is handles the user can invest in.

Elements of identity

To allow your user to successfully create an identity, you need to provide ways for users to reveal themselves online. Four elements of online identity are:

Profile

A profile is a collection of information about the user, typically including a short biography and contextually appropriate facts. Orkut, Google’s foray into social networks, collects and displays gender and marital state prominently. LinkedIn, a business networking site, doesn’t touch any of these bits of information, focusing instead on job history, skill set, and education.

Orkut user profile.

LinkedIn user profile.

Presence

One thing any inviting and vibrant community needs is a sense of life. Presence is a way for a user to express themself and populate the online space. Presence can be a status, history of activity, or location.

Reputation

On a website, your reputation is equal to the sum of all your past actions on the site, good or bad, where the community defines “good” and “bad.” Since human memory is fallible, and of course, new members or visitors don’t always know the history, reputation systems are built into web software to track behavior and how the community judges it. Amazon’s “Top 500 Reviewer” or eBay’s “Top Seller” designations are great examples of reputation systems.

Relationships

Conflict: On a web site with thousands or millions of people, how do you make sure you can keep track of the people you care about?

Resolution: Create ways for people to identify, connect, and organize the people they care about, as well as the information those people produce. The complexity of relationship classification depends on how your customers will use your web site.

Relationships are always present in communities. Online, site software manifests and categorizes relationships according to the community’s needs. It can be simple, such as Twitter’s flat following mode. Twitter is based on the concept that people broadcast to others and subscribe to others’ broadcasts as they would to a magazine. The Twitter system design doesn’t recognize that mutual following might be a proxy for friendship. The entirety of the relationship is, “I’m interested.”

Following on Twitter.

Offering more choices to define the nature of relationships allows the user greater control, but introduces complexity. Flickr offers categories for “friends,” “family,” and “contacts,” which the user applies as they see fit—including marking as friends people who are really family and as family those who are really friends.

When your Flickr contacts grow to 100, “friends” becomes a useful tool to watch some people a little more closely, because your friends appear in the center of your homepage. Additionally, you set viewing permissions based on these distinctions. For example, a college student might show his most intimate photos only to a list of close friends labeled family. He may label actual family members as friends or contacts. Each label has a built-in set of assumptions that may or may not apply to the user’s needs. But having clarity on who sees what, no matter their label, is useful.

Flickr friends and family.

Elements of relationships

Relationships on the web are just as important as relationships in real life. Three key elements of relationships are:

Contacts

Give your users a way to classify the humans in their life. It can be as simple as just saying, “I know him,” or “I don’t know him,” or as complex as saying, “We were college roommates, but we haven’t spoken in ten years.”

Groups

Groups are another relationship structure, based on shared interests or experiences rather than personal connection. They include alumni groups, work groups, and professional organizations.

Norms

While walking into a biker bar wearing a Yamaha tee shirt might get you killed, wandering into a Star Wars forum and saying, “George Lucas ripped off Joseph Campbell, and he didn’t even do it well!” will generate 500 flames an hour. We call those who violate norms “trolls,” and it’s best to prepare for them. Create rules for behavior and consequences for violating the rules such as a time-out or a ban.

Activity

Conflict: If there’s nothing to do on a site, then it doesn’t matter if all your friends are there or not. The site has no more interest than an address book, and it won’t get affection or traffic.

Resolution: Create activities that are useful to individuals but are much improved by group participation.

The third major pattern in social software is community activity. This is just like being a party planner: you’ve brought people together, now what? Happily, humans have things they like to do together, and if you get them in the same spot and give them even rudimentary tools, they’ll start talking, sharing, and collaborating.

Shared goals on 43 things.

Elements of activity

The more things your users can do on your site, the more time and energy they’ll spend there. Some elements of activity are:

Sharing

Gift giving is a primitive human behavior—it binds us. When one person gives something to another, there’s gratitude, and a desire to reciprocate. In online community settings, where the nature of the medium ensures you retain a copy of any files you give to someone else, gift giving becomes sharing. Sharing gathers people of like interests, and allows for an exchange of ideas. As the community tightens, sharing permits exchanging dreams, hopes, secrets, and fears.

Conversations

Conversations and communication—that’s the heart and soul of a community. No matter how much software we build, people build the relationships, and they build them out of words first. If you don’t have a place for people to put their words, community devolves into viewership.

Collaborating

Social software was envisioned as a tool to allow work groups to collaborate. While the “social” part may have swept the web, there are still plenty of tools that focus on allowing smaller groups to get things done.

Architecture for Humans

Humans are complex, and the web is dynamic. Many more innovations and patterns of excellence will be defined. Yet human contact and interaction is not new. From A Pattern Language:

36. Degrees of publicness

Conflict: People are different, and the way they want to place their houses in a neighbourhood is one of the most basic kinds of difference.

Resolution: Make a clear distinction between three kinds of homes: those on quiet backwaters, those on busy streets, and those that are more or less in-between. Make sure that those on quiet backwaters are on twisting paths, and that these houses are themselves physically secluded; make sure that the more public houses are on busy streets with many people passing by all day long and that the houses themselves are exposed to the passers-by. The in-between houses may then be located on the paths halfway between the other two. Give every neighborhood about an equal number of these three kinds of homes.

Also in Issue № 279

This pattern decribes the design of a town, but can be applied to social network design. Facebook was initially lambasted over what has become its most popular feature: the news feed. The news feed is the equivalent of the town square where you can see what’s going on with everybody and chat about it. Some people want to live on the town square, so they don’t miss a thing. Others like to live at the edges of town, away from prying eyes and overwhelming updates. Social architecture’s ongoing challenge is to find intelligent and subtle ways of allowing people to choose degrees of publicness (including shelter from other people’s publicness).

If we remember the social in social architecture, we can continue to make new products that delight people as well as change their lives.

About the Author

Christina Wodtke teaches dreamers how to make change happen. She speaks everywhere from conferences to universities to boardrooms and opines across the internet, but is found most often on Eleganthack.com or Boxes and Arrows. She’s rumored to be writing a book, but procrastinates on twitter under the name cwodtke.

More from this Author

23 Reader Comments

More from ALA

Columns

The number of predictions that algorithms can make about us from even minimal data is shocking. Although we’re offered privacy settings that let us control who of our friends sees what, all our information and behavior tends to be fair game for behind-the-scenes tracking. We simply don’t know everything that’s being done with our data currently, and what companies might be able—and willing—to do with it in the future. Laura Kalbag believes it’s time to locate the exits.

Displays that are more tiny than our lowest-size breakpoints require a more condensed range of type sizes. If you don't already have in place a typographic system that can absorb the demands of this new context (watches, wearables, digital sticky notes, whatever), now might be the time to consider it. Matt Griffin was ready for anything because his site was simple and built to be future friendly.

March 19, 2015

From the Blog

It's all about us this week at ALA. From steps to sleep to social activities, we're counting every kind of personal data you can think of. But what's all that data add up to? How could we look at it—and ourselves—differently? In this week's On Our Radar, we ask ourselves—and our self—the tough questions.

That old monitor you've got lying around? Time to put it to work. Susan Robertson reminds us of how important it is to test our designs on older screens and ensure the things we build work well for everyone.

The future is here, for better or for worse—and this week, the ALA staff has been thinking about what that means: for our code (the impending arrival of HTTP/2), our content (publishing on Medium), and the cost of constant noise.

This week, the ALA staff is thinking about color accessibility, the process of building a vocabulary, the current state of web typography, and the lessons we can learn from skater culture. In other words: it's all about inclusion.