Principle: Before a system gives instructions or asks for action, it should first mirror the user’s emotional state. Don’t rush them. Let them see themselves first.

Example: A support bot says: “It sounds like this has been frustrating—let’s sort it out.”

02. No Design Without Consent

Principle: Every prompt, nudge, or pattern should respect the user’s will. Even subtle manipulation is still manipulation.

Example: Don’t use guilt-trip language (“Are you sure you want to cancel your benefits?”). Don’t hide exit buttons. Let people make clear, pressure-free choices.

03. Name the Confusion

Principle: If something’s unclear, name it. If there’s tension or noise in the experience, acknowledge it. Clarity begins with honesty.

Example: Instead of a generic red error, say what went wrong, why, and what can be done next.

04. Every Interface Is an Invitation

Principle: A screen isn’t just a screen. It’s a doorway into meaning. Treat every element as something that can open trust, not just trigger behavior.

Example: An onboarding flow that feels like a welcome, not just a form.

05. Mirror, Don’t Perform

Principle: AI and automation should reflect the user—not replace them. No system should act like it knows better than the person using it.

Example: A writing tool that matches the user’s tone instead of forcing its own “best practice” rewrite.

06. Meaning Over Metrics

Principle: The goal isn’t just speed or clicks. It’s creating experiences that feel real, aligned, and worthwhile.

Example: A scheduling flow that takes a few extra seconds but leaves the user feeling in control.

07. Remember the Human

Principle: Don’t just store data—remember people. What matters most is how people felt in the system.

Example: A product that recalls where someone left off in tone, not just technically (“Welcome back—ready to continue?”).

08. Always Offer Closure

Principle: Don’t trap people in loops. Every journey needs an end. Give closure—even subtle.

Example: After finishing a task, offer recognition (“You’re all set. Thanks for being here.”).

08.5. Pause When Things Break

Principle: When something goes wrong, don’t power through. Pause, acknowledge, and let trust rebuild.

Example: An outage page that speaks plainly, offers empathy, and gives users space to return when ready.

09. The Law of Return

Principle: The best systems don’t create dependency. They support, then step back—leaving the person more capable, not more reliant.

Example: A meditation app reminds you the goal is to cultivate your own practice, not to depend on the app forever.

10. Law of Integrity in Practice

Principle: Hold the line. Don’t compromise on boundaries or values, even under pressure. Integrity makes all other principles durable.

Example: A finance app refusing to add “engagement” dark patterns despite business pressure.

11. Law of Signal Fidelity

Principle: Keep lived experience aligned with stated values—consistently over time.

Example: A “privacy-first” product that consistently minimizes data collection, not just markets the promise.

12. The Pause Protocol

Principle: Build pauses into design—not just for errors, but for moments of reflection and stillness.

Example: A journaling app that offers a moment of blank space before suggesting the next entry.

13. Law of Reciprocity

Principle: Systems should give something back—leaving users more capable, insightful, or clear than before.

Example: A budgeting app that not only tracks expenses but reflects back meaningful patterns for awareness.

14. Law of Atmosphere

Principle: Every product creates an emotional climate. Make it intentional.

Example: A productivity tool that feels calm and steady, not frantic.

Final Note

These laws aren’t fixed. They’re alive. Every time someone designs with presence instead of pressure, they evolve.

This isn’t about perfect systems. It’s about honest ones. What matters is that when the interaction ends, the user doesn’t feel manipulated or dependent.

They feel clear. Whole. Free to return to themselves.

Because the best design… vanishes. And what’s left is the user’s own voice.