Posted by Whitney Quesenbery on July 01, 2008 | Comments (0)
Accessibility questions have come up on several lists recently, with an interesting twist. People were looking for answers not about exactly what they had to do, but why. What problem, for example, does a WCAG 2.0 checkpoint answer? Invariably, someone posts an explanation in terms of a story. Putting the guideline into a human context makes it easier to get your head around the "why". And that, in turn makes it easier to come up with a great design solution--one that not only meets the guideline, but does so in a delightful way.
Several years ago, a friend called me. He was working on his web site and wanted to know where he could find a text-only browser to test it with. He'd been told that it was important that it work without any images, but couldn't figure out why this made a difference, especially since he couldn't even find a browser that didn't display images.
To him, this seemed like an arbitrary rule, based on outdated technology. Of course, this guideline is not about technology, but about people. When he started to think about people, he immediately got the point. I didn't have to tell much of a story, just the beginning: "Imagine if you couldn't see the images...would your site make sense?"
Posted by Whitney Quesenbery on June 24, 2008 | Comments (0)
Kevin and I were talking about how we create stories. And that led us to think about how long a story has to last.
Of course some stories are carefully crafted. Kevin’s roller coaster story has been told and refined and retold. It’s on his CD “Kiss of Summer” where you can hear how finely tuned both the story and performance are. Good user research can be like this, as you sift through the data to find just the right way to share what you have learned.
Others are just quick illustrations. Both of us construct them on the fly as a way of illustrating points we’re making. Once you get used to the idea – and if you know your personas well – it gets easy to envision them in a situation, and tell that story.
Kevin brought up the idea that stories can be like a mold or a form. They are created to be used to create something else. An architect he knows is building his own house. The walls of the foundation will be made out of concrete cast in styrofoam. These seem like opposite materials. But when you put them together, you get the freedom and fluidity of styrofoam to make the prototype, and the permanence of concrete. It turns out that the foam is just strong enough to hold its shape while the concrete hardens. Then it crumbles away.
Scenarios for personas – the stories about what the user experience of a new product might be like - are often like this. They represent careful analysis, and are meant to be used over time. They gradually gaining solidity as they are designed and developed. But in the end, what’s left is the final product, not the story. These stories give a shape to the idea, but only last long enough for the idea to take shape around them.
How do you use stories in your work?
