I attended the Information Architecture Summit in Phoenix, Arizona, back in April 2010. The IA Summit is the premier gathering place for information architects and other UX professionals. This was the 11th IA Summit, and it included Dan Roam and Richard Saul Wurman as Keynote speakers. Whitney Hess was the closing plenary speaker.
This presentation introduced me to the AOF method of prioritizing features for social web applications. Joshua Porter's book, Designing for the Social Web, goes into more detail about the AOF method; however, here are the basics:
- Define the Activity
- Identify your Social Objects
- Choose your Features
Define the Activity
"Goals are the end condition that people are striving for. Activities are the set of tasks people do to achieve their goals."
The table below demonstrates the differences between goals, activities, and tasks:
| Web Application | Goals | Activities | Tasks |
| ProjectSpaces | Completing work effectively and on time | Managing a project | Share documents, assign tasks, send announcements, hold discussions |
| Washington Post's Subscriber Services | Save time/money | Managing newspaper subscription | Pay bill, schedule a stop in service for vacation, report a problem with delivery |
As designers, we often ask ourselves, "What do people want to accomplish on this site?" Christina offers these questions that help you better define the activities that people will do on your site:
- What do people have to do to make you [the organization] successful?
- What are you [the organization] making people better at?
- What are your users passionate about?
And borrowing from Chip & Dan Heath's Made to Stick, Christina suggested that we consider the commander's intent:
"If we do nothing else, we must..." or "the single most important thing we must do is..."
By answering these questions you set the stage for developing a successful, focused application.
Identify Your Social Objects
Interestingly enough, many of our online activities revolve around objects. Christina reminded us that social objects can be ideas, people, or physical objects. She explained that they influence social interaction and can change the way people interact with each other. Here is a list of successful web applications that are built around social objects:
| Web site | Social Object |
| ProjectSpaces | project documents |
| Flickr | photos |
| YouTube | videos |
| Slideshare | presentations |
In each of the above examples, all of the social features that connect people are around a type of social object. For example, on YouTube, people are connected by commenting on videos. During the IA Summit workshop, Christina shared this quote from Jyri Engestrom to stress the importance of focusing on the object that connects us together.
The term "social-networking" makes little sense if we leave out the objects that mediate the ties between people. Think about the object as the reason why people affiliate with each specific other rather than just anyone.
The point in all of this is that people gather around the social object, the content of your site, and through these objects, they interact with each other. A major part in social design is identifying these social objects and planning an environment that will support interactions around them.
Choosing Your Features
Now that you've defined the activities and social objects, you can start choosing features for your web site. The features you choose to include, or not to include, on your web site ultimately determine what activities your users can perform on the site. The first step in this process is listing out all of the objects (nouns) and then creating a list of actions (verbs) that users can take on those objects. Some of the common social objects that I work with on a typical project include:
| Object | Actions |
| Document | upload, organize, edit, share, comment, link to, email, download, |
| Discussion | ask a question, reply, delete |
| Blog Posts | create, read, share, comment, link to, annotate |
| Feature | Value to user | Value to business | Technical complexity | Total Score |
| Create blog post | 5 | 5 | 5 | 15 |
| Share a blog post by email | 4 | 5 | 4 | 13 |
| Share a blog post by twitter | 4 | 5 | 4 | 13 |
| Comment on blog post | 5 | 5 | 5 | 15 |
| Annotate blog post | 3 | 3 | 2 | 8 |
In this fictional example, we would probably choose to include the ability to create, share, and comment on the blog post. However, we would not include the ability to annotate the post because it is of little value and it has a high technical complexity.
Summary
Forum One News
Brian grew up on land that used to be part of his grandfather's dairy farm and spent hours exploring the outdoors. That kind of roaming and curiosity is a great foundation for an information...





Comments
Usability, design, and everything else.
Thanks for sharing. This is pretty simple information I guess, but we don't often sit down and take the time to work out how to apply it to our own ideas and businesses.
We have recently launched a usability testing website at http://intuitionhq.com - my task now is to consider how to use these strategies in terms of our site, and what are the important issues that we need to address to ensure the site is of value to both us and our users. Now I have a place to start though!
Thanks for sharing.
Good Kick-Off Meetings
Jamie,
I am glad you found value in the post.
I heard Kevin Hoffman speak at the IA Summit about kick-off meetings. I am looking forward to going through his kick-off meeting web site: http://goodkickoffmeetings.com/
Great post Brian. During our
Great post Brian.
During our kick-off meeting with Happy Cog, we went through a similar prioritization exercise but it had a twist. After adding the ratings for each feature (I think on a similar scale of 1-5), the total could not exceed the 3x the number of features presented. It was a nice way to prevent staff from saying everything was a priority.
Slideshare presentation with more about AOF
Post new comment