Knowledge Measurement, Analytics, and Value Realization
This section covers Knowledge Measurement, Analytics, and Value Realization. The exam tests metric selection, baselines, leading and lagging indicators, benefit mapping, and credible ROI.
Core rules
- Start from the business objective and map a chain: inputs, activities, outputs, outcomes, and impact. A knowledge base article is an output, not an outcome.
- Use leading indicators for early signal, such as expert requests routed to a community, and lagging indicators for realized value, such as reduced rework or faster onboarding.
- Establish a baseline before intervention. Without it, improvement claims are anecdotes.
- Combine quantitative and qualitative evidence. Search logs and cycle time show patterns; interviews explain why.
- ROI requires costs, benefits, timing, and assumptions. Present sensitivity ranges rather than false precision. Benefit mapping should name who benefits and when.
- Maturity models can frame progress, but they are diagnostic, not a scoreboard.
Worked example
A lessons-learned program claims success because submissions rose 60%. The reasoning should reject volume as value. A stronger design baselines repeat incident rate and time to find prior lessons, then tracks whether project teams use lessons in gate reviews and whether repeat incidents fall. Submissions remain an activity metric.
Traps
Do not use vanity metrics such as page views alone. Do not claim ROI without baseline and cost data. Do not confuse correlation with attribution. Do not measure everything and report nothing.