Posts tagged “user experience”

Portigal Consulting year in review, 2009

It’s been a busy year and as we head into the home stretch, looking forward to 2010 (supposedly the year we make contact), we wanted to take a look back at the past 12 months and call out some of the highlights.

Previously: Our 2008 review

Monotasking

Sometimes a seemingly minor interaction has a big impact.

At Black China Cafe in Santa Cruz, a small rock keeps napkins in place at the coffee station. With a cup of coffee in one hand, getting a napkin means picking up the rock, putting it down somewhere, picking up a napkin, and then putting the rock back in place.

I had just been thinking as I walked to the cafe about how hard it’s become for me to do something simple like walk across a parking lot without simultaneously jumping on my phone and checking my email, Twitter feed, etc.

I like being able to get lots of things done while I’m mobile, but at times I do this even when I don’t need to, and it starts to feel like a compulsion to multitask. Coming out of that context, the focused attention and step-at-a-time-ness of this little rock/napkin moment at the cafe shifted my whole pace of being.

Interaction design has always talked about temporal elements like pacing and pause. In their book, Interaction Design: Beyond Human-Computer Interaction, authors Helen Sharp, Yvonne Rogers, and Jenny Preece present a case study in which software testing showed adding pauses to a particular interaction would benefit users, and discuss some of the engineers’ reaction to this finding:

To make these changes would require adding additional menus and building in pauses in the software. This conflicts with the way engineers write their code: they are extremely reluctant to purposely add additional levels to a menu structure and resist purposely slowing down a system with pauses.

Right now, human/device interactions commonly involve waiting impatiently for our things to do what we’ve asked them to, and faster processing is often a goal. But as technological capability increases and our devices become faster than we are, I wonder if it may become increasingly necessary to also think about purposely slowing down elements of an interaction to create a different user experience – a’la the napkin rock – that is more aligned with “human-speed.”

Microsoft gets bookish

In our recent Reading Ahead research, we heard a lot from people about the physicality of books: how significant their tactile qualities and the kinesthetic experiences they afford are to the reading experience. So it’s interesting to see Microsoft going in a book-like direction with their Courier tablet device, here at Gizmodo.

While not explicitly geared towards reading, the Courier experience shown in the video below leverages some of the kinesthetics of book use, such as page turning (at least a digital approximation) and annotation.

What seems particularly promising here is development towards a synthesis of digital and analog gestural languages.

Related:
One Hour Design Challenge – Enter our Reading Ahead-based design competition in partnership with Core77 (the submission period ends Oct. 14)

The Trapper-Kindle – a response to the One Hour Design Challenge

Features vs. Innovation

Although the principal conceit of Apple’s latest Mac vs. PC ad is, as always, “PCs suck,” the ad does a nice job pointing to the difference between innovative thinking and the mere creation of features.

cup-holder-suit

While the cupholder suit that appears at the ad’s end is presented as a joke, many companies do have an unfortunate habit of burdening their products with clunky, grafted-on features as they try to push their ideas into new territory.

Compare the cupholder suit to Apple’s breakaway MagSafe cord, which the ad references. While there’s some debate over how well the Magsafe cord actually does what it’s supposed to, it at least intends to address a real issue that computer manufacturers had previously ignored (people’s cords get tripped on, yanked out).

Discovering that aspect of the user experience – however Apple may have done this – and recognizing it as one worthy of design intervention is the real innovation here.

Reading Ahead: Research Findings

Reading ahead logo with space above

(Updated to include slideshow with synchronized audio track)

We’re very excited today to be posting our findings from the Reading Ahead research project.

Lots more in the deck below, but here’s the executive summary

  • Books are more than just pages with words and pictures; they are imbued with personal history, future aspirations, and signifiers of identity
  • The unabridged reading experience includes crucial events that take place before and after the elemental moments of eyes-looking-at-words
  • Digital reading privileges access to content while neglecting other essential aspects of this complete reading experience
  • There are opportunities to enhance digital reading by replicating, referencing, and replacing social (and other) aspects of traditional book reading

We sat down yesterday in the office and recorded ourselves delivering these findings, very much the way we would deliver them to one of our clients.

Usually, we deliver findings like these to a client team in a half day session, and there’s lots of dialogue, but we tried to keep it brief here to help you get through it. (The presentation lasts an hour and twenty minutes.)

It’s been a great project, and we’ve really appreciated hearing from people along the way. We welcome further comments and questions, and look forward to continuing the dialogue around this work.


