The Report Nobody Reads (Or Understands)

Arlyne Pardo
August 17

A report can be technically available and still fail its purpose, if supervisors don't know where to find it, or find it and don't know what it means. We had both problems tangled together and mistook them for one. Untangling them, and closing each gap with a different fix, is what moved adherence.

“How's your team's performance this week?”

More than once, a supervisor's answer has been some version of, “I'm not sure where that report lives.” Not that the numbers were bad, they'd never opened the file. That's an easy problem to name and think you've solved with a few announcements. What we didn't realize was that fixing access would only reveal the harder problem underneath: supervisors who could find the report often still couldn't read it, not in the sense of literacy, but in knowing what the number in front of them meant.

Arlyne Pardo
August 17

Two Problems Wearing One Complaint 

When a metric doesn't improve, it's tempting to treat it as one issue: “people aren't using the report.” But that complaint can hide two failures that need different fixes. 

Access: the report exists, but supervisors don't know it exists or were never told it was theirs to check. 

Interpretation: the supervisor has the report open, but the number doesn't translate into a diagnosis they can act on. 
We had both, tangled together, which is why fixing “the report problem” with a single lever kept underperforming because it only ever addressed half the gap. 
Closing the Access Gap 

Our report lived in SharePoint: current, accurate and effectively invisible to anyone never shown where to click. Supervisors promoted from the agent role, without a walkthrough of the tools that came with the title, never crossed paths with it. The fix was unglamorous: repeated announcements, a standing agenda item in team meetings and direct links in channels supervisors already used. No new technology, just treating “where is the report” as a real onboarding gap instead of an assumed obvious. 

Closing the Interpretation Gap 

A supervisor can have the report open, see adherence sitting well below target and still miss what's happening. A low number is a symptom, not a diagnosis. Without knowing what's driving it, a system delay, a break violation, an unlogged task, the coaching conversation stops at the surface: “Your number is low, get it up.” That's feedback an agent can't act on. 
 
A glossary of metric definitions helped, but only partway. Knowing what adherence measures tells a supervisor what the number means. It doesn't teach them to ask why this agent, this week, is missing it, a skill closer to diagnosis than definition. The same gap shows up with AHT, occupancy, or shrinkage, anywhere a metric flags that something's off without saying why. 
 
Our Learning and Development team-built courses to close that gap directly: not just what each metric represents, but how to trace a miss to a root cause and turn it into a specific next step for the agent, instead of a generic reminder to “do better.” 

What Moved the Needle 

We ran the announcements, the meetings, the glossary, and the courses close together, and the metric improved once all four were in place. It's tempting to credit the bundle equally, but the honest read is we were solving two problems at once: announcements and meetings closed access; the glossary and courses closed interpretation. Neither pair alone would have been enough. A supervisor who can find the report but can't read it looks engaged without improving anything. One who understands the metrics but can't locate the report never gets the chance to apply it. The improvement showed up only once both gaps closed. 

The Layer We're Still Working On 

Even with the report in hand and the training behind them, some supervisors still won't say, “I don't know what this means” out loud, it can feel like admitting they're not qualified for the role. So, they guess, and a guess dressed up as feedback sends the agent back to being told to “fix” a number nobody explained. 
 
The piece we're still building isn't a document. It's the norm that “I don't know, let's find out together” is an acceptable answer, from a new supervisor and from WFM alike. That comes from WFM and operations working the same numbers together on a recurring basis toward the same goal, not handing a report down and calling it done. 
 
Access, we fixed. Interpretation, we're most of the way there. If your reports aren't driving the behavior you expect, it's worth asking which of these three problems you have, because a report nobody can find and a report nobody can read look identical from the outside, but they don't get solved by the same thing.