One of the big themes running through many of the workshops at this week’s
CALL conference in Montreal was redesign of products, platforms and processes. The conference ended yesterday.
The Monday session entitled “Please Don't Make Me Think: User Testing a Faceted Search Engine” was about how the Centre d’accès à l’information juridique (CAIJ), Quebec’s Courthouse library Network, conducted user testing sessions to validate the ergonomic and design aspects of many of its tools, including its new faceted search engine
JuriBistro UNIK.
I served as a guinea pig at the session. I volunteered to go up on stage and “test” a music store website. I was told to try to order the latest Céline Dion CD for a Mother’s Day gift and failed miserably. The presenter then explained that she had deliberately chosen a badly designed website. My embarrassment served as a perfect introduction to the importance of usability testing.
During user tests relating to JuriBistro UNIIK, CAIJ made some very surprising discoveries about how people think about their searching, what they see and do not see on your site, and how they (mis)interpret symbols or language that appear perfectly clear to project members.
Lo and behold, they discovered that lawyers - their users - READ text and do not see or even understand many of the pretty and cute pictograms designers provided as shortcuts to very important features such as the fulltext of cases. So they replaced icons with text like “Texte intégral - Jurisprudence” and all the guinea pigs (sorry, I mean test lawyers) were happy.
Other features that test subjects overlooked or failed to understand included such things as sort options, the concept of "keywords in context", links to help and search tips and the icon for further filtering of results which people thought looked like a martini glass (it was the Excel spreadsheet symbol for filter). Most of these items were replaced with text links.
The speakers, CAIJ’s Monique Stam and Anastasia Simitsis, User Experience Director with W.illi.am Digital Intelligence, used the Céline Dion example to emphasize a point. User focus groups are insufficient, watching what potential users do when replicating real-life scenarios is required.The experience of listening to test participants think out loud as they try (and very frequently fail) to do stuff on your test site is usually an eye opener for project team members, designers and your boss.
They explained the various possible flavours of usability testing, but they all offer similar benefits:
- identifying and fixing problems early (“why does CAIJ have a martini glass on its results page?”)
- validating assumptions
- solving opinion battles among team members (web designer: "I think the filter pictogram should go here"; project manager: "No, I am sure the users will be more at ease if the filter is over there"; your boss: "I say the filter belongs next to the results"; of course, the test users are all going: "What's with the CAIJ and all their stupid martini glasses all over my results page?")
- establishing a baseline to measure improvements
- reducing risk and reducing costs (it is way cheaper to fix problems during design than after launch).
Another Monday session on "Technology Project Management: Complexities and Challenges” offered three perspectives on how to manage large projects as well as stakeholder expectations.
Julie Allard from the Quebec public corporation SOQUIJ shared her experiences with the design of the new product that will replace
its AZIMUT Juris.doc legal information search tool in the fall of 2013. The project is highly complex, has incredibly short deadlines, involves a multidisciplinary team and clients are demanding. [SOQUIJ held a breakfast demo of its new search product on Tuesday morning. The changes can be easily summarized: extreme simplification of the interface. You search and find and manipulate results on just 2 screens. Everything happens on the first search screen and then on one single results screen. Full stop. Quite impressive.]
Getting the preliminary project planning right is key. This involves consulting customers and deciding what is and what is definitely NOT part of the project to maintain focus and avoid mission or project creep, probably the kiss of death of many projects. How many times does this simple truth get overlooked? Figure out what is NOT part of the game plan and you will be happier.
Among the successful strategies Allard mentioned for not losing control: chunking the project into shorter cycles with precise interim deliverables to ensure the project team achieves small but constant victories along the way; managing change requests ; user testing, and quality assurance/control during the entire process to make sure any changes are in line with the needs expressed by customers (testing and quality assurance are too often overlooked until the very end); tracking problems and anomalies as well as tracking measures taken to address them.
Managing stakeholders and their expectations requires a lot more thought than we often assumer. In the case of SOQUIJ, they came up with a series of clear roles: a dedicated project manager, a project sponsor, a person to act as the representative of the customers, the project team, testers, etc. All clearly delineated roles.
Frédérique Tessier, project coordinator at
Éducaloi, an award-winning website for public legal education, took the audience through the recent redesign of the site which included the complete reorganization of its content as well as migration to a new open source platform.
The organization asked an outside firm to evaluate a list of prospective agencies who could manage the project in cooperation with Éducaloi members and external contributors (lawyer-writers).
Finding content seemed to be one problem with the old site. 10 people were involved in a card sorting exercise to categorize the site’s hundreds of articles into a clearer classification scheme based on 10 broad topics (e.g. family), then broken down into nodes (“divorce”) and then into narrower areas (“child support”). On the page of any given article on the new site, there are links to other material within the same node and topic as well as in related nodes under different topics.
The big behind-the-scenes change for content producers has to do with how changes/updates to content are managed. The new content management system uses screens to add changes to any piece of legislation such as new section numbers or wording and find which pages link to that statute. If many articles refer to the same statutory information, they can all be updated at the same time on one legislative input screen.
The final presenter at that session was François Montreuil, director of IT at
Bibliothèque et Archives nationales du Québec (BAnQ).
He focussed on streamlining stakeholder management during major technology projects.
BAnQ used to run projects with a 15-19 member project management committee. Meetings were long, unwieldy. A new executive committee was created with 7 people that meets before the larger committee. It invites stakeholders to address it according to need and expertise and they are asked to leave after they have made their presentation. Actual projects are run by project teams with specific mandates and deadlines.
Everyone agreed there is no perfect structure but clear communications, follow-up, and reporting structures as well as behind-the-scenes communications to minimize irritants and deal with differing interpretations of how a project should proceed (i.e. politics) are essential elements.
Labels: conferences, e-resources, law libraries, web design