Audio

Reading Ahead: Building models

Reading ahead logo with space above

We’ve been hard at work synthesizing the Reading Ahead data. There’s a great deal of writing involved in communicating the results, and sometimes it makes sense to develop a visual model that represents a key idea.

Here are several partial models evolving through paper and whiteboard sketches, and finally into digital form.

We’ll be finishing synthesis soon, and publishing our findings on Slideshare, with an audio commentary.

Stay tuned…

Portigal-Consulting_synth5

Portigal-Consulting_synth4

models

Reading Ahead: Managing recruiting

Reading ahead logo with space above

There’s always something new in every project. Often we encounter a bit of process that we may not know how to best manage it. So we’ll make our best plan and see what happens. We learn as we go and ultimately have a better way for dealing with it next time.

In a regular client project, we write a screener and work with a recruiting company who finds potential research participants, screens them, and schedules them. Every day they email us an updated spreadsheet (or as they call it “grid”) with responses to screener questions, scheduled times, locations, and contact info. It still ends up requiring a significant amount of project management effort on our end, because questions will arise, schedules will shift, people will cancel, client travel must be arranged, etc. etc.

For Reading Ahead, we did all of the recruiting ourselves. Although we’ve done this before, this may be the first time since the rise of social media: we put the word out on LinkedIn, Twitter, Facebook, email to friends, and here on All This ChittahChattah.

While Dan lead the effort, we both used our own networks, and so we got responses in a number of channels, sent to either or both of us, including:

  • @ replies on Twitter
  • direct messages on Twitter
  • Comments on Facebook posts
  • Messages on Facebook
  • Emails (directly to either of us, or forwarded from friends, and friends-of-friends

facebook
A private dialog on Facebook

facebook2
Comments on a Facebook status update. Note that Dan is able to jump in and make contact directly

twitter
Direct Messages in Twitter

Some people were potential participants, some were referrers to other potential participants, and some were both. And given the range of platforms we were using, with their associated restrictions (and unclear social protocols), we had to scramble to figure out who could and should communicate with who to follow up and get to the point where we could see if the people in question were right for the study. We didn’t expect this to happen, and eventually Dan’s inbox and/or his Word document were no longer efficient, and as some participants were scheduled or in negotiation to be scheduled, he ended up with this schedule cum worksheet:

schedule

Being split across the two of us and these different media, eventually we were interacting with people for whom we had to check our notes to trace back how we had connected to them, which was great for our sample, since it meant we weren’t seeing a group of people we already knew.

It was further complicated when we had finished our fieldwork and wanted to go back to everyone who offered help close the loop with them, thanking them for help. Technically, and protocol-wise, it took some work (who are the people we need to follow up with? Who follows up with them? What media do they use), basically going through each instance one-by one.

twitter2

We haven’t figured out what we’ll do next time; we won’t forget the challenges we’ve had but there’s just not time or need right now to plan for the future. If I had to guess, I’d imagine a Google Spreadsheet that includes where we got people from, who owns the contact, whether they are participant-candidate or referrer, etc.). Despite being very pessimistic about the demands of recruiting, we still underestimated the time and complexity required for this project.

Reading Ahead: Looking for the story

Reading ahead logo with space above

I started today by typing up all of the Post-it notes you saw in our recent blog post on Synthesis.

This activity created a 6-page Word document of bullet points.

The next part of the process is something I always find challenging: taking an incredibly detailed list of observations, particpant statements, hypotheses, and ideas; figuring out what the Big Ideas are (there’s a point in the process where many of them seem Big!), and putting those into a form that tells a cogent story.

First step: make a cup of tea.

Ok, then my next steps were:

  • Categorize all those bullet points
  • Synthesize those categories a bit further
  • Write down in as short a paragraph as possible what I would tell someone who asked me, “what did you find out?”

Then I went into PowerPoint, which is what we use when we present findings to our clients. I’ll continue bouncing back and forth between Word and PowerPoint; each piece of software supports a different way of thinking and writing.

I dropped my synthesized categories into a presentation file, sifted all of the bullet points from my Word doc into the new categories, and then started carving and shaping it all so that it started to follow the paragraph I had written. (I’m mixing cooking and sculpting metaphors here.)

I printed out the presentation draft, and laid it out so I could see the whole thing at once.

Portigal-Consulting_synth10

Steve came back from a meeting and I asked him to read over what I’d printed out. He started writing notes on my printouts, pulling out what he saw as the biggest of the Big Ideas.

