Opentext

Elevating Security and Data Processing: A Transformative UX Journey

5 mins read

· Last updated on July '22

Under NDA

Elevating Security and Data Processing: A Transformative UX Journey

This case study presents a sample project inspired by a real-world redesign of a security and data-processing platform. Due to NDA restrictions, I cannot disclose the actual project, but this closely mirrors the challenges tackled, the design process followed, and the impact created.

In a world where data security and operational efficiency are paramount, organizations require platforms that not only safeguard sensitive information but also simplify complex workflows. This case study details my role as a User Experience Designer in reimagining a legacy system into a modern, efficient, and compliant solution. It’s a story of collaboration, empathy, and innovation one that transformed user frustrations into seamless experiences while aligning with business goals.

Role

User Experience Designer
Interaction Designer

Collaboration

UX Designer
Researchers
Engineers
PM's and Business Analyust

Duration

8 - 10 Weeks
June '21 - January '21

Tools

Figma/Axure RP
Jira Atlassian
Google Doc's
Zoom and Teams

I was responsible for designing and improving the platform’s user experience, ensuring efficiency, usability, and compliance. My primary focus was to:

  • Introduce automated document classification to reduce manual workload

  • Develop intuitive interaction flows that align with user behavior and business needs.

  • Present wireframes and prototypes to internal and external stakeholders.

  • Collaborate closely with engineering, designers, and business analysis teams to ensure seamless execution.

PLANNING THE PROCESS

Design process

The project followed an iterative and non-linear design approach, ensuring that user needs remained the focus while balancing technical feasibility and business viability.

USER RESEARCH

Research summary

I conducted user interviews via remote sessions to gain insights into how users performed tasks, their motivations, and pain points. Observations and direct engagement helped shape the solution. A competitive analysis was performed to benchmark against industry standards.

  • Manual document classification was time-consuming, leading to inefficiencies.

  • Users worked exclusively in office environments, leading to inefficiencies.

  • There was no way to annotate documents, making collaboration difficult across teams.

Defining the Problem

Problem statement

Users faced challenges in tracking, annotating, and categorizing security-sensitive documents, leading to inefficiencies, collaboration gaps, and compliance risks.

  • Introduce inline annotation feature for better collaboration.

  • Automate document classification workflows to improve speed and accuracy.

  • Ensure compliance transparency without compromising user experience.

IDEATION

User flow diagram

Collaborated with business analysts, developers, and compliance teams to define workflows and explore possible solutions.

  • Created affinity diagrams to identify major pain points.

  • Mapped user journeys to visualize where users faced friction.

  • Defined task flows for new annotation and classification features.

Workflow Context

The workflow visualizes a content extraction and integration process for various types of inputs, such as email receipts, image receipts, and scanned records. These inputs are processed through a content extraction phase and integrated into a system for further use.

Key Elements:

  • New Content: Represents the incoming data, such as receipts or documents, which need to be classified and processed.

  • Processing Categories:

    • Email Receipts: Content extracted from emails.

    • Image Receipts: Scanned images requiring OCR (Optical Character Recognition) or other processing tools.

    • Scanned Records: Physical documents converted into digital format for processing.

These inputs are processed through a content extraction phase and integrated into a system for further use.

  • Content Extract: A centralized stage where data is cleaned, structured, and extracted for meaningful use.

  • Integration: After extraction, the structured data is integrated into a larger system, ensuring it’s ready for workflows such as compliance, reporting, or analytics.

Low-fidelity wireframes

Initial pen-and-paper sketches were created to explore different design solutions. These wireframes were tested and iterated upon based on client and user feedback.

Design & Prototyping

Mid-fidelity wireframes

Collaborated with business analysts, developers, and compliance teams to define workflows and explore possible solutions.

  • Created in Figma to test interactions and navigation flows.

  • Incorporated internal design system components to maintain consistency.

Prototyping & Design Execution

High-fidelity visual design

Collaborated with business analysts, developers, and compliance teams to define workflows and explore possible solutions.

  • Created in Figma to test interactions and navigation flows.

  • Incorporated internal design system components to maintain consistency.

Lessons Learned

What worked well

The project resulted in a powerful and user-friendly app that helps users efficiently manage their credit cards and maximize savings opportunities. Settle Rewards simplifies the process of keeping track of rewards and offers, providing value to users with busy lifestyles.

  • A structured design system accelerated design execution and maintained consistency.

  • Iterative design cycles improved usability at every stage.

Future Updates

Key learnings - What can be improved.

More frequent usability testing could have further refined the product.

  • More frequent usability testing could have further refined the product.

  • Better cross-timezone collaboration with visual designers would have improved design iteration speed.