The truth
Your resources aren't being ignored because people hate learning.
They're ignored because they don't solve an urgent job problem in the moment of need.
Goal: performance, not consumption.
The 7 reasons resources don't get used (and the fix)
1) Too long → Shrink it
If it takes longer than the problem itself, it loses.
Build assets in these sizes:
- 60–90 sec: one concept
- 2–3 min: one process
- 1 page: one decision (checklist / job aid)
Rule: One resource = one problem.
2) No obvious value → Pass the 5-second test
If the promise isn't instantly clear, they bounce.
Write situational titles (not academic):
- Bad: Compliance Training Module 4
- Good: What to Do When a Customer Requests a Refund Outside Policy
Use this intro template:
You're [in the situation], and you need to decide ___ in under ___ minutes.
3) Too generic → Make it role-specific
Generic content feels like "not for me." Before you publish anything, answer these five questions:
| Question | Fill this in |
|---|---|
| Who is this for? | Specific role/team |
| What triggers it? | Real moment of need |
| What should they do after? | Specific behavior |
| What does "good" look like? | Example / rubric |
| How will we measure usage? | A metric that isn't completion |
4) Hard to find → Design for retrieval
If someone can't find it in 30 seconds, it doesn't exist.
Minimum metadata (every asset):
- Plain-English title (or whatever the majority language is)
- 1-sentence summary ("Use this when…")
- Role tags + problem tags
- Time to use (e.g., "2 min")
- Owner
- Last updated date
- Linked from the workflow where the problem happens (Notion, Slack, LMS, manager playbook)
Rule: Search time > 30 seconds = invisible.
5) Passive → Force a decision
"Read this" or "watch this" produces consumption data—not capability.
Add one active element:
- scenario question
- decision tree
- 3-question mini-quiz
- "What would you do?" prompt
- 1 practice example + answer key
Structure:
- Situation
- Decision
- Consequences
- Correct path
- Try one
6) No reinforcement → Give managers a script
If managers don't reference it, people assume it's optional.
Manager pack (copy/paste):
- 2-sentence message to send
- 2 discussion questions
- 1 follow-up prompt (48–72 hours later)
- 1 behavior to look for this week
7) Wrong measurement → Track usage + outcomes
Completion is not the outcome.
Track:
- Search → open rate (findability)
- Start rate (promise quality)
- Drop-off point (where it loses them)
- Repeat usage (utility)
- Scenario accuracy (understanding)
- Behavior metric (what changed in the work)
The "Fix One Asset" sprint (do this first)
Pick one high-value resource that's accurate but underused.
Step 1 — Finish this sentence
Someone uses this when ___, and they need to decide ___.
Step 2 — Cut to the minimum
Keep only:
- what they must know
- what they must do
- mistakes to avoid
- one example
Step 3 — Rebuild it into this format
Problem (moment of need):
Why it matters:
What to do (steps):
Example:
Check yourself (1 scenario question):
Next step:
Step 4 — Publish where the work happens
Link it from the exact place the decision occurs.
Step 5 — Add one reinforcement touch
A manager script or an automated follow-up prompt.
Why video is the fastest format for "actually used"
Not because video is magic—because it reduces friction and compresses the important idea.
Best lengths:
- 60–90 sec = one concept
- 2–3 min = one process
- 3–5 min = deeper walkthrough (split if longer)
Next step (free)
🎬 Turn one ignored L&D resource into a narrated animated video in minutes.
Start free on Knowlify and rebuild your first underused resource into a short video your team will actually watch.
Best starting inputs: a PDF, slide deck, SOP, onboarding doc, playbook, or even an idea.