A Dive into a Specific Instance of Cultural Probe Use.

Written by: bnjmnjackson

Reading: Cultural Probes by Gaver, B., Dunne, T., and Pacenti, E.

I’m going to assume that you, the reader, know the very basics of what I mean when I say “Cultural Probe.” If this isn’t the case, feel free to take a look at an earlier post of mine: What are Cultural Probes? The Basics.

A note on the context of this article (which I will refer to). In the late 1990s, a design team was assigned to, over several years, look at possible novel interaction techniques to increase the presence of elderly in three communities. Bijlmer, in Amsterdam, Netherlands; a community in Oslo, Norway; and Peccioli, a commune in Italy. The project was very open-ended, which gave the team a lot of room to do whatever they see fit.

Now that that’s out of the way, let’s dive in. First of all, let’s contextualize the design team. Starting this project, they had no data on these communities except what’s in the public domain. It was understood that these communities were diverse from the start, so there was likely not an objectively correct approach to take for any or all the communities. Given how large and diverse these communities were, the team decided on using Cultural Probes to get a better grasp on what they were really working with. The particularities of what each community lacked, to put it generally.

Given how universally general each of these proposed solutions/additions had to be to be productive to an entire community, the team obviously couldn’t take a path of design that many would consider ‘traditional,’ as this isn’t a traditional task. The team decided to take an aesthetic artist-designer approach, looking for “… cultural implications of our designs, and ways to open up new spaces for design.” Using logic-driven scientific approaches to new design will only allow one to stray but so far away from the previously set path of knowledge, whereas empirical data from informal analyses, or even stray observations found by chance, can spark new creative jumping-off points.

So they had a direction, and a method – now they needed implementation [of the probes]. Before anything was made or implemented, several challenges had to be addressed. Firstly, as we all know, next to nobody likes answering phone calls from local government officials, even though in the officials’ minds, all they are doing is trying to help the people they are calling. (If we give them the benefit of the doubt, that is. Maybe this is a poor example) This problem is exacerbated by the fact that there is likely going to be an immediate distance between the team and the community caused by the notion of having professionals flown in to help said community.

Put yourself in the shoes of someone in a community like this. These communities are inherently full of people who are at once wizened by age and likely free of the labors of work, but also still full of many people who are disabled in some way(s). Society often stereotypes the elderly as a group who are needy and fragile. Whether either or both of these are worth considering as a general fact is irrelevant when you consider that if your group is actively stereotyping a community with which you want to help, you likely aren’t going to be very productive. Taking this aura of looking-down-upon away frees up a lot of design space. It is possible to go too far the other way, however. As a team with a goal, if the interaction between you and the community is too casual, you may end up with a year of wasted time from irrelevant responses. Taking this into account, the team wanted to create probes that were interesting, open-ended, and personable while not being either too condescending or too formal.

“We wanted to lead a discussion with the groups towards unexpected ideas, but we didn’t want to dominate it.”

So let’s look at what they ended up doing. (Spoiler: It was indeed successful and productive) In making the probes, the team tried to be revealing to the groups as they asked them to be revealing to the team. There is a common theme of mutual respect that can be applied to any co-design project. The final probes contained maps, postcards, cameras,and requests for small photo albums.

Maps were bundled with small inquiries. Some of these were very straightforward (A map of the world paired with “Where have you traveled in your life?) while others were more poetic. (a map of the community, with “If Piccioli was New York” alongside of stickers of the Statue of Liberty, Times Square, or a scene of people injecting drugs) The point of these maps were to be fun, individualized, and engaging. The postcards were similar, as they all had small prompts. A reason these are attractive to the team is they have casual connotations. Unlike having a formal questionnaire dropped at your door, you can personalize your answer and mail it to the exact person on the team who will read it. The disposable cameras also had requests for each picture slot, like “Your home” or “The most attractive place around,” except that near half the slots were titled “Take a picture of anything you would like to show us.” The photo album simply requested “6-10 photos to tell us your story.”

While the Oslo group returned most all of the materials, the Bijlmer group returned a bit more than half, as they seemed less convinced about the project as a whole, and the Piccioli group returned less than half, despite being enthusiastic about the probes when the team was there in person. But all of this was still great for the team. For example – “The group in Oslo is affluent, well educated, and enthusiastic: We are proposing that they lead a community-wide conversation about social issues, publishing questions from the library that are sent for public response to… public spaces.” This is clearly something that the team would not have concluded if it were not for this open ended style of information-collection.

Although the probes were successful in their goal of familiarizing the team to the community and vice-versa, they did not directly lead to any of the following designs. Instead, they inspired the team in ways that could not have been anticipated, and it must be stated that this was the goal of the probes the entire time.

Cultural Probes are clearly useful when implemented elegantly, but it must not be understated how much thought must go into analyzing what particular challenges a set of probes must face for a given project for a given community.

