Before the Tool Exists

In 2010 at Evernote, under Phil Libin, we were working on a markup tool.

Phil had one constraint:

No conventional editing controls.

Not a better version. Not a cleaner version.
No toolbar waiting to be discovered.
No visible set of tools to select at all.

The team did what experienced designers often do. We started sketching alternatives that looked different on the surface but behaved the same underneath. Clusters of controls. Grouped actions. Hidden menus. Variations on learned behavior.

Different clothing. Same skeleton.

I suggested something that did not land particularly well with some of my peers.

“Let’s go watch kids fingerpaint.”

Not usability participants.
Not power users.
Not designers evaluating interaction patterns.

Children.

Montessori classrooms. Kindergarten tables. Anywhere we could observe how people interact with a surface before they have learned what a “tool” is supposed to be.

There were a few scoffs.

Phil’s eyes lit up immediately. He leaned forward instead of away. We ran the observation.

What stayed with me was not the output of the study itself. It was the contrast.

Adults approach interfaces by interpreting intent first.

What is this trying to do?

Then they act.

Kids begin with action.

What happens if I do this?

Then they discover.

Same surface. Completely different relationship to it.

Adults carry decades of learned behavior into every interface they touch. We expect menus. We search for controls. We compensate automatically, even when a design is ambiguous or poorly structured.

Children do not compensate.

They engage or they walk away.

That difference matters more than most research frameworks acknowledge.

Much of modern usability testing quietly depends on adaptation. We recruit participants who already understand digital conventions deeply enough to recover from unclear design. If they eventually complete the task, the interface is considered successful.

Completion becomes the metric.

Comprehension rarely is.

Sometimes the signal we are looking for is buried underneath expertise.

Experienced users are extraordinarily good at masking design failure. They infer intent. They fill gaps. They normalize friction because they have spent years learning how software usually behaves.

The result is subtle but important.

Familiarity starts masquerading as clarity.

That day did not instantly transform how we designed products. It did change how I think about certainty inside design rooms.

When everyone rapidly converges on the same solution, it is often because the pattern is already socially familiar, not because it is inherently understandable.

Those are not the same thing.

Design improves when we stop pretending they are.