Workplace Learning Usability: Making Learning Available Is Not the Same as Making It Usable

Making learning available is not the same as making it easy to use.

That sounds obvious, but a lot of learning design still behaves as though access is the main problem. What do we have? What topics are covered? What can people click into?

 

Those are fair questions. But they are not always the ones that determine workplace learning usability or whether something will actually help.

Most people do not come looking for development because a topic heading catches their eye. Usually it is because something in work has become difficult and they need help with it.

How do I prioritise when everything feels urgent?

How do I handle unclear expectations?

How do I have a useful conversation when everyone is already stretched?

That is often the real starting point.

The challenge, then, is not just whether resources exist. It is whether someone can recognise where to begin without having to translate a whole library first. That is a large part of workplace learning usability.

That came up for me recently in a piece of work I was iterating.

Deciding what to include was not really the difficult part. The bigger issue was making sure the learner did not land on a page full of plausible options and then have to do all the sorting themselves. In theory, a broad set of resources can look generous. In practice, it can leave people doing extra interpretive work at exactly the point where they want help, not another decision to make.

That is where I kept coming back to the paradox of choice.

More options can look helpful. They do not always feel helpful when you are the person trying to choose. If too many things appear relevant, it becomes harder to know what to trust, what to ignore, and what to start with. People hesitate. Sometimes they do nothing.

What helped me think this through was not just platform design. It was delivery experience.

When you have worked with people face to face, you get a much better feel for the kinds of problems they actually bring. People do not tend to think in tidy content categories. They usually want help with something specific, and their needs tend to cluster around that. That changes the design problem. It becomes less about listing resources and more about giving people a clearer route into them.

That is why I keep coming back to enablement.

Not as a replacement for learning, and not as a critique of it. More as the thing that helps people make use of what is already there.

Sometimes that means clearer entry points. Sometimes it means better framing. Sometimes it just means helping someone understand what a resource is for before asking them to spend time on it.

That matters even more when people are under pressure.

If someone has to do too much translation work simply to decide whether something is relevant, there is a good chance they will not get to it at all.

Access matters. But workplace learning usability matters too.

I also found AI useful in the iteration stage of this work.

Not as a substitute for judgement, but as a way to work through different structures quickly before testing them properly and building them in the live platform. It helped with prototyping. It helped me see alternative routes through the material. But the decisions were still mine to make.

That is probably the part I find most useful.

Not AI generating content for the sake of it, but AI helping me get to a better learner experience faster.

Sometimes the value in learning design is not adding more.

It is making it easier for people to find a way in.

​

More options can look helpful. They do not always feel helpful when you are the person trying to choose. If too many things appear relevant, it becomes harder to know what to trust, what to ignore, and what to start with. People hesitate. Sometimes they do nothing.

 

What helped me think this through was not just platform design. It was delivery experience.

 

When you have worked with people face to face, you get a much better feel for the kinds of problems they actually bring. People do not tend to think in tidy content categories. They usually want help with something specific, and their needs tend to cluster around that. That changes the design problem. It becomes less about listing resources and more about giving people a clearer route into them.

 

That is why I keep coming back to enablement.

 

Not as a replacement for learning, and not as a critique of it. More as the thing that helps people make use of what is already there.

 

Sometimes that means clearer entry points. Sometimes it means better framing. Sometimes it just means helping someone understand what a resource is for before asking them to spend time on it.

 

That matters even more when people are under pressure.

 

If someone has to do too much translation work simply to decide whether something is relevant, there is a good chance they will not get to it at all.

 

Access matters. But so does usability.

 

I also found AI useful in the iteration stage of this work.

 

Not as a substitute for judgement, but as a way to work through different structures quickly before testing them properly and building them in the live platform. It helped with prototyping. It helped me see alternative routes through the material. But the decisions were still mine to make.

 

That is probably the part I find most useful.

 

Not AI generating content for the sake of it, but AI helping me get to a better learner experience faster.

 

Sometimes the value in learning design is not adding more.

 

It is making it easier for people to find a way in.