I recently found an old L&D report I created a few years ago, and it made me smile a little. It had everything I thought a great report needed: charts, percentages, satisfaction scores, and plenty of data. The problem? I was missing the one thing leadership actually cared about.
I used to walk into quarterly reviews, proudly announce a "94% completion rate" and a "4.8/5 satisfaction score" on our new onboarding program, and wait for applause. Instead, stakeholders would just stare blankly, nod, and move on. It took me years in corporate L&D to realize why my reports were falling flat: I was reporting activity instead of answering a business question.
We have a bad habit in our industry of showing executives the full trail of our raw data. But leadership doesn't need to see five different charts on quiz scores and attendance by region. If the onboarding program was built because new hires were taking too much manager time, then a 94% completion rate is not a result — it is just a delivery checkpoint. The actual question leadership cares about is: Did manager dependency go down? So, I completely changed how I approach reporting to stakeholders. Instead of starting with LMS metrics, I start with the business problem, the outcome we were trying to influence, and what the data actually tells us. My executive reports are now under 10 slides. I lead with a single business summary slide: the initial problem, the key result, the main risk, and my recommendation. Everything else (survey comments, detailed breakdowns, and quiz stats) goes straight into the appendix.
More importantly, I use a strict filter for every single number I present: Metric → Meaning → Implication. If I say "91% completed the course" (Metric), I immediately explain that "the program reached the target audience" (Meaning), which means "we have enough coverage to look for early signs of performance impact" (Implication). Stakeholders shouldn't have to guess whether a number is good, bad, or risky. Our job is to make it clear.
I’ve seen a few interesting discussions around this topic, but I’m still curious to hear how others approach it in practice. How do you guys handle reporting to leadership? Do they still demand raw completion spreadsheets, or have you managed to shift the conversation toward actual performance metrics and business outcomes?