While working as a UX writer and designer at Omatic Software, I participated in efforts to make continuous improvements to our flagship product, Omatic Cloud. As a part of making these continuous improvements, my team was in charge of implementing upgrades to Omatic Cloud’s “transformation” function.

Transformation is a frequently used feature, and Omatic Software’s product management had received significant feedback from users about what kinds of improvements they would like to see in the product. Most notably, in the previous version of Omatic Cloud, transformations were three separated features that users wanted condensed into a single function.

As the UX design lead for the team, I was tasked with creating a design that combined all three separate transformation functions into a single, streamlined feature, updating pre-existing transformations to make them more user-friendly and intuitive, and creating new transformations from scratch that aligned with the design strategy used for Omatic Cloud.

You can review the full brief and case study with screenshots, process explanations, design iterations, and notes in the PDF linked here.

While working as a UX writer and designer at Omatic Software, I participated in efforts to make continuous improvements to our flagship product, Omatic Cloud. As a part of making these continuous improvements, my team was in charge of implementing upgrades to Omatic Cloud’s “record match search” function.

Record match search is an integral part of record processing in Omatic Cloud, and Omatic Software’s product management had received significant feedback from users about what kinds of improvements they would like to see in the product. Most notably, in the previous version of Omatic Cloud, users noted that search scenarios were returning too many results for them to review, and they wanted to make Omatic Cloud more efficient to save time when searching for matching records.

To solve this problem and jumpstart the design, I worked with a fellow UX designer and the rest of my team to complete a design sprint, which gave us ideas on what kinds of methods we could implement to make the user experience more efficient. Following the design sprint, I took the lead on designing a new “advanced matching settings” concept that would enable users to prioritize search scenarios and reduce the number of data returned from the record match search.

You can review the full brief, process, and design samples in the PDF here.

As part of my UX design work at Omatic Software, a colleague and I developed a vision-type for an upgrade to Omatic's flagship product, Omatic Cloud.

In the current version of the product, users need to manually configure integrations to transfer data from a source to their organization's system of record. This configuration includes selecting the fields that are used in the source and destination platforms, setting the criteria for cross-referencing matching records, creating directions for how to route the data, and then reviewing the data when it has been processed.

In the vision-type that my colleague and I created, we designed what the user experience would look like if we incorporated an AI into the software that would perform all those manual tasks for the user, interact with the user to confirm those tasks, prompt the user to make key decisions, and provide helpful documentation along the way. We created the designs for a chatbot and developed a clickable prototype in Figma, which we demoed to our company's key stakeholders (to highly positive feedback).

You can view the demo video of a part of the prototype here.

When I started pursuing UX Design and UX Writing for career options, I began by taking an accelerated UX bootcamp through BrainStation. Over the course of 10 weeks, I and other students learned from UX industry experts about the basics of UX design and the process that designers follow, from initial discovery to design to testing to revision to presentation. As part of this bootcamp, we learned about the different deliverables created through the UX design process, including personas, wireframes, prototypes, user interview and testing scripts, and information architecture schemas.

To put all of our learning into practice and complete the bootcamp, every student was required to develop a prototype for an application (either mobile or web-based). The app could be something entirely new or a re-imagining of a pre-existing product. For my project, I chose to develop a recipe app called ReciParty.

You can review the entire case study for how I developed this prototype app in the presentation here.