Much of the writing I have done is, of course, proprietary information. Thus, I have only included samples that highlight core attributes of a technical writer and business analyst:
1. The ability to craft detailed instructions.
2. The ability to gather requirements and assess a situation by interviewing/questioning subject matter experts, project and program managers, and relevant clients and end-users.
3. The ability to detail technical, complex information to a clearly defined end-user.
Other related documents that overlap with technical writing, such as scope of work and contracts, the latter which can be found on the Professional page.
API Documentation, Diagrams, and Stakeholder Engagement (Slides)
The following images contain references to API documentation work (with code), RACI charts, and process flows created for Zensar Technologies and other clients.
(01) Implementation Emergency Communication Plan
Client: State of North Carolina
Document Type: Internal Communication Procedures
Context
When working for the State of North Carolina, a project can shift with any sudden change in politics. I was tasked with creating an Emergency Communication Plan so Executive Management can swiftly disseminate internal and county-facing news
(02) NC FAST User Guide
Client: State of North Carolina
Document Type: User Training (Internal and External audiences)
This document was written for NC FAST Help users in North Carolina. I actually had an old coworker who worked at a county office who would tell me of her struggles navigating NC FAST Help. It reminds me of the importance user guides.
(03) Interview Framework
Client: State of North Carolina Document Type: Qualitative Research; Process document (Executive Management audiences)
As I was assisting with the standards guide, I felt it necessary to audit my teams’ writing and content development processes. My experience as a Writing Center Coordinator at the University of Mount Olive readily informed my decisions, and my intuition for this need was spot on: eventually, all the content developers were laid off due to budget cuts. My experience in business and communication consulting and investigative interviewing has become an oft-used skill.
Note: Identifiable information has been redacted
(04) Intake Process FAQs
Client: Zensar Technologies
Document Type: FAQ
Context
I automated the Change Management Intake Process for Zensar’s end-client back in 2023 in PowerAutomate. As a Change Leader, I maintained the automated intake flow as part of my responsibilities.
To fill the knowledge gap with my other colleagues, I created an FAQ detailing how the flow works and how to use the environment components/connections to address common problems that arise during the intake process.
(05) Intake Process FAQs
Client: Zensar Technologies
Document Type: How-to-Documents
Context
I automated the Change Management Intake Process for Zensar’s end-client back in 2023 in PowerAutomate. As a Change Leader, I maintained the automated intake flow as part of my responsibilities.
To fill the knowledge gap with my other colleagues, I created a document instructing how to install the flow in PowerAutomate and reestablish the connections.