Unit 1 · Lesson 4 of 20

What makes an experience trustworthy?

Relate clarity, evidence, control, privacy, and reversibility to the stakes of a decision.

Ready to learnOne idea, one guided decision, and an application in a new context.
YOUR LEARNING PATH
04 / 20

01 / Learn

The idea

Trustworthy UX lets people form accurate expectations and retain appropriate control. The interface should make the proposed action, recipient, source material, and consequence visible before commitment. A fluent draft or confident tone is not proof that the content is correct or that the user has authority to send it.

The amount of review should reflect possible harm and reversibility. A small formatting change may need light feedback; a message to thousands of customers needs a reviewable payload, permissions, and a recovery plan. Privacy also matters: previewing sensitive information to the wrong role can be harmful even if no message is sent. Record uncertainty honestly and test whether users notice material limitations.

A common mistake

A generic 'Are you sure?' prompt creates informed consent. Confirmation without decision-critical context can increase clicks while leaving understanding unchanged.

See the idea in action →

02 / See the reasoning

Worked example

Fictional scenario

An AI assistant drafts a customer message and offers to send it to an entire account list.

An expert examines a 'Send now' button next to an AI draft. They add a review step showing recipients, the exact outgoing content, source status, and the operator's authority. If a source is outdated, the flow blocks the unsupported claim and offers editing or escalation. The design is judged by whether the human can actually catch a harmful action, not by the presence of a modal.

Try a decision →

03 / Decide

Guided decision

The draft cites a superseded policy, but the operator can see the approved current policy. Which flow would you test first?

Choose the option you would try first

04 / Apply elsewhere

Independent application

Fictional scenario

A shared physical access terminal lets a supervisor revoke a contractor's building access immediately.

Describe the review, authority, confirmation, and reversal or support path for this action. Include what should and should not be displayed on a shared terminal.

Make: A concise risk and control map with an annotated action sequence.

Review your work against this criterion

The proposal matches controls to consequence, identifies authority and privacy, and does not treat a generic confirmation as sufficient evidence of understanding.

05 / Keep working

Sources and related patterns

Apply this skill: UX critique and problem statement →

Saved items