You’re looking at a usage dashboard for a tool you championed, and the number is smaller than you’d like to say out loud. Before anything else: that number is not a verdict on your people, your judgment, or the case you made to buy it. It’s information — and once you know how to read it, it points somewhere useful.
Here’s the short version, in one sentence you can take to your next meeting:
Low adoption is almost never a people problem. It’s a placement problem — the learning got put somewhere your people don’t actually work.
The rest of this piece is about how to read that signal, run a quick diagnostic on your own system, and pick the two or three moves that will actually move the number — without bribing anyone, badgering anyone, or starting another rollout campaign you’ll have to defend later.
What the number is not telling you
Three readings to set aside before we go further. Each one is tempting, each one is wrong, and each one keeps you stuck.
It’s not telling you your people don’t care about growth. They almost certainly do. You can see it in the hallway conversations, the Slack threads, the way someone pulls a teammate aside to walk them through a tricky account. Curiosity is not the bottleneck.
It’s not telling you that you bought the wrong tool. You probably bought a reasonable one. Most modern systems can do most of what was promised. The problem isn’t usually the platform; it’s where the platform sits in someone’s day.
It’s not telling you that you failed. Buying a learning system and watching adoption stall is one of the most common experiences in this category. It’s a category-wide design assumption that hasn’t aged well, not a private embarrassment.
Now, the more useful reading.
What the number is telling you
A login is a small but honest piece of evidence about one thing: whether the learning is where the work is.
Every login asks a person to stop what they’re doing, switch context, go somewhere else, and come back. People will do that for things they truly need — a benefits enrollment, a password reset, a compliance deadline. They won’t do it for things they only sort-of need, or things that might be helpful someday. That’s not laziness. That’s how attention works under deadline pressure.
So a low login number is telling you, very precisely:
The learning is sitting outside the flow of work, and your people are choosing the work.
That’s it. That’s the whole signal. Once you see it that way, the next moves get a lot clearer.
Inside the flow of work vs. outside it — in plain language
This is the one definition worth memorizing, because the rest of the article hangs off it.
Outside the flow of work: learning your people have to leave their job to reach. A separate site, a separate login, a separate calendar block, a separate mental mode.
Inside the flow of work: learning that meets them where they already are — in the tools, conversations, and moments where the actual work happens. They don’t go to it. It shows up.
A 40-minute course on objection handling, hosted on a platform someone has to remember to log into between calls? Outside. A two-minute walkthrough that pops up in the CRM the first time a rep opens a deal over a certain size? Inside. A library of leadership videos sitting in a portal? Outside. A short recorded answer from your best manager, dropped into the Slack channel where new managers ask their hardest questions? Inside.
You don’t have to abandon the system you bought to move things inside. You have to change what lives in it, and where it shows up.
The “Why Nobody Logs In” diagnostic
Run this on your own setup. It takes about ten minutes. Answer honestly — the point is to find the gap, not to defend the rollout.
Score each question 0, 1, or 2. Then add them up.
| # | Question | 0 — No | 1 — Sort of | 2 — Yes |
|---|---|---|---|---|
| 1 | Does the learning appear inside a tool people already use daily (CRM, inbox, chat, project tracker), without a separate login? | No, it’s its own portal. | We’ve embedded one or two things. | Yes — most of it shows up in their normal tools. |
| 2 | When someone hits a real moment of need — a hard call, a new task, a stuck deal — can they get the relevant help in under two minutes? | Not really. | Sometimes, if they know where to look. | Yes, and we can point to examples. |
| 3 | Is most of the content created or curated by people who actually do the work (not just L&D or an outside vendor)? | No, it’s all bought or built centrally. | A little — a few SMEs contributed. | Yes — internal experts are regularly creating it. |
| 4 | Does a person’s manager have a clear, weekly reason to point at something specific in the system? | No, managers ignore it. | Some do, some don’t. | Yes — managers use it as part of how they coach. |
| 5 | Can you tie at least one piece of learning to a business outcome (ramp time, error rate, win rate, retention), not just completions? | No, we report completions. | We’re starting to. | Yes — we have at least one real outcome story. |
0–3: The learning is almost entirely outside the flow of work. Low logins are exactly what you’d predict — and the system is doing what you set it up to do. Nothing personal.
4–6: You’ve got pockets of “inside the flow,” surrounded by a lot of “outside.” The hallway is winning because it’s closer to the work than your system is.
7–10: You’re closer than you think. Adoption is probably already higher in those pockets — and the move is to expand them, not to launch another campaign.
Whatever you score, the diagnostic itself is the artifact. Screenshot it. Walk a peer through it. Take it to the meeting.
The handful of moves that actually change adoption
You don’t need fifteen initiatives. You need two or three, and they all follow from the diagnostic.
Move 1 — Put the next piece of learning where the work happens, not where the system lives
Pick one high-stakes moment in your business — a sales objection, a customer escalation, a first-week onboarding task — and put the relevant help into that moment. Embedded in the CRM. Linked in the ticket template. Pinned in the channel. Anywhere except behind a separate login.
You’re not migrating your whole library. You’re proving the pattern with one piece, and watching what happens when learning is the path of least resistance instead of a detour.
Move 2 — Make your best people the source, not the audience
The single most underused asset in your organization is the person three desks down who’s quietly excellent at the thing everyone else is struggling with. Find two of them. Ask each one to record a five-minute answer to the question they get asked most often by teammates. Drop those answers where the question actually comes up.
This is the hallway, captured. It is also the move that changes how your people feel about the system, because now it sounds like them, not like a vendor.
Move 3 — Give managers one specific thing to point at, every week
Adoption doesn’t come from broadcast emails. It comes from a manager saying, in a one-on-one, “Hey, before our next pipeline review, watch this two-minute thing — it’s exactly what we talked about last week.”
Pick one piece of content a week. Tell managers what it is and why it matters for their team’s work this week. That’s the campaign. That’s the whole campaign.
If you can only do one of these this quarter, do Move 1. If you can do two, add Move 3. Move 2 compounds over time and is worth starting in parallel, even small.
How to talk about this at the leadership table
You don’t have to walk in and confess. You have to walk in and reframe.
Here’s the shape of it, in plain language you can adapt:
“Our login numbers are lower than we want, and I want to tell you what they actually mean. They’re telling us our learning is sitting outside the flow of work — people are choosing the work, which is the right instinct. We’re moving the highest-value pieces into the tools people already use every day, starting with [the moment you picked in Move 1]. I’ll report back next quarter on outcomes, not completions.”
Notice what that does. It treats the number as a finding, not a failing. It names a specific design choice and a specific next move. It promises a different kind of evidence — the kind your leadership actually wants. And it stops you from being the person who has to defend an activity metric nobody at the table respects anyway.
You’re not asking for forgiveness. You’re upgrading the conversation.
A quieter note about the real learning
You already sense this, or you wouldn’t have read this far: the most valuable learning in your organization is already happening. It’s in the hallway, the Slack DM, the “do you have a second?” pulled aside before a meeting. The knowledge that walks out the door at 5 p.m. is the knowledge your business runs on.
The work ahead isn’t forcing people into a system. It’s building a thin layer that catches what’s already moving between them, and puts it back where the next person needs it. That’s where the deeper pieces in this series go next — how to capture peer-to-peer expertise without turning your best people into content factories, and how to measure learning in a way that earns respect at the leadership table.
For now, one thing to take with you, and one thing to do.
The thing to take with you:
Low adoption is a placement problem, not a people problem.
The thing to do: run the five-question diagnostic on your own system before the end of the week. Whatever you score, you’ll walk into your next meeting with a clearer story than you have right now — and a much better one than the dashboard alone was going to give you.