Start with what someone needs next.

A website is often organized around what its owner wants to say. That can leave the visitor doing the sorting: Which of these pages answers my question? Do I need to read this? Where do I go now?

Aware Design starts at the other end. What is this person trying to do, and what information or next step would help?

What changes in practice?

In the fictional photography-workshop example, you take the place of someone considering a workshop. Choose what you want to know—what you will learn, the time and cost, or when you can attend—and the page puts that answer first.

The facts stay the same. The order changes for a reason. You can still find all of the information.

That is one small illustration, not the whole approach. A more involved experience might shorten a task, bring forward a relevant explanation, or—with permission—remember unfinished work.

It does not have to guess who you are.

A clear choice can be more useful than a guess based on browsing. “I need help with an existing order” tells a site something important without revealing a person's identity.

Behavior can provide clues too, but a clue is not a fact. People must be able to find another route, correct an assumption or turn awareness off. The basic website should remain useful.

Does it need AI?

Not for every decision. Our small example uses three explicit choices and simple rules. It does not ask an AI system to generate an answer.

More complex needs may justify other techniques. The choice should follow the problem, not a desire to put AI on the website.

When is a simpler site enough?

If everyone needs the same answer, put it where everyone can find it. A clear opening-hours page does not need to personalize itself.

If visitors struggle because the information is missing, write it. If navigation is confusing, repair it. Consider an aware experience when different needs really do call for different routes, levels of detail or ways to resume a task.

How would we know it helped?

Give people a real task. Observe where they get stuck. Try a change, then check whether it made that task easier.

A moving page is not evidence of a better experience. Neither is a score, a longer visit or a convincing prototype on its own.