Brief: knowledge-management
Research brief for knowledge-management · how it was made.
Research brief — knowledge-management
| Field | Value |
|---|---|
| Slug | knowledge-management |
Primary query / seo_intent | Team Knowledge Scorecard and Fixes for Repeat Questions |
| Template (A–E) | A |
| Evidence tier (1–3) | 2 (personal/team question scorecard) + APQC Knowledge Flow Process |
| Audience (one line) | Team leads and ICs drowning in wikis and tools - blunt ops voice, not enterprise-KM vendor MBA |
| Public byline | 8020.in Editorial |
| Reviewer | Practitioner / ops pass |
| Date | 2026-07-20 |
1. Concentration claim (one sentence)
In knowledge management, most useful reuse concentrates in a few habits you can name - which questions keep repeating, which answers get written once in a trusted place, who maintains them, and whether people can find and use them in the flow of work - while equal energy on documenting everything and buying another tool expands into busyness without moving the scoreboard.
Differentiation
| Piece | Job |
|---|---|
research / critical-thinking | Finding and judging claims |
productivity / time-management | Personal shipped-work focus |
knowledge-management | Capture/find/reuse concentration for teams and working individuals |
Cross-link; do not ship a full wiki OS or tool catalog.
2. Hard anchors (2–5)
- APQC Knowledge Flow Process — Seven-step cycle: create, identify, collect, review, share, access, use; identify critical knowledge to focus effort; use is the point of the flow. https://www.apqc.org/resource-library/resource-listing/apqcs-knowledge-flow-process-framework · https://www.apqc.org/blog/managing-knowledge-starts-knowledge-flow
- APQC four components — People, process, content/IT, strategy (context that tools alone are not KM). https://www.apqc.org/blog/what-are-best-four-components-knowledge-management
- Question→doc scorecard — team/personal measurement (never invent universal “20% of docs = 80% of answers”).
2b. Field 80/20 examples
| Approx % claim | Field / context | Source | Where |
|---|---|---|---|
| Identify critical knowledge before collecting everything | KM process | APQC Identify step | Audit focus |
| Flow ends in use (solve/decide), not in storage | KM process | APQC Use step | Outcome lever |
| Illustrative: top recurring questions = most ask-time | Team scorecard | Illustrative | Audit |
Never invent “20% of employees hold 80% of knowledge” as a measured universal law.
3. Original observation (only-on-8020 seed)
KM concentration scorecard (2 weeks): for each repeated question or search fail - topic; ask channel (chat/meeting/ticket); doc existed? (Y/N/stale); kept outcome (reused / rewrote / asked-again / none). Protect topics with high ask-again; write one source of truth; starve wiki gardening of unused pages.
4. Ignored majority (named)
Documenting everything; empty tool migrations; orphan pages with no owner; search theater; experts answering forever in chat with no capture; measuring KM by page count.
5. Composite policy
| Scenario | Keep as Illustrative? |
|---|---|
| Two-week question log sample | Yes |
6. Vital few (draft)
- Recurring-question inventory
- One source of truth per top topic
- Named maintainer + review
- Findability from where people already ask
- Use/feedback loop (APQC “use”)
7. Device budget
≤3 example/move pairs; scorecard; viz: none; no hero
8. SEO / links
- Internal:
/research,/critical-thinking,/productivity,/time-management,/decision-making - Outbound: APQC knowledge flow framework + blog; four components blog
9. Common-sense gate
- Opens in team/ops language, not Pareto lecture
- Not Step 1/2/3 tip stack; invent no expert-Pareto laws
- Bold lead-ins;
-; link attrs