|
I build and organize knowledge so people can find, trust, maintain, and use it. That means turning scattered documents, SME input, process notes, system details, and operational knowledge into structured content that supports real work.
|
|
I analyze existing documentation to identify gaps, duplication, outdated material, inconsistent terminology, missing ownership, and content that no longer matches the current process or system behavior.
|
|
I develop knowledge-management content including FAQs, knowledge articles, process documentation, service desk references, operational procedures, training-support materials, and searchable support content.
|
|
I create content structures that support findability and reuse, including categories, metadata, naming conventions, cross-references, glossary terms, role-based organization, and consistent page or article patterns.
|
|
I support documentation governance through review cycles, version control, stakeholder feedback, content ownership, release-aligned updates, and practical standards that help keep information from becoming stale.
|
|
I understand that knowledge management is not just a repository. A repository only helps if the information is accurate, organized, searchable, maintained, and aligned with the way teams actually work.
|
|
I help preserve institutional knowledge by capturing what is often stuck in meetings, emails, spreadsheets, legacy documents, and people’s heads, then turning it into content that can be reused, trained, searched, and sustained.
|