For Facebook (Meta), I created original technical support content and video scripts for Oculus for Business. Technical support videos were developed based on the scripts I wrote. In addition, I wrote step-by-step procedures incorporated into the technical support web pages. I also conceived of and worked with an illustrator to create the isometric illustrations incorporated into the web page procedures.

For Fluke Networks, I created original help content for mobile apps. This sample is taken from an app that is used to detect and display Wi-Fi related information on mobile devices. I wrote in-app user interface text. In addition, I wrote and edited related FAQ content.

For Fluke Networks, I created a user guide for a new, proprietary, tablet-based product. The project entailed condensing the 400+ page user guide for a sophisticated enterprise software application into a simplified "quick-start" version for inclusion with the tablet.

For Calient Networks, I created the hardware installation guide for a new optical switch product. Under the guidance of a field technician, I developed step-by-step installation procedures by performing a hands-on installation .

 

For the Automobile Association of America for Northern California, Nevada and Utah (NCNU), I created ten policy and procedure guides for various financial and record processing functions such as payment processing and financial accounting.

The documentation process involved a fast-paced combination of interviewing subject matter experts (SMEs), hands-on use of record management and payment processing software systems and iterative document reviews. I incorporated an active voice to speak directly to the reader about required job tasks along with step-by-step procedures about how to perform each task.

For Fluke Networks, I implemented several advanced features of Adobe Robohelp to create a "single source" authoring and publishing platform for technical documentation.

By utilizing the conditional text and variable features of Robohelp, I created express, pro and branded OEM versions of documentation.

In addition, for each version, I created both PDF and Microsoft HTML Help (CHM) publishing formats.

Creating a topic-based, single source publishing platform considerably reduced content development and review cycle time. It also enabled marketing with much stronger opportunities for cost-effective OEM branding variation throughout the content.