Activity Centered Design
Activity Centered Design
Activity Centered Design
INTRODUCTION
This paper examines Activity Centered Design, an activity-focused user-centered design
method. ACD is quite different from the other UCD methods like Scenario-Based design or
contextual design. ACD helps product developers use human activities as objects for their work,
“offering an activity-centric view of Human Computer Interaction” (Li & Landay, 2008). This
paper talks about the aspects of the ACD method. It takes you through the process of ACD using
an example of several activities (using a mobile phone as an example). To understand the ACD
better, this paper compares it to other UCD methods to find the similarities and differences. I
try to ask a few questions, which when answered, might define a structure for the process.
not what tasks or activities the user must perform with the application but what tasks or
activities must be enabled by the application/tool/system” Williams (2009, pg. 5).
Some authors suggest that Activity theory is not yet developed as a complete process,
that it is largely theoretical in nature. (Williams, 2009)(Gifford & Enyedy, 1999) ACD tries to
combine activity theory with other approaches like situated learning and collaborative learning.
There are others (Li & Landay, 2008) that suggest that although ACD is largely a set of
perspectives and concepts, it’s an art to apply it in practice. ACD seems to minimize the need
to do a few user-centered parts (personas for example) and looks at the fundamental activities
that are more important to the end design. Using the example of a mobile phone, we need not
know the persona of a person (whether he likes calling family or friends or peers) to design the
interface, instead the concentration is on activities like calling, texting or clicking pictures. ACD
seems to look at activities from the system perspective while most UCD methods try to look at
tasks from a user perspective. To elucidate, take the example of the mobile phone again
ACD: activity based, think about calling, texting, etc.
UCD methods: task-based think about how a user would go about doing a task like
dialing, typing or adding a phonebook entry.
We can also look at different scenarios which might help understand when using ACD
would make sense over another UCD method:
A mobile phone manufacturer wants to create software that attracts new customers;
this is when a UCD method like scenario based design would probably help identify the
most important tasks.
A mobile phone manufacturer thinks about activities that can be done using a mobile
phone, like clicking a picture, for example, you don’t really need to involve the user for
an activity like this, ACD would be appropriate in such a situation.
It is still unclear whether ACD has a fixed process or structure. Since it is a theoretical
framework, the deliverables and steps of ACD aren’t set in stone yet. A closer look at Activity
Theory helps us identify what could be the important parts/deliverables of the ACD process.
Here is a list of parts in ACD that might prove to be valuable as stages of the ACD process:
Activity Analysis
Activity analysis is the identification or description of activities that are done by the
users of a system/product. Activity analysis tries to answer:
What are the activities that can be performed Calling, sending messages, clicking pictures,
using the system? browsing the web.
How are activities performed by different users? User 1 uses predictive text input while typing
versus user 2 who types manually.
What’s the time spent on activities? How long does it take to reach the compose
message window?
How valuable is the activity to the overall Is quick dialing really important?
system? Do we need to include a pager number in the
address book?
How intensive is the activity? Will clicking an image use a lot of resources?
The various questions in the activity analysis phase can be answered by conducting field
studies and requirements gathering. A few important questions that might be answered are:
Who are the users? What are the activities? What are the objects that a user interacts with
while performing the activity? How do different objects affect the activity?
Are activities fairly stable and fixed for different types of users?
Users can be unpredictable at times; can the selection of activities address this issue?
Can we come up with a set of activities which are independent of the user performing it? An
example of this would be a Google search, the developer would much rather focus on the
relevance and importance of the search results that worry about different users and how their
personalities affect the search! An activity like Google search would be fixed for all users.
(Although what the users search for definitely varies)
CONCLUSION
Activity Centered Design is just a theoretical framework and hasn’t matured to the point that it
can be used as a full blown UCD method. ACD is very distinct and has quite a few differences
that sets it apart from other UCD methods. It might be surprising for a theory that does not
place users in the center of the design/development process to be classified as a “User-centric”
design method. If we take a step back and look at it, the main goal is to deliver usable systems.
ACD definitely cannot ignore users as a part of the process although the focus is on activities.
Activities cannot be performed without the involvement of users. There is definitely an overlap
between ACD and UCD. If done correctly, a part of UCD methods (user research) can help form
the foundation for ACD. The need for Activity Centered Design emerged because users are wide
in taste and narrow in behavior, it’s an attempt to narrow down the scope and generalize the
process, making it independent of users influence while at the same time keeping in mind the
fact that ACD is meant to create better system for users. What I have attempted to do here is to
present a set of questions that might lead to the formation of a basic structure of the ACD process
because right now ACD is just a theory!
REFERENCES
Gifford, B. R., & Enyedy, N. D. (1999). Activity Centered Design: Towards a Theoretical
Framework for CSCL. CSCL (pp. 189-196). Palo Alto: Stanford University Press.
Li, Y., & Landay, J. A. (2008). Activity-Based Prototyping of Ubicomp Applications for. CHI (pp.
1303-1312). Florence, Italy: ACM.
Nardi, B. A. (1996). Context and consciousness: activity theory and human-computer interaction.
Massachusetts: The MIT Press.