UX CASE STUDY
Worked on flows for Core Capture, an information capture SaaS application built and owned by Opentext.
PROJECT OVERVIEW
The Product
OpenText Core Capture is an information capture SaaS application for file classification and data extraction. It provides standard capture features, such as document scanning and processing powered with AI. [1]
Project Duration
Jan 2022 - May 2022
My Roles and Responsibilities
UX Designer I was assigned to be responsible for any needed designs that were to happen in Core Capture. Primary responsibility was to get two functionalities included in the product- to be able to annotate, and to identify the documents that have been scanned according to the existing file type list.
Design Strategy and WBS through sprint meetings.
Interaction design and related prototyping.
Opentext internal design system was used for prototyping.
Getting the wireframes approved in the internal and external stakeholder presentations.
Collaboration with the visual design, development & business analysis teams to make sure the product stays in line with the captured users' expectations.
Deliverables Clickable protyope in Axure RP, video demo of the designs, documents like the user flow diagram, personas, and journey maps. Visual designs were created in Figma
DESIGN PROCESS
Iterative and non linear design thinking was adopted where user was kept at the centre. At the same time, technical feasibility and business viability were considered.
USER RESEARCH
Research Summary
User interviews through zoom meetings to understand how the users presently accomplish the tasks, to get more insight into their motivation and pain points. By talking, observing, engaging and empathizing with them, I was able to pull few key findings that would help shape the project. Competitive analysis was done to understand competition better.
Users were only using the product in their offices.
Users wanted a fast forward way to classify the documents they were scanning into pre defined types.
They wished to leave and recieve notes while passing a document to the next stage in the product as there would be a new user using it in next stage.
Most of them were using big screens and laptops for the work.
DEFINING PROBLEM
Problem statement(s)
There were multiple problem statements for different scenarios, an example of it is:
Objective for providing annotation features in the system:
Users are losing track of critical information which surfaces up in the workflow and is closely likned with a certain part of the document(s).
User personas
Different personas were created for different kinds of users- document scanning employee, administrator, etc.
IDEATING
Brainstorming
Sessions conducted included participants from wide range of teams like the business, development, testing, client teams to identify implicit and explicit user needs.
Affinity diagrams and journey maps were created.
User flow diagram
To illustrate the user flow within the application, several user flows were discussed.
Low fidelity wireframes
With pen and paper wireframes, multiple version of each screen were created to increase intuitively as much as possible.
These were presented to the clients and users to get their feedback and comments in iteration.
PROTOTYPING
Wireframes: High Fidelity
Axure RP was used.
These were created and shown to stakeholders for testing and initial ideation to filter out the best solutions through A/B testing, co-designing, and other approaches.
We followed the internal Opentext design system.
Visual Design UI Prototypes
Figma was used by the visual design team.
These were created and iterated over user testing and feedback cycles.
I will not be able to share the link to prototype as I'm under an NDA to not disclose any information from the software. However, I have tried to explain the process clearly without revealing much details about the application.
TESTING
Conducted A/B and usability tests over different features of the app in different iterations. This was done remotely through calls.
This was done in a feedback meeting with the involvement of relevant stakeholders.
The live testing of the software to be done through the annual Opentext event called Opentext World as users are easily available.
REFLECTION OVER LEARNING
Using a comprehensive and well defined design system helps in saving time and keeps the applications consistent.
What I would have done differently.
It would have been better to be able to conduct feedback sessions and user tests more frequently.
The visual designer was in another time zone and hence they could not be actively involved with the entire design process. It would have been fortunate to have time for some sync up calls with them.
REFRENCES
Thank you for reading!