Portigal-Consulting_synth11

We talked about what he’d written, which led to an energetic discussion in which we really started to breathe life into this. Tomorrow, I’ll start the day by iterating the presentation draft based on our conversation.

Reading Ahead: Analysis and Synthesis

Reading ahead logo with space above

Synthesizing field data into well-articulated, data-driven patterns, themes, and opportunities is a big part of our work, but it’s an aspect that generally has less visibility than the fieldwork.

An essential early step in the synthesis process involves going back over the fieldwork sessions. An hour or two-hour interview creates an incredible amount of information. By going back into a record of the interview, we make sure not to leave anything significant behind.

We go through and make notes on interview transcripts (done by an outside service), watch videos of the sessions, and look over photographs, sketches, maps, and participatory design pieces.

Portigal-Consulting_synth3w
Annotated interview transcript

We made a bulletin board of the people we met, so they’re ever-present while we’re working.

Portigal-Consulting_synth1

Yesterday we came together to share the points we’d each pulled out. We present each interview, like a case study, to the team. Sometimes it’s just us, and sometimes our clients join us for part of this process.

Portigal-Consulting_synth2w

While one of us presented, the other captured the essence onto Post-its. We had a lot of discussion and debate while we did this, pulling together multiple viewpoints.

Portigal-Consulting_synth5w

When we were done presenting the interviews, the board looked like this:

Portigal-Consulting_synth4w

Our next step is to take these notes and start grouping them. We’ll look at different ways the information can be organized, and from there, will start refining our work and writing it up clearly and succinctly into a report.

ChittahChattah Quickies

  • Sherry Turkle is Professor of the Social Studies of Science and Technology at MIT and a sociologist. – She has focused her research on psychoanalysis and culture and on the psychology of people's relationship with technology, especially computer technology and computer addiction.
  • apophenia – danah boyd's blog – danah boyd is a researcher at Microsoft Research New England and a Fellow at the Harvard University Berkman Center for Internet and Society.
  • Michael Wesch's IA Summit 09 Keynote – Even though the presentation itself uses a lot of visuals and YouTube examples, I found the podcast to be extremely interesting and provocative. Wesch takes many examples of Internet and social media culture that we're familiar with but wraps them together to create a new and exciting story about the kinds of new things that technology is enabling. While I might have thought I knew it all already via danah boyd and Sherry Turkle, I learned a lot (that's not to say that boyd and Turkle haven't covered this material, I have no idea; but for me this podcast was a huge leap forward in my grokking of the issues).

ChittahChattah Quickies

  • BusinessWeek looks at how Steelcase went from user research data to insights to opportunities – "But most innovations depend on nontraditional research methods—ethnographic studies, customer-created collages, and so on—that can't easily be sliced and diced in Excel. That means synthesis can be one of the most challenging steps in the innovation process." This is an issue I'll be addressing in my upcoming workshop at EPIC 2009 "Moving from Data to Insights to Opportunities"
  • The Museum of Forgotten Art Supplies – Not technically a museum (or even an Internet museum) as they've really just aggregated images that represent tools and ways of working that have or are in the process of obsoleting.

ChittahChattah Quickies

  • UX guy complains about AA.com being crap and UX guy from AA.com responds – UX guy reprints email and then attempts to address corporate culture issue; strong opinions follow but most compelling part is the insight from the AA.com UX guy himself (known as Mr. X)

    "But—and I guess here’s the thing I most wanted to get across—simply doing a home page redesign is a piece of cake. You want a redesign? I’ve got six of them in my archives. It only takes a few hours to put together a really good-looking one, as you demonstrated in your post. But doing the design isn’t the hard part, and I think that’s what a lot of outsiders don’t really get, probably because many of them actually do belong to small, just-get-it-done organizations. But those of us who work in enterprise-level situations realize the momentum even a simple redesign must overcome, and not many, I’ll bet, are jumping on this same bandwagon. They know what it’s like."

  • Health management goes for ethnic marketing/customization: Asians and diabetes – Rice is a carbohydrate that is particularly unhealthy in large quantities for people with diabetes. That's why doctors and other health care providers are increasingly trying to develop culturally sensitive ways to treat Asians with diabetes – programs that take into account Asian diets, exercise preferences and even personality traits. "Diabetes is primarily a self-managed disease, and you have to try multiple approaches with different patients. But many of those are not culturally appropriate for Asians."

Series

About Steve