10 minutes
Why voluntary learning stops It rarely stops because people lost interest. Five conditions hold it up, and the three usual rescues break the thing they are trying to save.
What you’ll be able to do Identify which of the five conditions — time, permission, relevance, visibility or safety — has gone missing on a specific team, using evidence the team already has. Compare the responses to this question and explain your choice: What is the most useful first move? Document a next step for Why voluntary learning stops: Name the last three staff members who told you they wanted to take something on and did not. For each, write which of the five conditions was missing, in one sentence, without naming anyone in anything you share. Interest is almost never the problem When a voluntary learning offering goes quiet, the first explanation offered in a leadership meeting is usually about motivation. People are busy, priorities shifted, the enthusiasm faded. That explanation is comfortable because it places the cause in staff rather than in the design, and it leads directly to the three interventions that damage voluntary learning most.
In a public agency, the more accurate explanation is nearly always structural. A staff member who wants to take a forty-minute module has to decide, in the middle of a caseload or a policy deadline, whether spending that time is allowed. If nobody has said out loud that it is, the safe answer is no. If the time is not on a calendar anywhere, the safe answer is no. If the module has no visible relationship to a decision the person will actually make, the safe answer is no. None of that is a motivation problem, and none of it is fixed by a reminder.
Five conditions hold voluntary learning up: time, permission, relevance, visibility and safety. They fail one at a time and they fail quietly. The useful question after a drop is not why people stopped caring. It is which of the five went missing, and when.
Five conditions, and how each one disappears Time Permission Relevance Visibility Safety
What it looks like when it holds: a protected slot on a real calendar, or an explicit statement that this counts as work time and does not have to be made up.
How it disappears: nobody says where the time comes from. Staff conclude, correctly, that it comes out of their own evening or their own backlog. The offering is not refused; it is postponed forever.
What it looks like when it holds: a supervisor says, in a meeting and again in writing, that taking an hour for this is expected to be normal, and then is seen doing it.
How it disappears: permission is assumed rather than stated. Newer staff, staff who are already worried about their standing, and staff whose work is closely measured all read silence as a warning.
What it looks like when it holds: a module is attached to something the team is about to do — a policy revision, a letter rewrite, a partnership meeting, a complaint pattern.
How it disappears: the catalogue is offered as a catalogue. Everything is available and nothing is connected, so choosing becomes one more decision in a week that is already full of them.
What it looks like when it holds: people hear what colleagues found useful, in ordinary conversation, and see something in the work change because of it.
How it disappears: learning becomes entirely private. Not private in the protective sense — private in the sense that nobody ever knows it happened, so it never becomes part of how the team talks about its work.
What it looks like when it holds: it is clear what is and is not recorded, reflections stay with the person who wrote them, and not knowing something is treated as ordinary.
How it disappears: a well-meant report, a roster, a stray comment in a performance conversation. It takes one instance for people to conclude that the honest answer is the expensive one.
Say the permission out loud, then be seen using it What you can change You control whether the people you supervise have actually heard that spending work time on this is normal, and whether they have seen you do it.
What to watch for Do not assume that opening a resource is the same as granting permission. Staff read the absence of a statement as a risk, and the people most likely to read it that way are the ones with the least standing to lose it.
Your next step At your next team meeting, say plainly where the time comes from, then block the same amount on your own calendar where the team can see it.
The three rescues, and what each one costs Requiring it
Turns reflection into compliance. People produce the answer that is safe to have on record, which is exactly the answer that teaches nobody anything. A genuine requirement may sometimes be right — but it belongs in the required-training system, negotiated openly, not bolted onto something that was introduced as optional.
Counting it
Turns curiosity into a file. Once individual use is visible to anyone above a person, the rational move is to open the module and move on. You gain a number that measures page-opening and lose the thing the number was supposed to describe.
Comparing teams
Turns colleagues into competitors and makes supervisors manage the number rather than the practice. It also lands hardest on units with the least slack, which are usually the units carrying the heaviest and most exposed work.
Required training
A genuine obligation with a real basis, recorded in the department's own system, with consequences that are stated in advance. It should be named as such, plainly, and never blurred with optional learning.
Voluntary learning
Chosen by the person, not recorded against them, safe to be honest in, and free to decline. Completion here does not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
I wanted to take the module on language access because I write the letters. What I could not work out was whether an hour of it would look like an hour I was not doing my job. Nobody had said either way, so I did not risk it.
Composite DSD program staff perspective, illustrative Private reflection, for you alone and collected nowhere: think of a colleague who has never taken up any of this. What in the way you run the team might be telling them that it is not for them, or not worth the risk? Nothing you write here is recorded or shared.
Carry this forward Voluntary learning depends on five conditions. Time that is actually protected, permission that people have heard out loud, relevance to a decision in front of them, visibility so the work is not invisible, and safety so that what a person does not yet know cannot be used against them.
The three usual rescues change what learning is. Requiring it turns reflection into compliance, counting it turns curiosity into a file, and comparing teams turns colleagues into competitors and exposes the least confident person first.
Required training and voluntary learning are different things with different rules. Keeping them plainly separate is what makes the voluntary part safe enough to be honest in.
A single time slot for everyone feels like fairness and quietly selects for people whose week looks like the organizer's. Treating sameness as fairness is the habit the continuum calls Minimization, and it is the most common default in a large division.
A scenario about a learning offering that went quiet by the third month, a knowledge check on what a drop in use actually tells you, and a condition-by-condition reading of one team.
Name the last three staff members who told you they wanted to take something on and did not. For each, write which of the five conditions was missing, in one sentence, without naming anyone in anything you share.
Browse and download only. Course notes are not typed or saved on this page.
Reset this lesson
Course overview Next lesson Participation and course completion in this program do not count toward DHS-required training credits unless management, a director, or DHS leadership expressly approves an exception.
