← Chapter 12 companion · All chapter resources
Worked solutions to the two Practice on your own problems from Chapter 12 (§ Practice). Work each problem yourself before opening the reveal — the moment of comparing your read to the worked answer is where the discipline gets internalised.
Problem 1 — the operational-monitoring exception
Restated: A logistics team asks Copilot for a real-time warehouse-throughput dashboard. Copilot returns a 12-visual page, dense and detailed. Name why the 5-Visual Rule may not be the right check for this dashboard, and name the check that replaces it for the operational-monitoring case.
Show worked solution
Why the 5-Visual Rule does not apply. The 5-Visual Rule is calibrated to executive-summary dashboards: pages read for thirty seconds by an audience that is not going to look at them again today. Under those conditions, more than five visuals dilutes the primary KPI and slows the decision to unhelpful. An operational-monitoring dashboard has a different audience with a different reading pattern: warehouse dispatchers, logistics coordinators, or shift-lead operators who read the same page every few minutes across an entire shift. They are trained on the layout; they know where every gauge lives; they scan for anomalies against a known baseline rather than search for a headline. Information density is the point, not a failure mode. Twelve visuals on an operational page can be exactly right if every visual answers a decision-relevant question the operator will ask this shift.
What replaces it. The check that governs operational-monitoring dashboards is the anomaly-scan check: can a trained operator, at a glance, identify which visuals are in a normal state and which visuals are in an anomalous state? The visual encoding on an operational page has to make normal-versus-anomalous readable without the operator having to interpret each number in isolation. Concretely, this means:
- Colour-coded state on every visual — usually a red / amber / green treatment, with redundant shape or position encoding so the state survives CVD (Chapter 6).
- Reference bands and target lines on every gauge so the operator does not have to know the target values from memory.
- Consistent layout across shifts so the operator’s eye learns where each visual lives and can scan for anomalies without hunting.
Wexler, Shaffer, and Cotgreave’s Big Book of Dashboards is the canonical treatment of the operational-vs-executive distinction; the operational-monitoring pattern gets its own case-study chapter there. The Ch 12 book text names this exception explicitly in the «When Copilot’s defaults are right» section — it is the second of the two conditions under which Copilot’s denser first draft is often closer to right.
Meta-observation. The 5-Visual Rule is a default, not a law. The point of Ch 12 is that dashboards should be composed deliberately; deviating from the default is fine when the deviation is named and the replacement principle is applied. What is not fine is shipping twelve visuals on an executive-summary page because you skipped the check entirely.
Problem 2 — the blurred-thumbnail failure
Restated: You take a screenshot of a dashboard, blur it, and it reads as uniform noise (no primary visible, no cluster, no white space). Which two of the four Refine checks are most likely failing? Name the sequence you would apply to fix the failure.
Show worked solution
The two failing checks. The blurred-thumbnail test is a composition failure indicator; when the blur produces uniform noise, the two Refine checks most likely failing are:
- Hierarchy — specifically size and colour. If every visual on the page is the same size and every visual carries its own brand accent, the blur cannot preserve a primary visual because there was no primary visual to preserve. The blur just averages everything to a uniform tone.
- Composition — specifically white space. If the page is packed edge-to-edge with visuals and no visible gutters separate decision-relevant chunks, the blur cannot preserve chunks because there were no chunks to preserve. Every pixel is chart; nothing is separator.
The 5-Visual Rule and Mobile checks are less likely to be the direct cause. A page with three visuals of equal size and no white space can fail blurred-thumbnail too (hierarchy + composition failure without a visual-count failure), and a page that passes on desktop can fail on mobile without failing blurred-thumbnail on desktop.
The fix sequence. Apply the four Refine checks in this order (not the order Ch 12 lists them — that order is pedagogical, this order is remedial for the blurred-thumbnail failure specifically):
- Hierarchy first, size before colour. Identify the one visual that answers the audience’s central decision question. Resize it to at least 2× the area of any supporting visual. Do not adjust colour yet.
- Hierarchy second, colour after size. Remove the brand accent from every visual except the primary. Render the supporting visuals in a muted-gray palette. The accent now appears exactly once.
- Composition third, white space. Add visible gutters between decision-relevant chunks — usually the primary KPI zone, the supporting-visual cluster, and any footer/narrative zone. If the page currently has no white space, budget 8–12% of the total page area for gutters.
- Re-run the blurred-thumbnail test. If it passes, ship. If it still fails, the primary KPI is not visibly dominant enough — return to step 1 and increase its size further, or reduce the supporting visuals’ sizes further.
Meta-observation. The 5-Visual Rule often enables the fix rather than being the fix itself: cutting from nine visuals to five is what creates the room for the primary to be visibly dominant. But cutting alone does not guarantee blurred-thumbnail pass; five equally-sized visuals fail the test the same way nine equally-sized visuals do. Hierarchy + composition are the load-bearing checks.
Related on this site
- Chapter 12 companion page — Rohan’s services-dashboard walkthrough, further reading, self-check quiz, and the full-composition Refine activity.
- Rohan’s services dashboard dataset — the aggregate rollups behind the two dashboards on the Chapter 12 companion page.
- All chapter companion pages.
- Errata — publication log for updates and corrections across all chapters.
About the three-tier Practice format
Each chapter of the book closes with a three-tier Practice block adapted from Cole Nussbaumer Knaflic’s course-adoption pattern in Storytelling with Data: Let’s Practice!: Practice with us (one worked problem with full solution in the book), Practice on your own (open problems whose solutions live here), and Practice at work (an open-ended prompt to apply the chapter’s move to a live artifact). This page hosts the middle tier.