Journal

Recognition Before Instruction

A first encounter should show that a person's purpose has been understood before explaining the tool's own language.

Field NotesPublished October 9, 2026Work period June 1, 2026 to June 7, 20262 min readIsrael Wilson

A child brings a drawing to a teacher.

The teacher could begin by explaining perspective, proportion, and the correct way to hold a pencil. Those lessons may matter later.

A better first response might be to notice what the child made.

"You made the dog look as though it is running."

The child has been recognized before being instructed.

In the first week of June, our work on first encounters with Rhiz returned to a similar principle.

The first useful moment

Technology companies often begin with explanations.

There is an account to configure, a product tour to finish, and a vocabulary to learn. The user enters with a purpose. The system enters with a curriculum about itself.

Those two intentions can pass each other without meeting.

A person who has taken the trouble to explain what matters to them should receive evidence that the system understood their words.

That could be a careful reflection, a useful distinction, or one question that makes the next step clearer.

It should belong to the person's actual situation.

Understanding is the first service a system can provide.

Recognition has limits

A good teacher listens before prescribing. A good doctor asks about symptoms before recommending treatment. A thoughtful friend understands that an immediate answer may be less useful than the right question.

The same pattern belongs in intelligent tools.

It does not require pretending to know more than the evidence allows.

A system might say, "I understand you want to reopen this community building. I do not yet know who owns it."

That sentence is useful. It recognizes the person's purpose and reveals the next missing fact.

The answer becomes a doorway into real work.

Remove one explanation

Open your product as a stranger.

Count how many things someone must learn about your organization before they can make progress on their own goal.

Then remove one.

Replace a feature tour with a relevant question. Replace generic encouragement with a truthful observation. Let the useful action teach the meaning of the tool.

First encounters reveal what kind of relationship people have entered.

Make that relationship begin with attention.

3 related pieces

Field NotesPublished October 9, 2026Work period May 4, 2026 to May 10, 20262 min readIsrael Wilson

The Important Thing Was in the Margin

When the most useful information is pushed to the edge of a screen, design has chosen the wrong center.

Why should useful information occupy the center of a digital experience?

Field NotesPublished October 9, 2026Work period July 27, 2026 to August 2, 20263 min readIsrael Wilson

The Shape of a Promise

Design decisions teach people what a system values long before the first explanation appears.

How does visual design express who has authority, attention, and agency?

Field NotesPublished October 9, 2026Work period June 15, 2026 to June 21, 20262 min readIsrael Wilson

A Doorway Should Speak Human

The first words of an institution should help people recognize their own needs before introducing the machinery inside.

How should a public entrance explain an unfamiliar product or organization?

Bring the work that matters.

Run a first read