Content Strategy

My content strategy experience breaks down like this:

  • Technical Writing
  • UX Content Strategy
  • Creating infrastructure: information architecture, building documentation publication systems, and building teams

Technical Writing

  •  Expert in planning, writing, and publishing all types of documentation (manuals, web pages, release notes, software bugs, API docs) from conception to completion in all formats in line with changing business goals through acquisitions and churn.
  • Creating processes, implementing tools, and generally optimizing a user’s experience with product documentation.
  • Experienced in implementing cutting-edge tools and technologies for technical writing, including machine learning, topic-based authoring, Markdown, XML authoring, DITA, and DocBook in various source-control/CCMS systems.
  • Publishing documentation in multiple formats (HTML, CHM, PDF, print) using multiple tools (Oxygen, Vasont, Adobe Framemaker, Arbortext Epic, Clearcase, Astoria, XMetal, Microsoft, etc.) and formats (Markdown, DITA, DocBook, and XML)

UX Content Strategy

  • Product managed on-boarding tour tool at Adobe.
  • Created and implemented multiple on-boarding tours for UX at various stages in the engineering lifecycle (Agile and waterfall). Worked on automating chatbots, on-boarding tours, and in-app help and populating it with content pulled from product documentation.
  • Contributed to countless UI and UX designs including button names, tool tips, and error messages throughout my entire career.

Creating Infrastructure

  • Expert in building high-quality, efficient, balanced teams and processes, delegating responsibilities, managing, and growing writers.
  • Designed two help systems for startups and integrated into an additional three. Created and maintained the style guides, processes, automation, and publishing systems around them, including designing the pipeline, choosing authoring tools, page and article size, depth and design, back-end information architecture, github repo structure and branching strategy, integration of analytics tools, and publication output. All considering the optimal user experience, writer efficiency, scalability, localization, and future contribution.