Niss BerrySenior Product Designer
← Back to Writing

UX opinion article · July 2026 · 5 min read

Product Education Is Part of UX

People do not only need instructions. They need context, confidence and a clear next step.

A Nissberry writing piece about clarity, confidence and the quiet moment when a system does not explain itself.

A system they did not design

Somewhere, someone is trying to make sense of a system they did not design.

It might be Susan running her husband’s plumbing business, suddenly responsible for quotes, invoices, stock, bookings and the software that holds it all together.

It might be a cancer survivor leaving an appointment with too much information, too many new words and too little energy to decode what comes next.

It might be a junior designer opening Figma for the first time, trying to understand why everyone else seems to know the language already.

It might be an operations lead, an admin person, a therapist, a teacher, a patient, a parent or a small-business owner.

Different people. Different systems. Same quiet moment:

I am supposed to know what to do here, but I do not.

That moment matters.

Because when a product, process or platform does not explain itself clearly, the user does not usually blame the system first.

They blame themselves.

Scattered knowledge is a design problem

Most products do not fail because nobody explained anything.

Usually, the explanation exists somewhere:

  • A video in a folder.
  • A PDF attached to an old email.
  • A support message someone keeps forwarding.
  • A quick screen recording made by the person who had time.
  • A piece of context living in the head of the team member who has been there the longest.

The knowledge exists, but it is scattered. And scattered knowledge creates dependency.

People become dependent on memory, goodwill and the nearest helpful person. Inside businesses, that helpful person often becomes the unofficial trainer — the one everyone asks, who knows which link to send, which status means what and which tiny rule never made it into the interface.

That person may be an SME, an operations lead, an administrator or simply the team member who understood the system first. Good UX should care about them too — not only the person clicking the button, not only the product team, not only support.

The person who has to translate the product for everyone else is also part of the experience.

Documentation is not designed learning

Documentation tells people that information exists.

Designed learning helps people use that information at the moment they need it. That difference matters.

It is tempting to treat product education as something that happens after the “real” design work is done, in this order:

  1. 01The product is designed.
  2. 02The documentation is written.
  3. 03The videos are recorded.
  4. 04Support helps everyone who still gets stuck.

That order may make sense inside a delivery plan. It does not always make sense to the person trying to use the thing. Users experience the product as one continuous journey:

  • the label they read;
  • the button they click;
  • the empty state they land on;
  • the error message they do not understand;
  • the video they need but cannot find;
  • the colleague they ask because they are unsure.

A clean interface can still leave people feeling uncertain if the learning layer around it is weak.

That does not mean every product needs more explanation. Sometimes the best product education is a clearer label, a better flow, a kinder empty state or removing a confusing step entirely. But when the work itself is complex, the interface cannot always carry everything alone.

The goal is not to pretend complexity does not exist. The goal is to help people move through it without feeling lost.

What building a learning space taught me

In a previous product team I had the privilege of working with, useful learning material already existed. The problem was not that nobody cared. The problem was that the learning layer had not yet been treated as part of the product experience.

Training videos, support knowledge and helpful explanations lived across different places. Users and internal teams often needed someone to know which link to send, which video explained the right thing or where a particular answer lived.

The opportunity was not only to “make a resource page”. It was to make product knowledge easier to find, follow and reuse.

We shaped that scattered knowledge into a more structured learning space: clearer categories, more understandable pathways and short how-to videos placed closer to the questions people were already asking. It also reduced the pressure on one helpful person needing to remember where everything lived.

That part mattered to me. Because every time a user has to ask, “Can you please send me that thing again?”, the product has lost a little bit of trust.

Not because the user is incapable.

Because the learning experience has not been designed with the same care as the screen.

Confidence is part of the experience

We often talk about usability in terms of task completion:

  • Can the user find the button?
  • Can they submit the form?
  • Can they move from step one to step two?

Those things matter. But I care just as much about what happens underneath the task:

  • Do they feel stupid?
  • Do they feel dependent?
  • Do they feel like they are bothering someone?
  • Do they feel brave enough to try?
  • Do they trust themselves to do it again tomorrow?

When people feel unsure, they hesitate. When they hesitate, they avoid. When they avoid, the product becomes something technically available but practically underused.

Good product education helps close that gap. It gives people:

  • language;
  • context;
  • a path back when they forget;
  • enough confidence to make the next step feel possible.

That is not hand-holding in a negative sense.

That is care.

Inclusive learning belongs inside the experience

Once you start seeing product education as part of UX, you start seeing it everywhere.

I saw it in a therapy-support product where the experience needed to help therapists track a child’s session progress without interrupting the child, changing the natural rhythm of the session or needing another person to listen in just to count whether the right words were practised.

I see it in healthcare communication, especially after physically seeing and experiencing how easily patients and families can feel overwhelmed when information is rushed, scattered or filled with language they are too tired, scared or overloaded to decode.

I see it in a South African language and literacy idea I keep returning to, where data costs, device access, literacy levels and language all affect whether a digital product is genuinely usable.

And sometimes I see it in small moments of mainstream inclusion that make me unexpectedly emotional — like seeing Disney Animation reimagine familiar musical scenes in American Sign Language, with the characters themselves animated to sign. That stayed with me because it did not feel like access sitting outside the story. It felt like access being designed into the story.

When learning, access and understanding are designed into the thing itself, more people get to participate without feeling like they are asking for special treatment.

They are simply included.

Five things I now design for

If product education is part of UX, then it needs the same care we give to flows, screens and components. Here are five things I try to look for.

01

The moment of confusion

Where does the user pause?

Good education begins by noticing where uncertainty appears — in a label, an unfamiliar status, an empty state, an error message or a step that makes sense to the product team but not to the person using it.

02

The accidental teacher

Who becomes responsible for explaining the product inside the organisation?

If an SME, admin lead or operations person becomes the bridge between the product and the rest of the team, the experience should make their job easier, not heavier.

03

The first successful attempt

When does the product first start to feel possible?

A good learning experience helps users reach that moment sooner — not by overwhelming them with every possible detail, but by giving them enough context to complete one meaningful action with confidence.

04

The language users actually use

Whose words are we designing with?

If the product says “configuration mapping” but the user thinks “the thing that opens the right form when I scan this tag”, there is a translation problem hiding inside the interface.

05

The path back

How does someone return when they forget?

A strong education layer gives people a way back without making them start from scratch, search through old messages or depend on one helpful colleague.

Clarity is care

Teaching people how to use a product is not an apology for bad design. It is a sign that we respect the complexity of their world.

Some products are simple enough to explain themselves entirely through the interface. Many are not — especially in B2B software, healthcare, education, finance, operations and any system where the user is dealing with pressure, responsibility or uncertainty.

Clarity is not decoration. It is care.

Final thought

Product education is UX because confidence is part of the experience.

References / further reading

A few references that shaped or supported this piece.