Data Backed Design

Design debates, settled with receipts.

Design debates stall on opinion. The question that ends them is “what do the best teams actually do?”, but answering it usually means hours of digging through design-system docs, research, and help centers. Data Backed Design does that digging ahead of time, so you can ask a UI/UX or design-process question and get an answer in a minute.

topics
20
sources
54
evidence cards
2,655
counted positions
124

Every answer has the same four parts

The goal is a decision you can defend in a review, backed by sources you can open yourself.

Should I disable the submit button until the form is valid?

Direction

Keep the submit button enabled, and say what’s missing when someone presses it. Disable it only briefly, such as while a submit is already in flight.

Why

A disabled button can’t explain itself. People face a form that looks finished, with no way to find out what’s wrong.

Evidence

Atlassian (opens in a new tab), GitHub Primer (opens in a new tab), and GitLab Pajamas (opens in a new tab) say never disable it, and GOV.UK (opens in a new tab) says avoid it unless research supports it. Shopify Polaris (opens in a new tab) and Porsche Design System (opens in a new tab) allow it when the screen says why.

Disabling submit until the form is valid · contested4 of 8
Never 4 · Sometimes 4
  • Never: Atlassian, GitHub Primer, GitLab Pajamas, GOV.UK
  • Sometimes: IBM Carbon, Shopify Polaris, Microsoft Fluent, Porsche Design System

Tradeoffs

People will press submit on incomplete forms and hit errors they might have avoided, so the inline error messages have to carry the weight.

A shortened example. Citations open the source page they quote.

Some questions are settled. Some aren’t.

Answers say how strong the evidence is. When every source agrees, you hear that. When they split, you hear who sits on each side instead of a made-up consensus.

SettledForms & Validation
Error messages appear inline at the offending field16 of 16
Inline 16
  • Inline: GOV.UK, IBM Carbon, Shopify Polaris, Google Material 3, Atlassian, GitHub Primer, Adobe Spectrum, Microsoft Fluent, Salesforce Lightning, Mozilla Acorn, Stripe Apps, shadcn/ui, Porsche Design System, Base Web, GitLab Pajamas, Radix UI
LeaningForms & Validation
Labels sit above the field9 of 12
Top 9 · Floating 2 · Left by default 1
  • Top: GOV.UK, IBM Carbon, Atlassian, GitHub Primer, Adobe Spectrum, Microsoft Fluent, shadcn/ui, GitLab Pajamas, Salesforce Lightning
  • Floating: Google Material 3, Mozilla Acorn
  • Left by default: Ant Design
SplitForms & Validation
Disabling submit until the form is valid · contested4 of 8
Never 4 · Sometimes 4
  • Never: Atlassian, GitHub Primer, GitLab Pajamas, GOV.UK
  • Sometimes: IBM Carbon, Shopify Polaris, Microsoft Fluent, Porsche Design System

Four rules shape every answer

  1. Published sources only

    The corpus is built from material anyone can open: 54 sources, from the documentation of design systems like Carbon, Polaris, and GOV.UK to the help centers of products teams use every day and usability research from groups like Nielsen Norman Group and Baymard Institute. Nothing comes from private products or guesswork about them.

  2. Every quote checked

    Each of the 2,655 evidence cards quotes its source word for word. Before a card is published, a checker fetches the live page and confirms the quote is really there, and the card records when it was verified.

  3. Counted, not guessed

    Each of the 20 topics is broken into the questions designers actually debate, and the same core set of design systems is tallied on every one. That is where the counts in an answer come from. When a source says nothing, it is recorded as silent rather than stretched to fit, and when sources split, the answer names who sits on each side.

  4. Answers from the evidence only

    Your question pulls the most relevant cards from the corpus, and the answer is written from those cards alone. Citations to anything that was not retrieved are removed before you see them. If the corpus has nothing on your question, the answer says so instead of improvising.

Who makes it

Data Backed Design is made by Mark Uraine (opens in a new tab), a product design leader with 20 years experience. Over those years the same debates kept coming back:

  • Where do filters belong?
  • When should validation fire?
  • How should critique run?
  • Paginate or infinite scroll?
  • Toast or banner?

The fastest way to settle them was always to look at what strong teams had already published, and that took far longer than it should. Data Backed Design is that research, done once and answerable in plain language, with the receipts attached.

Got a debate to settle?

Your first 3 questions are free. Every answer comes with the sources behind it.