Knowledge Manager Weekly Operating Checklist

Weekly Operating Checklist — Knowledge Managers

Purpose: A concise, repeatable routine to keep your knowledge repositories healthy and discoverable. Designed to be adaptable: use this as a baseline, shorten or expand items to match your team's size and workflow.

Cadence and timebox

Estimated time: 1–3 hours per week for a single knowledge manager. If you manage many collections, focus on a rotating sample each week (e.g., by collection, product area, or owner cohort).

Priority checklist (actionable steps)

1. Review content flagged for update (staleness & feedback)
   • Open the "flagged for update" queue. For each item: verify the current owner, last-updated date, and whether the flag includes suggested changes.
   • Decide one of: quick update (minor fix you can do in 10–20 minutes), owner review (assign to content owner with a due date), or archive (if obsolete).
   • Record the decision and next action in your tracker (ticket, content record, or the platform submission form).
2. Process discovery requests and intake
   • Triaging: categorize request as Search fix, New content, Update, or Metadata/tagging. Assign priority (P1–P3) based on customer impact and frequency.
   • SLA guideline: acknowledge within 2 business days; target resolution or owner-assignment within 10 business days for routine requests unless escalation is needed.
   • Log request status (New, Acknowledged, In Progress, Waiting on SME, Done).
3. Run search-quality quick checks
   • Choose 8–12 representative search queries: top 5 from analytics plus 3–7 random or known problem terms.
   • For each query: scan the first page of results for relevance, broken links, outdated content, and missing canonical answers.
   • Record any zero-result queries, poor-ranking authoritative content, or high-click, low-satisfaction items for follow-up.
4. Sync with analytics on top search queries and usage signals
   • Review the top 20 search terms for the last week: note trends, new product names, or emerging issues.
   • Flag terms with high volume + low click-through or high zero-results for prioritization.
5. Triage experiment and change documentation
   • Check recent experiments (A/B tests, content experiments, UI changes) that affect search, navigation, or recommended content.
   • Verify experiment documentation is stored with dates, owners, and rollback criteria. Ensure experiment learnings are captured in a short summary and linked to affected content.
6. Escalate taxonomy or metadata proposals
   • Review new taxonomy proposals or recurring classification requests. Group similar proposals and escalate to the taxonomy owner or steering group with examples and recommended actions.
7. Update and validate the owner roster
   • Confirm each content item in your weekly sample has a current owner and contact. If owner is uncertain, assign a temporary steward and create an owner-confirmation task.
   • Note any overloaded owners and consider rebalancing ownership or creating shared stewardship patterns.
8. Quick hygiene and links check
   • Spot-check 10 items for broken links, embedded images, and clear version indicators. Fix trivial issues immediately; create tickets for larger work.

Suggested lightweight metrics (keep it meaningful and local)

• Staleness rate = percentage of items in a collection not updated in the last N months (N typically 12). Use this to focus review cycles rather than as a binary health pass/fail.
• Request response SLA = % of discovery requests acknowledged within the chosen SLA window (e.g., 2 business days).
• Zero-result rate = fraction of queries returning no results (weekly, by product area).
• Top-query coverage = % of top 20 queries with at least one high-quality answer on page 1.
• Owner coverage = % of content items with confirmed owners.
• Measure trends weekly or monthly. Avoid measuring checklist completion alone — prefer outcome signals (search quality, request resolution, owner coverage).

Sample dashboard layout (compact)

1. Staleness rate (by collection) — small chart + counts
2. Top 10 search queries — volume & zero-result markers
3. Open discovery requests — status & age (SLA flags)
4. Owner coverage — % with owners, recent confirmations
5. Recent fixes and experiment summaries — short log

Templates and short examples

Owner confirmation note (one-line):

Hi [Name], can you confirm you’re the owner for [Content Item Link]? Please update or confirm a review date within 10 business days. Thanks — Knowledge Team

Triaging shorthand (use labels/tags):

• P1 — Search-critical (customer-facing, high-volume)
• P2 — Content update required (moderate impact)
• P3 — Low-impact / scheduling ok

How to avoid checkbox-driven bureaucracy (governance reminders)

• Measure outcomes, not just task completion. For example, pair "staleness rate reduced" with improved search click-through or reduced zero-results.
• Keep the checklist adaptable: teams should be able to drop or modify items to match local ways of working.
• Use short notes on each checklist item explaining tradeoffs. When you mark something "done," record what changed and why.

When to escalate

• Persistent zero-results for high-volume queries despite content updates.
• Owner cannot be identified for critical content after two attempts.
• Repeated failed experiments or evidence of search indexing problems.

Practical next steps (first 30 days using this checklist)

1. Run the checklist weekly for 4 consecutive weeks on a representative sample to baseline staleness, owner coverage, and request backlog.
2. Create or adapt the dashboard to show the suggested widgets.
3. Adjust SLAs and triage categories to reflect stakeholder expectations.

Notes: Keep language local (use your org’s naming for collections, owners, or roles). Treat this checklist as an operational pattern you iterate on, not a rigid policy.