|
I develop structured technical documentation for enterprise systems where the source material is complex, scattered, or still evolving. My work is to understand the system, clarify the workflow, and turn that information into documentation people can actually use.
|
|
I create user guides, operational procedures, system documentation, workflow references, API-support materials, configuration notes, release documentation, and knowledge-base content that support implementation, training, support, and long-term maintenance.
|
|
I translate SME input, system behavior, stakeholder requirements, and implementation details into clear documentation for business users, technical teams, trainers, service desk teams, project managers, vendors, and leadership stakeholders.
|
|
I am comfortable working in the space between business and technology. I ask enough questions to understand what the system does, why the process matters, where users struggle, and what documentation is needed to make the work understandable and repeatable.
|
|
I organize technical content into practical structures, including procedures, process flows, data dictionaries, field definitions, crosswalks, FAQs, job aids, support references, and role-based documentation.
|
|
I maintain documentation through review cycles, release changes, stakeholder feedback, version updates, and evolving operational requirements. The goal is not just to produce a document, but to keep the content accurate, useful, and trusted.
|