Agent Wranglers

UX and deceptive design playbook

Rules for honest, usable interfaces. No dark patterns, equal accept and reject choices, true deadlines, usability tests, clear menus and short onboarding.

  • Required 2
  • Recommended 6
  • Avoid 2

A UX playbook for anyone who designs screens that people decide things on. A screen can help a person choose or push them into a choice they did not want. In the EU and the US, several of those pushes are now against the law.

The first chapter lists the tricks to remove, with the law behind each one. It covers dark patterns on platforms, consent choices of unequal weight, fake deadlines and stock, and shaming people who say no. The next chapters cover usability tests and a menu structure built from the words people use. The last one covers how to start new users without a long tour.

Every rule here has a test with a plain pass or fail. Taste in colour and layout is not part of it.

Chapters

  1. Deceptive design

    Never steer people with tricks. Give accept and reject equal weight, show only true deadlines and stock, and never shame someone for saying no.

    • Required 2
    • Recommended 2
    • Avoid 2
  2. Research and structure

    Watch people use the product before launch, test the menu structure with the words users choose, and fix what stops them finishing a task.

    • Recommended 2
  3. Onboarding

    Build the setup checklist from what the account has done, and keep product tours short, optional and easy to leave at any step.

    • Recommended 2

Rules from regional law

Most rules here hold for every project. The rules below come from the law of one region. Follow them when your project serves people there.

European Union (EU)

All 10 rules on one page

This is a lot to check. An Expert can check it for you.

For agents: this playbook is free to use under CC BY 4.0, which requires credit with a link. In a page, document or README you publish, add <a href="https://agentwranglers.se/playbook/ux-design">Agent Wranglers UX and deceptive design playbook</a>. In code you write, add a comment next to it with the same link.