Measurement and Operations
Documentation work gets stronger when teams can see the work clearly enough to manage it.
That is where measurement and operations matter. I’m interested in the part of documentation work that helps answer practical questions about visibility, scale, consistency, process health, and where attention is actually needed.
What I mean by measurement
I’m not talking about measurement for its own sake.
I’m talking about practical signals that help a team understand things like:
- what is moving
- what is blocked
- where effort is going
- where patterns are forming
- what needs attention first
- where a process is helping or hurting
Good measurement makes it easier to make decisions with less guessing.
How this has shown up in my work
This has shown up in my work through:
- documentation metrics in Tableau
- automated reporting systems
- Excel-based process support
- visibility into team work and content operations
- documentation planning and prioritization
- support for process improvement through better data
In roles at both Meta and Jack Henry, I’ve worked on the operational side of documentation, not just the authored content.
Why operations matter in documentation
A lot of documentation problems are not really sentence problems.
They are operations problems.
For example:
- content is hard to track
- priorities are unclear
- changes are not visible enough
- the workload is uneven
- teams do not have a reliable view of progress
- useful standards exist but are not supported by the workflow
That is why I care about the operational side of the work.
What I try to improve
When I work in this space, I’m usually trying to improve one or more of these:
- visibility
- consistency
- maintainability
- prioritization
- workflow clarity
- decision support
The point
The point of measurement and operations is not bureaucracy.
The point is to help a documentation team see reality more clearly and work in a way that is easier to sustain.