Rachelle Duncan

Overview

In my time in the Fintech space, I have formalized and refined a user experience program, which includes:

Outreach

In an ideal world, we would be able to send out mass invitations to every user that has ever touched our product. However, in our customer base that was likely to do more harm than good, provoking a hostile response rather than opening a productive discussion.

Instead, I sought to get buy-in from users for research activities before we needed to reach out to them using the following methods:

Examples of wireframes and prototypes used for user testing, spanning from low fidelity to high fidelity.

Running sessions

Scripts, templates, and best practices were standardized for the program. While for more experienced designers these functioned more as rough guidelines than a strict procedure, their existence was especially useful for new designers joining the team.

Interview best practices

Crafting a user study script

Drafting a list of tasks for a user study should be done with the utmost attention to detail to be sure your verbiage will not unduly affect user performance. Using the exact terms used on the page could inflate the success rate of tasks by causing the users to note elements they otherwise would have skipped over.

Because of this, the phrasing of questions in a user study script should be adhered to much more closely than an interview script, where it is treated more as a loose prompt.

Screens from the templates created for user study scripts and reports.

Returning results

For this program, I created standardized reports that are quickly put together for sharing post-study and could be easily referenced by key decision makers at later dates when working on roadmaps.

Templates for two types of report were created:

Program Benefits

Increased customer engagement

Accelerated research timelines

Increased actionable insights from reviews

When fully developed, the UX Research program helped increase customer engagement, accelerate timelines, and standardized communication for ease of use. Once built, a research initiative could be spun up within a day when a new concern arose. In a fast-paced environment, this agility was a tremendous boon to the team.