Bad Design is Everywhere. Part 2, Inclusivity Boogaloo.

Written by: bnjmnjackson

Reading: Don Norman on – I wrote the book on user-friendly design. What I see today horrifies me from FastCompany Business Magazine. That said, Don Norman has credentials on his own, not to be discounted through the medium of an online magazine.

Inclusive Design (design intended to help more than just one target audience), when done well, looks like a happy accident. Closed captions for those hard of hearing? Doubles perfectly in loud sports bars. Sloped curbs at intersections for the blind or elderly? Perfect for mothers with baby carriages, or travelers’ suitcases. The point is, even if you can sustain your (business, product, idea, etc.) only off of your target audience currently, we are now reaching a day and age where the percentage of elderly persons in society is growing rapidly.

“What do you mean? There are ramps everywhere, hearing aids, ‘large text modes’ on phones, and handicap accessible seats everywhere!”
I hear you, I promise. Let’s dig a little deeper so I can hopefully show you that this is a problem. Many of these anecdotes are from Norman himself (a self-proclaimed elderly man) or the people he’s around, relayed by him through this article. That said, Norman claims to still be a functioning member of society. Still able to run errands without passers-by becoming irritated at his sheer senility.

For starters, elderly people typically have less strength, dexterity (accuracy), mobility (speed), less clear vision, and fading hearing. This isn’t comprehensive or perfect for any one person, but it’s what we’ll focus on as a generalization. If we look as something as simple as groceries, it may not be obvious, but it’s possible that someone may need an over sized wrench to open a jar. Norman himself says that he and his wife choose which restaurants they prefer based on the ambient noise, as constantly loud locations will give them headaches over the course of an hour. What about something less obvious? Large-text modes on phones, in a vacuum, seem like a great idea, right? But, when a company like Apple decides to make the text on their phones a font and color that’s often neigh-invisible without being lucky and having a heavy background contrast, this mode is just a facade. (If you have an iPhone, go to your settings, really squint your eyes, and try to read the grey name of your current WiFi)

There are plenty of more examples of non-inclusive design, but I hope you get the jist. What about things designed exclusively for the elderly? That should be easy, right? Well, imagine a classic wooden walking cane from the mid 1900s. Fine, right? Well, nowadays, companies that design canes and walkers for the elderly are focused so much on function, they’ve thrown form out the window. Modern tools for the elderly are often given this aesthetic that reads ‘I’m fragile and weak and old.’ So much so that many people, against their better judgement, will forego using walkers, canes, or hearing aids for this reason.

“Are elderly people handicapped? Maybe, but so is a young, athletic parent while carrying a baby on one arm and a bag of groceries in the other,
and perhaps trying to open their car door.”

Don Norman, on high contrast or large text in phones

We must not forget that when we are designing for a non-standard audience, not only should we consider their circumstances, but also remember that customers are still human beings. We’ve proven that we can design for the disabled while being inclusive to the general public (and the vice versa less so, but we’ve still seen success). We just need to not forget the basics while we are shooting off into new technology or infrastructure at lightspeed.

Bad Design is Everywhere.

Written by: bnjmnjackson

Watch (5:09): It’s not you, Bad doors are everywhere. – Vox

Think of a door, just one side. What does it look like? Does it have a knob? If so, Is the knob on the left, or right? It’s pretty consistent, as far as I’m aware, that we’ve gotten used to pulling knobs on the right, and pushing on the left. Now what about doors in the wild? Maybe in an office building, or the entrance to a hotel. These often have “push” or “pull” labeled, but why? Likely because if it wasn’t labeled, people will take an incorrect guess. This should happen around 50% of the time, assuming a regular bad door, but it’s likely you know of a door that maybe 80-90% of people guess wrong on the first try. These, we call Norman Doors. (Coined by Don Norman, Author of The Design of Everyday Things)

I’ve mentioned Participatory Design, but if we go a single step up the tree, ie. more generic/further from the user, we have something known as Human-Centered Design (HCD). We can easily understand what this means (Design centered around people), but we can dig a little deeper. Two important parts of HCD are what we can call Discoverability and Feedback. Discoverability is what causes all these door problems. Discoverability is, quite literally, the ability to discover what a user can do to this something. The problem with many doors is that, on the side meant to be pushed, they may have a large handle which can be pulled. This is obviously the opposite of what we want, so we should aim to remove this ambiguity. One of many ideal doors may have a flat metal rectangle on the side meant to be pushed, as it has a very clear Discoverability. The answer of “What are my options” is set to one- push. The other side may have a cylindrical vertical handle, as it’s much more intuitive to pull a vertical handle and push a horizontal one.

