User scenarios have been widely adopted by web designers as a useful tool for helping ensure sites provide what visitors need and expect. Less well-known is that they are also a great tool for ensuring offline communications do the same.
Recently I was in Sears. They have created central checkout kiosks at my local store (Cambridge, MA) which is a step forward, because previously, it was impossible to find a cash register and a salesperson at the same time. Now there's a large checkout hub at the exit/entrance to the connecting mall. When I entered the store I came from downstairs – not from the mall. I did not pass a kiosk. I shopped and could not find where to pay. I looked for signs, and found this (pardon the fuzzy, surreptitiously shot image).
The sign points to a wall. There's no pay kiosk on either side of the wall.
This could be blamed on a number of things, but for the sake of this post I'm going to pin it on a lack of user scenarios when the store was planning the pay kiosks. If, when someone in Sears corporate offices was thinking about or planning the kiosks, the context of shoppers making purchases came up, hopefully they would have realized that finding where to pay is just one part of a flow that ends with paying – that paying is a part of a larger scenario.
A few years ago, we worked with the marketing team at Sloan Executive Education. They run programs that are attended by professionals from all over the world. Aware that there was a flow of information, and that it needed to be consistent to ensure that expectations were met, we mapped out scenarios related to how potential participants found out about the programs, registered, made travel plans and arrived at the program. After listing all the recipient types and situations, we could evaluate the communications and see where information needed to be changed, added or made more consistent.
There are hybrid online/offline situations that call for scenarios as well. Hospitals can have complex and inconsistent technical setups that send healthcare workers back and forth between paper and electronic files. Working with a client who provides software to streamline hospital discharge, we needed to design a fax form that would literally connect paper and digital correspondence. Care facilities received faxes from hospitals to let them know there was a potential patient for them. Included in the fax was a unique code that, when entered on a website, would provide the patient details and acceptance information. We used scenarios that captured the full flow of contact – online and offline. Because we looked beyond the web interactions we were able to design a complete system that worked, not just a form or site that only addressed part of the situation.
User scenarios beyond the web
Posted:
Monday, February 15, 2010 |
Posted by
Tania Schlatter
|
Labels:
content planning,
healthcare design,
higher education,
information architecture,
marketing,
process,
scenarios,
servicedesign,
user experience
Subscribe to:
Post Comments (Atom)
About seen + learned
An archived blog by Deborah Levinson and Tania Schlatter, formerly of Nimble Partners, about what we learned and did as user experience designers (creating human-centered websites and applications: information architecture, prototyping, usability and visual design) from 2008-2014.
Labels
Monthly Archive
- Nov 2014 (2)
- Jun 2014 (3)
- May 2014 (3)
- Apr 2014 (1)
- Mar 2014 (1)
- Jan 2014 (2)
- Nov 2013 (1)
- Oct 2013 (1)
- Sep 2013 (2)
- Aug 2013 (2)
- Jul 2013 (1)
- Jun 2013 (2)
- May 2013 (2)
- Apr 2013 (3)
- Jan 2013 (1)
- Oct 2012 (1)
- Sep 2012 (1)
- Dec 2011 (1)
- Oct 2011 (2)
- Sep 2011 (1)
- Jul 2011 (2)
- Jun 2011 (1)
- May 2011 (1)
- Mar 2011 (1)
- Jan 2011 (1)
- Nov 2010 (1)
- Oct 2010 (6)
- Sep 2010 (2)
- Jul 2010 (3)
- Apr 2010 (1)
- Mar 2010 (2)
- Feb 2010 (1)
- Nov 2009 (2)
- Sep 2009 (2)
- Aug 2009 (1)
- Jul 2009 (1)
- Mar 2009 (4)
- Jul 2008 (1)
0 comments:
Post a Comment
Note: Only a member of this blog may post a comment.