Knowledge Sharing Starter Kit

Welcome — why this kit matters

Teams lose time and create risk when useful knowledge stays in heads or chat threads. This starter kit helps you capture practical know‑how, record decisions so they can be reused, and keep information fresh and discoverable without heavy process overhead. Use it as a simple, adaptable foundation you can tailor to your team, project, or site.

What’s included

• How‑to Doc Template — concise, action‑oriented document template for procedures, troubleshooting steps, runbooks, and onboarding notes.
• Canonical Decisions Checklist — checklist and decision‑record template to make important choices durable and traceable.
• Knowledge Inventory Spreadsheet Template — a simple inventory to find gaps, owners, and freshness status across content items.
• Lightweight Governance — roles, review cadence, and freshness rules to keep the collection reliable and reduce single‑point dependencies.
• Channel & Naming Guidelines — where to publish, how to title and tag items so they are findable across tools.
• Quick‑Start Rollout Checklist — practical steps to pilot, measure, and expand your knowledge sharing practice.

How‑to Doc Template (use this for procedures & guides)

Structure your how‑to documents so a reader can accomplish a task quickly. Keep each document focused on a single outcome.

1. Title — outcome phrased as a task (e.g., "Publish monthly operations report").
2. Why it matters — one short sentence linking to outcomes or customers.
3. Prerequisites — accounts, permissions, data, or assumptions.
4. Step‑by‑step — numbered actions with expected results and screenshots or links where helpful.
5. Common failure modes — quick checks and fixes.
6. Related resources — links to data definitions, systems, or decision records.
7. Owner & last reviewed — person, role, and date.

Canonical Decisions Checklist

Use this when a decision affects process, policy, or architecture. Recording decisions prevents repeated deliberation and clarifies accountability.

• Decision Title
• Date
• Decision Makers — names and roles
• Context — brief problem statement and constraints
• Options considered — short pros/cons
• Selected option & rationale
• Impacted owners — who must act
• Review or sunset — when to reexamine or retire

Knowledge Inventory Spreadsheet (columns & how to use it)

Keep a simple inventory as a map to what exists and where gaps are.

• Item ID — short stable handle
• Title
• Type — how‑to, decision, FAQ, dataset, SOP
• Location / Link
• Owner (person / role)
• Last updated
• Freshness status — OK / Review soon / Stale
• Audience — team(s) or roles who rely on it
• Notes / actions — edits needed, backlog priority

Use sorting and filters to surface stale items, ownerless content, and high‑value docs without owners.

Lightweight governance — roles & cadence

Design governance to reduce friction while ensuring accountability.

• Content Owner — responsible for accuracy and a scheduled review (often a role rather than a person).
• Knowledge Steward — a rotating or shared role that helps coordinate reviews and triage inventory items.
• Review cadence — set review frequencies by item criticality (e.g., high‑risk docs every 3 months, procedures every 6–12 months).
• Freshness signals — last updated date, automated reminders, and a simple status flag (OK / Review / Archive).
• Ownership fallback — if an owner leaves or is unavailable, assign an interim owner within 2 weeks to prevent orphaning.

Channels, naming, and discoverability rules

Consistent placement and names make search work:

• Publish in a stable place (team knowledge hub, shared drive, or THE collection) — avoid siloing in chat.
• Title pattern: [Team] — [Task] — [Outcome] (e.g., "Ops — Deploy rollback procedure").
• Use a few standardized tags: team, system, process, decision, how‑to, onboarding.
• Link decisions from how‑tos and vice versa so context is obvious.

Quick‑start rollout checklist

1. Pick a pilot team and one problem area (onboarding, incident response, or monthly ops).
2. Run a 1‑hour capture session to populate 3–5 how‑tos and 2 decisions into the inventory.
3. Assign owners and set review dates in the spreadsheet.
4. Publish items to the chosen channel with tags and links.
5. Measure: track number of items, percent with owners, and percent reviewed in last 12 months.
6. Iterate: collect feedback after 30 days and refine templates or cadence.

Practical KPIs and signals

• Percent of critical processes with a how‑to and owner.
• Number of orphaned documents (no owner).
• Average age since last review.
• User feedback: helpfulness rating or quick thumbs up/down on docs.

Tips to avoid tribal knowledge

• Capture decisions and troubleshooting steps immediately after events while memories are fresh.
• Encourage brief, practical notes — long manuals that never get read are less helpful than short, tested how‑tos.
• Use the inventory to surface people with unique knowledge and prioritize documenting those areas.

Next steps & tailoring

This kit is intentionally lightweight. After piloting, teams often add:

• Structured templates for technical runbooks or safety procedures tied to compliance needs.
• Short interactive forms to collect new knowledge and store responses automatically.
• Dashboards that surface stale items and ownership gaps.

Use the included templates as a starting point and adapt naming, cadence, and channels to local practice and tools.