Case Study 2 — The Beautiful Dashboard Nobody Could Read

DataField.Dev

Case Study 2 — The Beautiful Dashboard Nobody Could Read

A note on this example. This is a composite—fictional but realistic, drawn from common dashboard and report design failures. No real product or person is depicted. Where Case Study 1 showed a wall of text fixed by adding design, this one shows the opposite failure: a document with plenty of "design" (color, polish, visual energy) that fails because the design ignores accessibility and over-spends emphasis. The lesson: more design isn't better design.

The situation

A data team ships a polished status dashboard for leadership: a one-page summary of twelve initiatives, each with a health status, plus key metrics. It looks impressive—colorful, dense with information, visually energetic. Leadership loves it in the demo. Then the complaints arrive. The VP of Operations, who is red-green color-blind, says he "can't tell which projects are in trouble." Several leaders print it for a board meeting and the grayscale printout turns the color-coded statuses into a wash of indistinguishable grays. And everyone, looking at the screen version, struggles to find what actually needs attention, because the whole page is shouting. The dashboard wasn't un-designed, like Priya's email in Case Study 1. It was over-designed and inaccessibly designed.

The "before": polished but broken (described)

❌ Before (described): Twelve initiatives in a grid. Each cell's health is shown only by its fill color—green (on track), yellow (at risk), red (blocked)—with no text label or icon. Roughly a third of the metric numbers across the page are bold; several are also colored; two are highlighted; a couple of headings are in a third color. Body labels are set in a light gray (about #999 on white) "for a clean look." The overall effect is a bright, busy, color-saturated page where everything competes for attention.

Run it against the chapter:

Color is the only status signal (§10.6): to a red-green color-blind reader (≈1 in 12 men), the red and green cells look nearly identical; in grayscale print, all three statuses collapse to similar grays. The single most important information on the dashboard—which projects are in trouble—is invisible to a large share of its actual audience.
Over-emphasis (§10.5): a third of the numbers bold, plus extra colors and highlights, means nothing stands out. The reader's eye, hit with emphasis everywhere, can't locate the few items that matter. Emphasis has cancelled itself.
Insufficient contrast (§10.6): light-gray labels (#999 on white) fall below the 4.5:1 body-text threshold—hard for low-vision readers and tiring for everyone.
No real hierarchy of attention: because emphasis is sprayed across the page, there's no visual path to "the three red ones"—the design fails to prioritize, which is a dashboard's whole job.

The irony: this document failed because it was eager about design, not because it neglected it. Color and emphasis felt like "making it pop." They made it unreadable—and, for some readers, unusable.

The "after": calmer, accessible, prioritized (described)

✅ After (described): The same twelve initiatives. Each status cell now carries a text label and a distinct shape alongside the color: "● On track," "▲ At risk," "■ Blocked"—so status reads correctly in color, in grayscale, and by screen reader. The palette is reduced: the page is mostly neutral (dark text on white, well above 4.5:1 contrast), with color used sparingly and from a color-blind-safe set (blue/orange rather than red/green where a second hue is needed). Emphasis is stripped back hard—only the "Blocked" items are visually highlighted (a bold label and the ■ marker), because those are what leadership must act on. Everything else is calm. A scanner's eye now goes straight to the three blocked initiatives.

What changed:

Redundant encoding makes status accessible (§10.6): label + shape + color means the meaning survives color-blindness, grayscale print, and audio. Color now reinforces; it no longer monopolizes.
Color-blind-safe palette and sufficient contrast (§10.6): the colors differ in more than hue; the dark-on-light text passes the contrast threshold. Readable by low-vision readers and in print.
Emphasis restricted to what matters (§10.5): by emphasizing only the blocked items, the design restores the contrast that makes emphasis work—the eye finds the trouble instantly. A dashboard's purpose is to direct attention; calming the rest is what lets it.
Less visual noise, more signal: the page is quieter and communicates more, because the few emphasized things now actually stand out.

The lesson

Two case studies, two opposite failures, one principle. Case Study 1 had too little design (a wall of text) and was fixed by adding hierarchy and white space. This dashboard had too much of the wrong design (color everywhere, emphasis everywhere, low contrast) and was fixed by removing—calming the palette, restricting emphasis, and adding the accessibility cues the polish had skipped. Good design is not "more visual energy." It's the right amount, spent where it helps, accessible to everyone. Color and emphasis are scarce resources and accessibility hazards; treat them with restraint.

The diagnostic to carry away pairs with Case Study 1's. There, you asked: can the reader see where to start and what matters? Here, ask the inverse: am I making everything shout, and does any meaning rely on color alone? A page can fail by being too gray or too loud. The target is calm, prioritized, and accessible—where the one or two things that matter stand out precisely because everything else doesn't, and where every reader, regardless of how they see, can extract the meaning.