Most training reporting is built for the person who owns the programme. It aggregates: completion by department, trend over time, comparison against target. That's the right view for someone deciding whether the programme is working.
It's the wrong view for the person who can actually close a gap, which is a team lead looking at four specific people.
The two questions are different
The programme owner asks: how are we doing, is it improving, where are the problem areas.
The manager asks: who on my team hasn't done this, is it a problem, and what do I say to them.
An 82% completion figure answers the first question and none of the second. To act, a manager needs names, what's outstanding, how overdue it is, and whether it's serious enough to interrupt someone over.
Reporting that only aggregates forces every manager to either request a breakdown or ignore it. Most ignore it.
What a manager view should contain
Ordered by how much it affects whether anything happens:
- Their team, by default. Not the organisation with a filter — a manager should see their people without configuring anything.
- Named individuals, not counts. "3 of 8 incomplete" is a prompt to go find out who.
- What's outstanding and how overdue. A module assigned yesterday is not the same as one three weeks past a compliance deadline.
- Where people stopped. If four of five people stalled at the same module, that's a content problem the manager should escalate rather than a discipline problem they should chase.
- Nothing else. Every extra metric reduces the chance the useful part gets read.
Where it stopped is the most underrated field
Most dashboards report completion as binary — done or not done. That hides the diagnostic.
If someone started and stalled at module four, that's a different situation from someone who never opened it. The first suggests module four is too long, unclear, or assumes something; the second suggests the assignment or the delivery didn't reach them.
Those need opposite responses, and a manager can only tell them apart if the data distinguishes them.
It has to be where they already are
A dashboard behind a login that a manager visits when reminded is a dashboard that gets visited when reminded — which is the same problem as the training itself.
The version that works is either pushed to them on a cadence, or available in the tool they already have open. A weekly summary in a channel, or a command that returns their team's status in a few seconds, outperforms a well-designed web dashboard nobody opens.
Don't turn it into a leaderboard
Ranking managers by their team's completion rate produces the behaviour you'd expect: pressure applied at the wrong moments, and eventually people clicking through modules to make the number move.
The goal is closing gaps, not competing on a metric. Give managers their own team's picture and let them handle it. Comparison across teams belongs to the programme owner, not to every manager.
What good looks like
A manager should be able to answer, in under a minute and without preparation: who on my team is behind, on what, by how much, and is anyone stuck at the same place.
If getting that requires a request, an export, or a meeting, the reporting isn't doing its job — and the gaps will close slowly or not at all.
How Poplearn handles it
/progress returns live completion by team directly in Slack, so a manager gets their team's picture without leaving the tool they already work in, and without an account on anything else. It exports on demand when someone needs the underlying record.
Because modules are delivered as Slack direct messages and completed in place, the data is current rather than reconciled — what the manager sees is what happened, not what was last synced.
Add Poplearn to Slack — free under 20 seats, installs in about a minute.
