Learning experience 03
Illustrative scenario · Meridian is a fictional company
Measure what matters
Imagine Meridian is measuring, and that is the problem. Completion rates sit at 94%. Satisfaction scores average 4.2 out of 5. Leadership considers the knowledge system a success. Meanwhile, new hires still take 14 weeks to become effective and managers still answer the same questions every week.
The system isn't broken. The measurement is. This is how I'd redesign it.
Illustrative scenario · Fictional company
What Meridian tracks before Source. Everything looks healthy. That's the problem.
These metrics measure activity, not behavior. None of them answer the only question that matters: did anyone make a better decision because of this system?
What I'd instrument during a Source rollout: behavior signals, not vanity metrics, tracked weekly across all regions. Illustrative data.
Repeat searches on the same topic is the most diagnostic signal: it shows where the content isn't actually answering the question. In practice, it would drive rounds of content revision during rollout.
Lagging indicators I'd track at 6 months post-launch, shown with illustrative targets. Connecting Source adoption to actual performance change.
The measurement framework would double as a governance tool: the adoption indicators in phase 2 would be reviewed monthly by the L&D and operations teams to catch content gaps before they become performance gaps.
The framework
Activity metrics tell you what happened. Adoption metrics tell you if the system is working. Impact metrics tell you if it mattered. You need all three — in sequence, not simultaneously. Trying to measure impact before adoption is like checking exam scores before anyone studied.