Feedback, while not entirely relevant to doors, is another important part of HCD. If you’ve ever seen Apple’s iPhone X, It has no buttons on it’s touchscreen face, but it does a decent job (so I hear) at making it obvious what each touch or set of motions does. Relatively poor Discoverability, but relatively good feedback. Now, if you’ve ever had a new car, with buttons that have terms you don’t know, and pressing them appears to do nothing at all, that is a great example of something with poor feedback.

Clearly, most of these things are not designed with malice, so why is it such a common issue? The answer is likely oversight. Underwhelming, I know, but we can avoid this, rather easily with Iterative Design. Step one: Observe people. Step two: Generate ideas or solutions. Step three: Prototype in some way. Step four: Test it! Whether that be through WoZ, or just trying the thing yourself. Just ask “Is this intuitive?” If not, then we go back to step one, with our newfound knowledge, and try again.

(Together, we can save humanity from terrible Norman Doors)

What is Participatory Design? The Basics.

Written by: bnjmnjackson

Reading: Universal Methods of Design by Bella Martin and Bruce Hanington.

Participatory design is a bit broader than the other concepts previously discussed. It refers to, during most of the design process, having an active communication and engagement between the design team and the user(s). There are many ways of going about this, including, but not limited to: Cultural Probes, face-to-face activity-based co-design, or diary studies*. The point is simply that the users-to-be are directly involved in impacting the design process. How one goes about a specific type of Participatory Design (Should we use Cultural Probing? Or Diary Studies? etc.

*It should be noted that Diary Studies are similar to Cultural Probes, but instead of a kit, the user interacts with a guided diary over a significant period of time.

What are Cultural Probes? The Basics.

Written by: bnjmnjackson

Reading: Universal Methods of Design by Bella Martin and Bruce Hanington.

Cultural Probes are, at their core, a creative way to get a better understanding of a community, possibly in ways that the designer(s) could not have anticipated otherwise.

A Cultural Probe is something (typically a package of items) sent to people in a community with instructions of how to use the contained items, and a return address. The intent of these packages is to consider the personal context of people in said community. The goal is not to send a map and say “How exactly do you get from this point to that point?” These probes are much more open ended and exploratory in nature. A better example of something in one of these kits may be a small audio recorder with instructions of use, and have instructions – The next time you go on a walk, be it to a cafeteria, or simply your favorite place to sit and read outside, bring me with you, and talk to me! Tell me anything running through your mind. There is no such thing as unimportant, here. It is important for these probes to be informal, as we want personable data, but also thoughtful, as we want high response rates, while getting thoughtful, respectful feedback from enthusiastic users. Once again, the goal is not to get data in numbers, but to better understand the target community as a whole, in relation to our project.

What is the Wizard of Oz Technique? The Basics.

Written by: bnjmnjackson

Reading: Universal Methods of Design by Bella Martin and Bruce Hanington.

The Wizard of Oz (WoZ) technique, at it’s core, is a way for testing the feasibility, functionality, and general effectiveness of a UI without requiring all the time and effort into making a prototype. This is done by creating a mock-up interface for the user to ‘use’, where someone(s) on the team (the ‘Wizard(s)’) manually implement the interface. For example, say I wanted to design a smartphone banking app, which has a few functions, and a few different pages. If I wanted to gauge how a customer was feeling about this using WoZ, I may preemptively draw out all the possible pages the user could access on small whiteboards, and when the user ‘clicks’ (in this case, points and tells me “I would like to click this”) on something, I would swap out the whiteboards and adjust any numbers, as needed. The whole point is to get a general sense from the user. ie. “Man, it’s annoying that I cant get from here to there in one click.”

“Just keep a running list through Amazon’s Wish List service (here is mine).”

Written by: Rajen Tandel

“Just keep a running list through Amazon’s Wish List service (here is mine).”

I think you meant to include a link in this sentence.

“When I start a book, I almost always go straight to Wikipedia (or Amazon or a friend) and ruin the ending.”

Just to be clear, you are talking about nonfiction books in this right? I don’t see the point in doing this for fiction or stories.

Great article.

Written by: Rajen Tandel

Great article. I’ve been guilty of reading as a form of procrastination before. But if you like autobiographies, I really liked Arnold Schwarzenegger's Total Recall. To go from a small Austrian town, to a professional bodybuilder, to an actor, to the governor of California is incredible. It’s pretty long but its worth it. The Glass Castle is another memoir that I really liked.

I also haven’t read many from your recommended list. I’ll check them out. I also like the last bullet: “For something beautiful”.

Collabanno Progress Report 6/21/2018

Written by: Rajen Tandel

I continued working on the CORS proxy today. It’s still not completed but I am getting close. It’s formatting the request correctly, but the interaction between React Components has been a bit strange. It’s updating state, but not rerendering the component correctly.

Tomorrow I plan to continue working through this issue as well as refactoring the code in the project. A lot of the code up until this point has been just to get the project working. Now that the project is beginning to work, I feel like continued work will be easier if the code is more well written.