Skip to Navigation

How to Prioritize Features on Social Web Sites

Printer-friendly version

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. 

During the conference, I attended Christina Wodtke and Jennifer Ruffner's pre-conference workshop: Social Architecture: From Strategy to Success Metrics. While this workshop covered a great deal of information about designing social spaces, one of the big takeaways is that your goal is to design a place to allow people to interact. Forget about controlling the interactions or resulting content. Instead, focus your efforts on designing an environment that supports the activities that will occur within that space.
 

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:

  1. Define the Activity
  2. Identify your Social Objects
  3. Choose your Features

Define the Activity

When developing a social web application, you should consider the goals of the application, the activities the application will support, and what tasks the user will complete to accomplish a goal or perform an activity. Joshua Porter succinctly defines the difference between goals, activities, and tasks as:

"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:

  1. What do people have to do to make you [the organization] successful?
  2. What are you [the organization] making people better at?
  3. 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

 

What is somewhat striking is that many of the actions translate directly into features. Once you've created this list of actions, your team will have to prioritize them. There is a natural tendency to want to include as many features as possible; however, each feature included means more complexity. This means that it may be more complex to develop, more complex to use, and may cost your organization more time and money supporting the application as the site grows.
 
There are a number of ways of prioritizing features. One method that I really enjoy is listing each feature and the value it brings to the user, the value it brings to the business, and the general complexity it will take to implement that feature. For each feature, you assign a value of 1 - 5, where 5 is the high number for both value to the user and value to the business. You invert this for technical complexity, so features with a score of 5 are easy to implement. Those features with a total score near 15 should be consider for inclusion, because they bring great value to the user and business--they are also very easy to implement. Features that are near 0 should not be included because they are hard to do and bring little value to the user or organization.
 
The table below is an example of how you may prioritize features for the blogging area of your web site.

 

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

Only a small portion of the workshop focused on the AOF method. Joshua Porter goes into more detail in Chapter 2 of Designing for The Social Web.  The social architecture workshop at the IA Summit has a lot of fantastic content and I am sure I will be writing subsequent posts on some of the other areas that Jennifer and Christina covered. It is a gold mine of inspiration. I've included a link to the full presentation below.  

 

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

Brian Verhoeven's picture

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

Brian Verhoeven's picture
Just stumbled upon this presentation by Joshua Porter that has more detail about the AOF method. See slides 18 - 30 for particulars.

Post new comment

The content of this field is kept private and will not be shown publicly.
  • Allowed HTML tags: <em> <strong> <cite> <code> <ul> <ol> <li> <dl> <dt> <dd>
  • Lines and paragraphs break automatically.

More information about formatting options

Mollom CAPTCHA (play audio CAPTCHA)
Type the characters you see in the picture above; if you can't read them, submit the form and a new image will be generated. Not case sensitive.