Omatic Software Writing Standards Guide
This is a company-wide writing standards guide that I developed for Omatic Software. This process involved a thorough review of pre-existing written communications and guidance to identify the general consistencies and standards that the company was already following and that I could build out further. Additionally, I conducted several interviews and consulting sessions with senior stakeholders in the organization to determine voice, tone, and content strategy, as well as solicit feedback. This guide is intended to be used for all writing at Omatic, ranging from marketing to in-product microcopy.

The linked PDF contains a selection from the writing standards guide I developed for Omatic Software; certain sections related to Omatic’s branding and specific UI components have been removed.

View the PDF here.

Omatic Cloud Error Message/System Notification
Omatic Cloud’s Data Queue page displays formulas that users have configured to import records from one system of record to another. These formulas are shown on individual cards that provide details about the formula (e.g., how many records are being processed, how many records are ready for import vs. need further review) and display status notifications in the event that Omatic Cloud encounters a problem when performing an import.

When designing one of these status notifications in Figma, a colleague on the UX Design team at Omatic Software asked for assistance on the language for a system status message in Omatic Cloud. The message would appear if Omatic Cloud could not authenticate access credentials with a data source to import records.

My colleague created a rough draft based on the product manager’s parameters and then flagged it for me to review and revise in Figma, with a note that she wasn’t sure how to best articulate the system status and what kind of further guidance could be helpful for a user to resolve the associated error.

Working directly on the design in Figma, I collaborated with my colleage to produce a clear and effective system status message that met the parameters set by the product manager, who approved the update.

The complete sample and further details are available in the PDF here.

Omatic Cloud User Guide: Formulas
As part of my work at Omatic Software, I was tasked with developing a comprehensive user guide for Omatic Cloud, the company’s flagship product for non-profits to import data from source systems into their systems of record.

To create this user guide, I developed a standardized template for capturing and presenting information and step-by-step processes, I conducted research in the product itself to test my knowledge and the processes I documented, I interviewed numerous product managers, software engineers, and client-facing consultants as subject matter experts (SMEs), and I solicited these SMEs for feedback and approval on the documentation I authored and published for users.

Using ProProfs, I developed more than 40 total articles of user-centered reference information, how-to steps, best practices, and FAQs on topics that covered all of Omatic Cloud’s features.

The sample article below focuses on formulas, which are set of instructions that users create in Omatic Cloud to configure a data integration from their source platform to their destination system.

See the complete sample PDF here.

Omatic Cloud Upgrade: Transformations
Omatic Software was in the process of upgrading a feature for Omatic Cloud’s transformation capability—this is a tool in Omatic Cloud that enables users to modify the data that they import from their source platforms and make the changes they need before the data is exported to the destination.

As part of this upgrade, we needed to create an in-product announcement that highlighted these significant changes for how our uses process their data in Omatic Cloud. I was asked by a product manager to write the content for the announcement and create it in Pendo.

The complete sample and further details are available in the PDF here.