Content governance that outlives its author
Documentation keeps working only as long as someone remembers how it's supposed to work. Governance is writing that part down too — standards, roles, and workflows that don't depend on their author staying in the room.
§1 The situation
A collaborative help-center environment where contributors and subject-matter experts write customer-facing guidance. Without shared standards, that kind of system degrades predictably: each article answers to its author's habits, metadata drifts, permissions blur, and review happens when somebody remembers. The guidance was load-bearing for customers, so the process behind it needed to be load-bearing too.
§2 What I did
Authored the documentation style and publishing standards, and established the operational machinery around them: content models, metadata, permissions, and intake, review, QA, and publication workflows. Every piece served the same purpose — make the path from draft to published guidance explicit enough that contributors could follow it without asking.
§3 Result
Contributors and subject-matter experts had a more consistent, reviewable process for creating and maintaining customer-facing guidance. Operational standards made customer information easier to maintain, review, and trust — without depending on unwritten knowledge.
§4 Difficulty & judgment
Governance work balances on a narrow ledge: too loose and consistency evaporates; too rigid and contributors route around the process, which is worse. The standards had to preserve contributor ownership and speed while still buying consistency, accessibility, release readiness, and a clear source of truth. A process outlives its author only if the people inside it actually want to use it.
§5 Not claimed
Deliberately left unclaimed
- Sole creation of the help-center platform or its content — contributors and subject-matter experts wrote the guidance; this plate claims the standards and workflows they worked in.
- A team of direct reports — collaborators on this work were exactly that: collaborators.
- A precise role chronology — exact role-boundary dates are still being reconciled against sources, so this plate stays at the year.
§6 The same work, other lenses
- Knowledge & training
- Usable standards that helped subject-matter experts create consistent, supportable customer guidance.
- Operations leadership
- A standardized path for moving contributor work from intake through review, QA, and publication.
- Governance
- Ownership, review, metadata, permissions, and publishing boundaries made explicit, so assisted content work stayed reviewable.