Respect Existing Human Behavior
Good products do not punish people for being human.
Start With the Human — Do not begin with the product. Begin with the person.
People forget
People forget to save, forget deadlines, forget what they already entered, and forget to return to unfinished flows.
If a product knows this and still assumes perfect memory, the issue is not only the user. The system assumption deserves examination.
Good products do not require perfect memory.
People change their minds
A decision that was right today may not be right tomorrow. A setting may need revision. Published content may need updating.
Products that respect people leave room for change, edit, undo and correction whenever possible.
Change is not failure. It is part of being human.
People get interrupted
Work rarely happens in one perfect session. People get called away, switch tabs, change devices, lose network or return hours later.
Autosave, drafts and state recovery are not minor conveniences. They are ways the system respects reality.
Design for interruption, not uninterrupted fantasy.
People do not read every instruction
Not because they are lazy. Attention is limited and context is competitive.
If a flow works only when users carefully read all documentation, the product depends on an unrealistic condition.
Critical understanding should live in the flow, not only in the manual.
People are not always rational
Users may click too quickly, follow defaults, delay decisions, react to wording or overlook important information.
Design should not exploit those weaknesses. It should reduce the chance that a momentary mistake becomes a large consequence.
Human-centered design protects people from predictable mistakes, including their own.
Good products anticipate recovery
An error state should not be a dead end. People need to know what happened, what was preserved and what they can do next.
Good recovery turns mistakes from catastrophes into ordinary parts of interaction.
Recovery is a core product capability.
Undo, autosave, draft and search are forms of respect
Undo accepts that people change their minds. Autosave accepts that people forget. Drafts accept that work may not finish in one session. Search accepts imperfect memory.
These features are powerful not because they are technologically impressive, but because they understand human reality.
Respect often appears as recovery, memory and reversibility.
To me when I want to blame the user
If analytics show many people making the same mistake, I do not want to conclude too quickly that they “do not know how to use it.”
I want to ask what the system assumed about attention, memory, language or sequence, and whether design can make the error harder to make or easier to recover from.
User error is not always product error. But repeated user error is always product evidence.
Do not ask only why users fail. Ask what the system assumed about them.