Home

A7. Ethnography (Grp)

Fri, 08/19/2011 - 12:06pm — monica
Group/Individual Assignment: 
Group Assignment
Assigned: 
Mon, 10/03/2011
Due: 
Mon, 10/17/2011 - 11:59pm

You obviously can't do anything resembling classical ethnography to understand your design context and community in two weeks, and you probably can't even much "rapid" ethnography. But a little ethnography is better than none, so we're going to do some.


PART 1. First, consider where your project falls on the "ethnography continuum" and decide if it is more "experience-intensive" or "information-intensive." Divide your project team into two groups so that the number of people in each group and thus the amount of ethnographic observation and analysis reflects where your project falls on the continuum. For example, if there are three people in your team and you have an "information-intensive" project context, you'll have one person taking an "experiential" perspective and the other two taking an "information-intensive" one. If you have four team members, split two and two.

PART 2a. The "experiential" team member(s) should first develop an "Engagement Plan" that briefly explains what they would ideally like to do. This has four parts:
  • Define the scope
  • Identify the informants
  • Plan the observations and data collection
  • Analyze and interpret

This plan doesn't have to be extensive - it is only to ensure that you think ahead so that you maximize the return on your limited time. Ensure that the plan is constructed using information learned in the Service Brainstorm. NOTE: You probably won't be able to do everything in your plan, but it is a useful exercise to imagine a 'rapid' engagement even if you're limited to a 'very rapid' one.

For example, a project team trying to understand the bookstore setting might plan as follows:

  • Define the Scope: We'll visit two different bookstores, a large chain store (Barnes and Nobel) and a small independent one (City Lights)
  • Identify the Informants: Bookstore customers of different ages and gender (at least 10 in each store), bookstore clerk (at least 2 in big store), bookstore manager
  • Plan the Observations and Data Collection: We'll pretend we are customers and watch people, focusing on their interactions with the books, other customers, and bookstore employees; After customers leave the store, we'll try to intercept them to ask them a few questions about their experiences. (Probably should talk to the clerk or manager first so they dont think we are stalkers). We'll visit each store at least three times, once in the middle of day mid-week, once in the evening, and once on a weekend.
  • Analyze and Interpret: How long do people spend in the bookstore? Do they always buy something? How many books? Do they talk to other customers? Do they talk to bookstore employees? etc.

PART 2b. Similarly, the "information-intensive" team member(s) should first develop an Engagement Plan to guide their work. There will be some similarity to the plan for the "experiential" ethnography.

For example, a project team trying to understand the ISchool office might plan as follows:

  • Define the Scope: We'll visit the ISchool office to understand the primary information-intensive processes that involve ISchool students.
  • Identify the Informants: We'll interview the "Front desk" person, the Office Manager, the Accountant, and one of the assistants. Ask the Office Manager first to get permission and "legitimated access" to the other employees in the office. We'll also interview some of the students who go to the I School office to have encounters with the employees.
  • Plan the Observations and Data Collection: We'll interview each informant to identify the essential documents/artifacts and information flows, trying to find the "headwaters" of each and the processes/transformations that they undergo during their life cycles. We'll collect examples of each as well as an information about their models. We'll interview each informant twice, at least a few days apart, so that we can ask followup questions suggested by what they told us the first time.
  • Analyze and Interpret: What are the essential documents? Can we develop a causal model of information flow? Can we determine how the information components of each document type are incrementally and collectively transformed? 

PART 3a. The "experiential" team should summarize its key findings of the user interviews, observations or surveys. Identify all items that you think belong in your project's traceability - either as completely new findings or new information that can be traced back to traces from your Service Brainstorm.


PART 3b. The "information-intensive" team should summarize its key findings by creating a diagram that depicts the lifecycle or information flows of the most essential documents or information artifacts. Use the example diagrams at the end of Lecture 11 as an example if they are appropriate for your project, but feel free to invent an alternative type of diagram if you can devise a better representation. Identify all items that you think belong in your project's traceability - either as completely new findings or new information that can be traced back to traces from your Service Brainstorm.

PART 4. The entire team should discuss the work of each sub-team and refine the project concept, being explicit about "traceability" of the changes. 

NEW! Submit your updated Traceability document as an attachment to your assignment.

Resource(s): 
Traceability How-To