Knowledge curation checklist: taxonomy, tagging, and lifecycle

Purpose

This checklist helps teams make critical knowledge easy to find and keep it current. Use it to design taxonomy and metadata, assign clear owners, instrument search and usage, and create a reliable lifecycle so search returns relevance instead of noise.

Before you begin

Identify the primary audience and one or two concrete use cases you want search to reliably support (for example: "new hire onboarding: locate environment setup steps" or "machine troubleshooting: find root-cause logs and SOPs"). Narrow use cases keep taxonomy practical.

1. Define audience and use cases
   • Action: List top 3 user roles and 3 most frequent questions each role needs to answer with knowledge artifacts.
   • Acceptance criteria: Each use case has a short success test (e.g., a person in Role X finds the required doc in under 5 minutes using a typical query).
   • Example: Role = Field Technician; Use case = "find valve calibration procedure for Model A".
2. Choose taxonomy and core tags
   • Action: Select a small core taxonomy (3–6 high-level categories) and 8–12 repeatable metadata tags (e.g., product, process, location, system, risk level, customer, document type, owner).
   • Acceptance criteria: Every existing critical artifact can be assigned at least one category and 2–3 tags from the core set without forcing new ad-hoc tags.
   • Starter tag examples: product:Model-A, doc-type:SOP, audience:technician, lifecycle:draft|published|retired, location:Plant-1.
3. Create content templates and metadata rules
   • Action: Provide at least two templates (how-to/SOP and troubleshooting incident report) with required metadata fields and example values.
   • Acceptance criteria: New content cannot be published without filling required metadata fields; templates are stored in a visible library and linked from the authoring page.
   • Example required fields: Title, Summary (one-sentence), Category, Tags, Owner, Date Published, Related Assets, Version, Review Date.
4. Assign owners and review cadence
   • Action: For each category, designate an owner (person or role) and set a review cadence (quarterly, biannual, annual) based on risk and change rate.
   • Acceptance criteria: Every published artifact lists an owner and next review date; owners receive an automated reminder 30 days before review is due (or a manual owner log is kept if automation isn't available).
   • Guidance: High-risk or frequently changing docs → review quarterly. Stable reference docs → review annually.
5. Instrument usage metrics and feedback loop
   • Action: Track at minimum: document views, search queries that return the doc, time-to-first-click, and explicit feedback (useful/not useful). Log duplication incidents discovered during searches or audits.
   • Acceptance criteria: Monthly dashboard shows top 20 documents by views, top failed queries (no good results), search-to-success rate, and a list of documents flagged for duplication or update.
   • Suggested metrics: Search success rate (target > 70% for primary use cases), average time-to-find, number of duplicate artifacts eliminated per quarter.
6. Operate a lightweight curation workflow
   • Action: Define a simple state model for artifacts (Draft → Published → Under Review → Retired) and a short workflow for edits and approvals.
   • Acceptance criteria: Changes to Published artifacts are versioned; an approval or owner sign-off is required before major edits go live.
   • Tip: Use a "quick fix" tag for small clarifications that the owner can approve in 48 hours without full review.
7. Run a quarterly search quality check
   • Action: Test 10 real queries from users and evaluate results for relevance. Note false positives (noise) and false negatives (missing docs).
   • Acceptance criteria: For tested queries, at least 8 of 10 return an immediately useful result; issues feed into a tuning backlog with owners and due dates.
8. Educate authors and users
   • Action: Publish a one-page guide showing how to write good titles, tag content, and pick categories. Run a 30-minute demo for each team that creates content.
   • Acceptance criteria: New authors complete the demo and use templates for their first two published items; a short survey shows increased confidence in tagging.
9. Prune and archive
   • Action: Identify low-use or outdated artifacts and either archive, consolidate, or retire them. Keep an archive log linking retired items to their replacements when applicable.
   • Acceptance criteria: Each quarter at least 3 low-value duplicates or obsolete docs are archived or consolidated; search results do not surface retired docs by default.

Quick implementation checklist

• Create core taxonomy and tag list (document in one page).
• Publish two templates (SOP and Troubleshooting) and required metadata rules.
• Assign owners and initial review dates for critical categories.
• Instrument basic metrics and create a monthly dashboard view.
• Schedule the first quarterly search quality check and author demo.

Suggested tags & examples

product, process, doc-type (SOP/HowTo/Report), audience (operator/engineer/manager), location, system, severity/risk, owner, lifecycle

Next steps & templates

Start small: pick one team, implement the checklist, measure search success for two months, then iterate taxonomy and cadence based on real usage data. Provide links or attachments to templates and an owner roster if available.

Connection to the hunger

This checklist turns the hunger "Make it easy to find the right knowledge at the right time" into concrete actions that reduce duplicated work, lower onboarding time, and improve operational consistency.