The Empty State Is a Promise: Designing Honest Zero-Data Screens
July 6, 2026 · 5 min read
By Joy Ojochegbe, Product & Brand Design at Genovo Technologies
Every product is judged on its full screens; the good ones are designed on their empty screens. A new Synthos account has no datasets, no validations, no findings — and every one of those moments either teaches, misleads, or shrugs. We treat the empty state as a first-class deliverable with a strict rule attached: it must tell the truth.
The rule sounds obvious until you meet the temptations. An analytics card with no backend yet could render plausible placeholder numbers. A findings table with no sampled coverage could show a reassuring green zero. Both would demo beautifully and both would be small lies compounding into distrust.
Three honest patterns
Our empty states resolve into three deliberate patterns:
- Teach — first-run screens explain what will appear here and offer the action that creates it: upload your first dataset, run your first validation.
- Disclose — an empty findings list explains its coverage: results come from a bounded sample of text formats, columnar inspection arrives with the GPU pipeline. Absence of evidence is labeled as exactly that.
- Badge — when an admin chart renders sample data because its endpoint is not live, an explicit “Sample data” badge sits on the chart. Placeholder without a label is indistinguishable from fraud at a glance, and glances are how dashboards are read.
Hide, do not fake
The companion principle governs unshipped capabilities: features whose backends are not live hide entirely rather than rendering dead buttons. A control that does nothing teaches users that controls do nothing. Interfaces earn trust the same way people do — by never making the reader double-check whether something meant what it said.