Overview 👀

The virtual assistant is a concept developed for large corporations. Its purpose is to make it easier for engineers to access and understand complicated documents like engineering manuals. The assistant acts as a learning platform to help engineers process large amounts of information in a corporate environment.

Tablets of Content

Problem

Solution

Scope

Design System

Prototype

Outcome

Screenshot 2024-04-13 at 15.22.08.png

<aside> 🚨 Note

ℹ️ TL;DR - Short Summary Description + video explaining the case study

<aside> ⏩ In this video, I provide a brief overview of the case study, focusing on the key takeaways, challenges, and outcomes.

</aside>

https://www.loom.com/share/9644395789e1453b8255758a2f9bb5b2?sid=30994338-a5a5-4fcd-a1dc-5e575c578b6c

</aside>

Context

<aside> <img src="/icons/compass_gray.svg" alt="/icons/compass_gray.svg" width="40px" /> I joined the design team when the Virtual Assistant was already a company product available on VR and mobile platforms. At that time, the virtual assistant was still in its early stages of development as a demo web app. The software engineers developed the demo and showcased it to potential clients through the sales team. One of my key tasks was to set up and maintain a new design system.

</aside>

My Role

<aside> <img src="/icons/briefcase_gray.svg" alt="/icons/briefcase_gray.svg" width="40px" /> My task was to build and maintain the design system and component library. I focused on developing a visual identity that was accessible, scalable and visually appealing. I collaborated with cross-functional teams in an Agile environment. To ensure that the design aligned with business goals and user needs, we reviewed the visual identity against accessibility standards and regulatory requirements.

</aside>

Challenge

<aside> 🤔 **The two main challenges:

Building a design system from scratch:** This was my first time building a design system, and there were no usable pre-existing assets, libraries, or design infrastructure. It was a challenge to create and implement a cohesive design system with no design ecosystem from which to draw.

Delays working with a silos team: We faced delays while working with an external sales team as they were not directly involved with the product. We had to rely on them for user feedback on our demo, but they were not able to provide us with a clear timeline for receiving the feedback from clients. Additionally, their lack of involvement and understanding of the product resulted in misunderstandings and miscommunication, which further delayed the process.

</aside>

Problem

UX Heuristic appraisal: Poor

In Evaluating the VA Web demo, I found that the design was not responsive, with many inconsistencies, bad practices, and poor visual hierarchy.

1.png

Solution

<aside> 🤔 To ensure the best possible user experience, I proactively addressed potential pain points through thorough research and UX audit. I created a cohesive and reusable design foundation by adopting Brad Frost's Atomic Design methodology, which allowed for consistent UI across devices. The design process prioritized accessibility and responsive design, with a comprehensive design system encompassing typography, a colour palette, iconography, UI components, layout grids, and accessibility guidelines.

</aside>


Redesign Before and After

Below is a comparison between the VA Web app before and after our redesign.

VA Chat Screens

VA Chat Screens

VA role management Screens

VA role management Screens


Scope and constraints

The virtual assistant was initially developed with basic functionalities without any user research or design input. The immediate goal was to improve the demo's appearance and functionality, so I focused on identifying design problems in the user interface to provide value in the interim.

Before the user testing session, I collaborated with the Head of Product to identify goals and improve the user interface of Web VA by providing a Heuristic evaluation report. We also brainstormed ideas for new features to enhance the user experience.

<aside> 🧗🏾‍♀️ Unfortunately, we depended on the sales team, an external department, to provide feedback for the demo. It was proving to take a lot of time, and we had no clear idea of when to expect the feedback. Because we didn’t want to be sitting ducks, we used preliminary research to anticipate and address any potential user needs before the first round of user testing began.

</aside>

https://naomi-alao.github.io/notion_widgets/slider2/index.html

🚦Getting the green light

Once we finally received the user research feedback, we were able to concur that the features that we had a head start on were also solutions in line with the pain points and user frustrations later discovered once we received the user feedback from the demo.

<aside> 💡 New Features

data vis.png