Skip to main content

Documentation Operations

Summary​

Good documentation depends on more than good writing.

It also depends on planning, visibility, consistency, workflow, reporting, editorial judgment, and the systems that support the work over time. Documentation operations is the part of the job that helps all of that hold together.

This has been a recurring part of my career, especially in roles that involved documentation leadership, cross-functional coordination, analytics, and large or evolving content environments.

The problem​

Documentation gets harder to sustain when the surrounding system is weak.

That can show up as:

  • unclear ownership
  • uneven quality
  • poor visibility into work
  • inconsistent structure
  • weak reporting
  • too much manual tracking
  • difficulty scaling across many products or teams
  • friction between documentation needs and product timelines

At that point, improving the writing alone is not enough. The operating model around the writing also needs work.

What documentation operations includes​

For me, documentation operations includes work like:

  • improving how documentation gets planned and tracked
  • supporting consistency across writers, teams, or product areas
  • using analytics and reporting to improve visibility
  • helping define realistic workflows
  • improving content systems and maintenance patterns
  • connecting documentation work more clearly to product and organizational needs

It is the part of documentation work that helps teams move from reactive content production to something more sustainable and better understood.

How this has shown up in my work​

This kind of work has been part of multiple roles in my career.

At Meta, my public role history includes work as both a Documentation Manager and a Documentation Engineer. That work has included supporting documentation across large product sets, collaborating with cross-functional teams, implementing documentation metrics in Tableau, using Excel to streamline processes and manage large data sets, and helping shape documentation strategy.

At Jack Henry, this work included managing documentation teams, delivering help content across many products, building automated documentation analytics with Tableau and SharePoint, onboarding acquired products into existing documentation practices, and helping improve how teams coordinated around documentation work.

Across those roles, the pattern is consistent: build clearer systems around the content so the content itself can work better.

What I pay attention to​

When I work on documentation operations, I usually care about questions like:

  • Can the team see the work clearly?
  • Are priorities understandable?
  • Is the reporting useful?
  • Where is the friction?
  • What is inconsistent?
  • What should be standardized?
  • What is too manual?
  • What will help the work scale without getting sloppier?

Those questions usually reveal whether the documentation system is helping or hurting.

Why this matters​

Documentation operations matters because good content does not survive very well inside a bad system.

Writers can be talented and still struggle if the surrounding workflow is unclear, the visibility is poor, the structure is inconsistent, or the process creates unnecessary friction.

Improving documentation operations helps create:

  • better visibility
  • better consistency
  • better decision support
  • better maintainability
  • better conditions for good documentation work

What this shows about my work​

This is a strong example of the broader way I work:

  • I care about systems, not just pages
  • I like making the work easier to see and easier to manage
  • I use analytics and structure to support better decisions
  • I think documentation quality depends partly on the operating model around it
  • I’m comfortable working where writing, process, tools, and organizational needs intersect