Description

Evidence Maps are a tool to help speech-language pathologists and audiologists stay up to date on the latest evidence-based practice. Lengthy articles are broken down into the relevant takeaways, so that busy professionals can filter down from massive collections of articles to find exactly the evidence that fits their question or patient.

Behind the scenes, these articles are put through an exhaustive, multi-person process to assess thier quality, so that only those articles that qualify as evidence-based are presented to the public in these maps.

Research

Initial user research was done to understand how speech-language pathologists and audiologists incorperated the first version of the maps (static pages of content) into thier work. These findings served as a guiding light throughout the process, to ensure that the outcomes were serving our member's needs.

Meanwhile, I needed to understand the back end process which was almost entirely offline, consisting of printed papers being moved from one desk to another and tracking processes on white boards. These process diagrams informed the back end system requirements.

Ideate and Design

After learning about the issues members face during the process, I began sketching, wireframing, and ideating. I developed several initial ideas for how end users could navigate to the content they needed, which would be user tested.

For the admin-side wireframes, I had the unique circumstance of having all of my users in one place, so the testing and iterating was nearly constant.

Test

In order to determine the best path forward, we were able to user test three new navigation and layout ideas plus the original idea by building out a single map in all three wireframes, and developing realistic scenarios for how providers might use the maps day-to-day. We assigned 20 people to one of each of the four prototypes, and asked them to find evidence that was relevant to a patient described or a question they might need to answer. I was also able to integrate CrazyEgg heat maps with my Axure wireframes in order to view exactly where on the wireframes users were clicking. The results helped solidify the group around the next steps.

Iterate and Refine

The outcomes of user testing solidifed the group around a filter system, which required a rework of thier backend process to include associating individual peices of evidence with specific, descriptive tags. New user-facing wireframes were developed and the backend wireframes were refined to accomodate the new process. We then worked with a vendor to develop and test the final product.

The End Result!