⚖️ Design decisions need 5x more justification ✦ Unicorn Club

← Back to Newsletters

Hey 👋

The dangerous moment in page sign-off is when your HTML breaks silently. The browser won't read it. You won't know until after ship, and by then the cost is credibility.

This week: a free test that catches it before sign-off, a name for the structural bias that makes design decisions take 5x longer to approve, and a two-line gate that stops underpowered tests from shipping.

Enjoy 🦄 - Adam at Unicorn Club.

Effortless feedback. Happier clients. Better websites.

Getting client feedback on websites is made ridiculously easy with BugHerd.

- Clients simply point, click and comment
- BugHerd automatically grabs a screenshot & saves technical details
- A task is created for your team to track

Goodbye endless emails. Get a client feedback process that just works - get BugHerd!

Start a free trial →

Three things worth your attention this week:

Build: Test browser read-aloud before sign-off and treat silence as broken HTML.

Shape: Name what counts as good enough evidence before your next review.

Ship: Add "Practical threshold:" and "Act if:" before running any test.

Top 3 this week 👇

Build: Your Browser Can Already Speak a Page ↗

Treat browser silence at sign-off as a broken HTML report, not a quirk.

Why: A page that won't speak at sign-off has broken HTML structure and accessibility failures ready to ship.

Adopt: Run browser read-aloud before you sign off a page. If it won't speak, something in your markup needs fixing.

Shape: The Justification Tax ↗

Name your evidence threshold before design review starts, or lose the room.

Why: It costs you the ideas designers stop pitching because the approval bar is too high to clear.

Adopt: Before your next design review, add one row to your spec: "Evidence we'd accept." Fill it in before the session starts.

Ship: Statistical Significance Isn't the Same as Practical Significance ↗

Statistically significant doesn't mean practically important.

Why: Statistical significance means you ruled out luck, not that the effect is large enough to act on.

Adopt: Before running any test, add two lines to your task description: Practical threshold: / Act if:

Let's make the newsletter even better ↗

Fill out a 15 second form to help shape the content and direction of the newsletter.

Dive into more

Ship: Accessibility testing takes more than a scan ↗ — Automated scanners miss most accessibility issues, so add keyboard navigation and a screen reader pass to your pre-release checklist.

Build: An in-depth guide to customising lists with CSS ↗ — If you're customising list markers with CSS, this covers ::marker, counter-reset, and the browser gaps worth testing before shipping.

Build: Standard HTML Video & Audio Lazy-loading is Coming! ↗ — loading="lazy" for video and audio is in Chrome Canary, ready to test on any media-heavy page this sprint.

Shape: Checking an LLM's work is a systemic, not an individual, problem ↗ — Quality checking for AI-generated work can't stay individual: build an explicit review gate before any AI output reaches users.

Build: Popover API or Dialog API: Which to Choose? ↗ — Use Popover for most overlays, Dialog only for true modals, and review the accessibility differences between them before picking one.

Useful Extras

Shape: Real-Time UI ↗ — AI-generated UI built on design systems

Shape: TBM 409: Minimally Viable Consistency (Part 2) ↗ — ideas that spread without being mandated

Build: Navigation API now Baseline Newly Available ↗ — intercept any navigation, build custom transitions

Build: Native HTML components don't guarantee good UX ↗ — where native elements fall short

Support the newsletter

If this was useful, here are two small ways to help it travel:

🚀 Forward to a designer spending more time justifying than designing.

📢 Book a Sponsorship

Thanks for reading

Adam from Unicorn Club

Follow me on X or BlueSky

Connect on LinkedIn

⚖️ Design decisions need 5x more justification

What makes good digital products work.