A Mercedes-Benz campaign did something remarkably simple.

It printed a steering wheel across a newspaper.

Readers could hold it, position it, and pretend to drive.

No tutorial.

No explanation.

No “Here’s what you should do.”

The design itself invited the interaction.

That’s a beautiful example of an important UX principle:

Design clues, not instructions.

A steering wheel already communicates something familiar.

Hands → Steering wheel → Hold it

That’s affordance in action.

The design suggests how it should be used. 

Digital products use the same principle every day.

A shopping cart suggests adding items.

A magnifying glass suggests search.

A map pin suggests location.

A play button suggests starting something.

A handle suggests dragging.

Familiar interactions reduce the amount of learning users need to do.

But there’s an important condition:

The behavior has to match the expectation.

If something looks draggable but isn’t, users get confused.

If a button looks clickable but does nothing, users get frustrated.

If an icon means something different from what users expect, cognitive load increases.

Affordance without function is a broken promise. 

So before shipping an interaction, ask:

• Can users tell what is interactive?
• Can they predict what will happen?
• Does the visual design suggest how to interact?
• Does it behave the way they expect?
• Do they receive immediate feedback?
• Can they succeed without reading instructions? 

The goal isn’t to make users study your interface.

The goal is to make the interface teach them.