Digi Capture: Prototype concept testing

Project Description:

Create an in-house solution to replace a vendor application that enables bankers to save specific documents in a file storage repository and add metadata to those documents so they can be retrieved in the future.

Project Impact:

Enable Product team to confidently start the build of the new application based on knowledge that the user interface the Design team created is intuitive to end users.

Define the problem

Worked with stakeholders to define the problem space and decide what aspects of the overall experience is in an out of scope for this research. Established clear timelines based on the project team's needs and the scope of this research.

Problem Statement:

Employees need a way to save specific types of documents and categorize those documents so they can be found later. The current system that accomplishes this task is going to be phased out and a new system needs to be built to replace it.

Create study plan and moderators guide

Define project background, business objectives, research objectives, timeline, and specific questions to ask participants during the study. Work with design, product, and development stakeholders to validate the information in the test plan and ensure the stakeholder's key questions are addressed.

Research objectives:

Understand the context of use for the current application used to store documents and add metadata
Determine if the new single page flow is more intuitive to end users than the old multi-step wizard flow.

Study type:

Moderated usability testing with a Figma Prototype

Recruit and schedule participants

Recruited 10 participants through established processes.

Participant demographics:

Representation from the 3 business lines that will be in the pilot
Mix of new vs. tenured employees

After participants were identified I reached out to them to determine if they were willing to participate and schedule a time to meet.

Run sessions

Met with participants remotely. Had participants complete tasks within the prototype. If participant had trouble with the task I asked probing questions to understand why they had difficulty with the task.

Analyze data

Used online white boarding tool (Mural) to consolidate and organize information learned during the usability testing.

Identified positive and negative aspects of the design from the user's perspective.

Created findings based on the observations and questions in the usability test.

Create presentation

Created slide deck and Confluence page to convey key learnings from the research to the stakeholders and decision makers. Multiple versions of the slide deck were created to convey information to different levels of stakeholders, e.g. Platform leaders vs immediate project team

Present findings

Presented findings to stakeholders while allowing room for discussion of each key finding. Utilizing this method enables stakeholders to build a shared understanding of the finding and if it is an issue commit to a specific owner and timeframe to address the issue.

Follow-up

Met with design team to carry findings forward when design decisions were made by acting as the voice of the user in design meetings.

Track progress towards rectifying issues by following up with the owner to check in about the status.