Usability and Self-Evident Design

Drive toward self-evident, effortless use: scannable pages, conventions, minimal words, low cognitive load, and mobile courtesy, judged by whether an average user reaches their goal without it being more trouble than it is worth.

When this applies

• judging whether a design is good enough to ship (P003).
• designing or reviewing web or app pages that users navigate under time pressure (P005).
• designing or reviewing any page, screen, or interactive element (P041).

Procedure

Apply these principles to the situation under review; for each, name the user need at stake and the trade-off the choice carries.

1. Judge usability by the effortless-use test (an average or below-average user accomplishes their goal without it being more trouble than it is worth), remembering usability is about people rather than technology, endures over time, applies to anything interactive, and that higher perceived effort makes people less likely to act. (P003)
2. Design pages for scanning users: use conventions, clear hierarchy, obvious links, low distraction, and scannable content so the first reasonable choice can succeed. (P005)
3. Treat usability as courtesy: protect and build users' limited goodwill by making key tasks easy, being candid, saving steps, supporting recovery, and apologizing when needed. (P026)
4. Make every page or screen self-evident so users understand what it is and how to use it without conscious effort; when full self-evidence is impossible make it at least self-explanatory, and relentlessly remove the 'question marks' (moments of uncertainty) that add cognitive load and erode confidence. (P041)
5. Follow established placement, behavior, and appearance conventions unless a replacement is clearly better or adds enough value to justify a learning curve; innovate only when you have a genuinely better idea, keep creativity subordinate to usability, and let clarity trump consistency. (P055)
6. Omit needless words: aim to cut about half the words (then half again as a discipline), kill content-free 'happy talk', and eliminate instructions by making things self-explanatory (or cut any necessary instructions to the minimum), because most page words go unread and merely add noise. (P062)
7. Manage small-screen space by prioritizing rather than sacrificing usability: keep frequent or urgent things close at hand, accept more tapping and scrolling as long as the scent of information stays strong, never trade away usability to fit the space, use responsive design rather than maintaining separate site versions, and honor mobile courtesies (allow zooming, deep-link to the actual content, and offer a full-site option). (P065)

Principles applied

• P003 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P005 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P026 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P041 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P055 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P062 (high) — grounded in claims/evidence and chunk anchors in sources/.
• P065 (high) — grounded in claims/evidence and chunk anchors in sources/.

Provenance

Grounded in principles P003, P005, P026, P041, P055, P062, P065, their backing claims and evidence records, and paragraph-level source anchors under sources/anchors/. Every cited id resolves into this package's distilled spine; see provenance-ledger.md and reports/faithfulness-report.yaml.