The Knowledge Steward Role

The knowledge steward is the linchpin of knowledge governance. In a federated model, every domain area has a steward: the person accountable for the quality, accuracy, and maintenance of knowledge within their domain. The steward is not the person who writes all the content — they are the person who ensures the content stays accurate and is maintained by the right people.

Most knowledge base failures can be traced to the absence of a clear steward. Content becomes stale because no one is accountable for reviewing it. Gaps persist because no one owns the responsibility to fill them. Contradictions go unresolved because no one has the authority to make the call.

1. What the Knowledge Steward Does Runs the quarterly review cycle for their domain: identifies stale content, assigns review to subject matter experts, follows up on overdue reviews. Approves new content before publication within their domain. Resolves content conflicts — when two items contradict, the steward makes the call on which is authoritative. Identifies knowledge gaps from user feedback and tickets. Coordinates with the central knowledge function on taxonomy changes and cross-domain items.
2. What the Knowledge Steward Does Not Do The steward does not write all the content. That is the centralized model. The steward does not make unilateral decisions on content that spans multiple domains. The steward does not set platform standards — that is the central knowledge function. Critically: the steward does not police every edit in real time. The steward sets the cadence and holds the quarterly accountability; contributors maintain content day-to-day. Conflating steward with gatekeeper creates a bottleneck.
3. How to Staff It The steward must have sufficient domain expertise to evaluate content accuracy. A steward who cannot tell whether a runbook is technically correct cannot perform the accountability function. This means stewards are senior domain contributors, not knowledge management professionals. The best profile: a senior contributor who cares about knowledge quality and can dedicate 3–5 hours per week to stewardship activities. Never a full-time role except in the central knowledge function.
4. Steward Succession When a steward leaves, their domain becomes ungoverned unless there is a named successor or a succession process. The central knowledge function should maintain a steward registry with each domain, the current steward, and the designated successor. Succession is the most commonly neglected governance task — until a key person leaves and six months of governance gaps accumulate in their domain before anyone notices.

# Knowledge steward registry
domains:
  - domain: "Infrastructure & DevOps"
    steward: "alex.chen"
    successor: "jamie.park"
    content_count: 147
    last_audit: "2026-01-15"
    next_review_due: "2026-04-15"
    governance_health: "green"
    notes: "Strong cadence. Quarterly reviews completed on time."

  - domain: "Sales Process"
    steward: "riley.morgan"
    successor: null     # <-- RISK: no successor designated
    content_count: 89
    last_audit: "2025-11-20"
    next_review_due: "2026-02-20"  # <-- OVERDUE
    governance_health: "yellow"
    notes: "Review cycle slipped. Riley on leave. No successor. Escalate to knowledge admin."

  - domain: "Compliance & Legal"
    steward: "sam.torres"
    successor: "dana.kim"
    content_count: 64
    last_audit: "2026-02-01"
    next_review_due: "2026-05-01"
    governance_health: "green"
    notes: "High accuracy requirements. All content reviewed by legal before publish."

  - domain: "Client Success"
    steward: null       # <-- CRITICAL: ungoverned domain
    successor: null
    content_count: 112
    last_audit: "2025-09-10"
    next_review_due: "2025-12-10"  # <-- 3 MONTHS OVERDUE
    governance_health: "red"
    notes: "Previous steward left. Domain ungoverned for 4 months. Priority: assign steward."