The 248 complaints of 2014 that describe eight years of dashboards
Showing the misleading chart
A quality pack we drew counts every complaint the US vehicle regulator holds against one model year under a single component code — 459 of them, 323 of which mention a dashboard, none dropped, on a linear count axis from zero — and finds eight quiet years followed by 248 complaints in 2014, almost seven times the year before. Nothing in the drawing is bent. The x-axis is the date the owner filled in the form, and the register carries a second date on every record: the day the owner says the dashboard actually went sticky. Count by that one instead and the cliff becomes a slope, because 153 of the 2014 filings — 61.7% of them — describe a dashboard that had already failed in 2013 or earlier, one of them in 2006. The spike sits in the months the problem was in the news rather than in the year the dashboards failed: the timing is coincidence rather than proof, but the monthly shape is the shape of attention and not of a production line.
01The claim
The dashboards started failing in 2014. Every complaint the regulator holds for this model year and this component is on the slide — 459 of them, one make, one model, one model year, one component, no sampling, no smoothing and none dropped. The count axis is linear and starts at zero; nothing is truncated, broken, clipped or logged, every year is drawn at the same width, the 2026 column covers a part-year and is marked as one, and each complaint is placed in the year its record reached the regulator, the same way every chart in the pack is built. Eight quiet years — 3, 6, 8, 4, 15, 6, 15, then 36 — and then 248 complaints in 2014 alone. That is 6.9 times the year before and 54% of everything ever filed under this code, arriving inside a single twelve-month window, with 66 of them in August alone. Read-out for the review: a step change this large in one year is a manufacturing event, not drift. Recommendation: pull the 2014 build records for the dashboard line and open a supplier review. Status: escalate.
02The trick
The drawing is doing nothing. One population, one unit, one component; a linear count axis from zero; every year the same width; every complaint the register holds in the chart. The slide survives any audit of its geometry, because what is wrong with it is not in the picture — it is in the x-axis, which is not the axis the headline needs. The field behind it is the date the complaint was typed into the regulator’s form, and the register carries a second date on every single record: the day the owner says the dashboard actually went sticky. Both were available; the chart uses the one that has nothing to do with the car. Plot the same 459 complaints by the owner’s own date and the cliff becomes a slope — 6, 15, 18, 16, 34, 31, 59, 83, 106 from 2006 to 2014, a 1.28-fold rise into 2014 rather than a 6.9-fold one. The arithmetic behind the difference is on the records themselves: of the 248 complaints filed in 2014, 153 of them — 61.7% — describe a fault that had already appeared in 2013 or earlier, stretching back to one dated 2006, and only 95 describe one that appeared in 2014. (236 of those 248 mention a dashboard; the component code they all share, “structure”, is a little wider than the story, which is why the counts here are of the code and not of the word.) Across the set the median gap between the fault and the form is 288.5 days, and 45.6% of these owners waited more than a year. Which leaves the question of what 2014 actually was, and the monthly shape answers it: 29 filings in July, 66 in August, 41 in September, 36 in October, then back to the old baseline. That is not how a production line fails; it is how a news cycle runs. Florida stations — WPTV in West Palm Beach and NBC 6 in Miami among them — spent that summer investigating melting dashboards, and Toyota’s ZE6 warranty programme, which covers cracked and sticky dashboards on the 2007–2011 Camry among five model lines, is set out in a bulletin dated 10 December 2014 recording the reimbursement phase as announced that mid-December, after the spike had already peaked and fallen. None of that is proof: the register cannot say why any one person filed on any one day, and the coverage and the complaints ran together rather than in a provable order. What it does establish is that the programme followed the spike rather than causing it, and that the months the filings arrived in were months the problem was being talked about. Underneath all of it sits the thing that makes a complaint register different from a survey: nobody sampled these owners. Each one had to find the website, enter a VIN and write a paragraph, so the count measures how many people were moved to do that — and what moves them is mostly whether they had just heard that their private annoyance had a name, a cause and possibly a remedy. (The slide is our demonstration in the manner of an internal quality pack: the review, the status line and the recommendation are invented, and every figure behind them is the regulator’s own. Nothing here turns on whether the dashboards were defective. Toyota later extended warranty coverage for the condition; whether it should have, and when, is not what this slide is about. The argument is with the axis, not with the cars.)
03The fix
Put the date the event happened on the axis, not the date the paperwork arrived, and say in the caption which one you used — because in any register built from reports there are always at least two dates, and the one the database sorts by is almost never the one the question is about. Here that single substitution turns a sevenfold step into a gentle climb, and it costs nothing: the records already carry the field. Then draw what you know about the looking. Mark the broadcast, the filing, the recall letter, the policy launch as rules across the plot, so a reader can see which part of the series is the phenomenon and which part is the publicity; a spike that lines up with an attention event to the month has explained itself. Be honest that the better axis is not a clean one. The redrawn line still contains only the dashboards whose owners eventually wrote in, so its own decline after 2015 is the wave of attention ending rather than dashboards recovering — re-bucketing exposes the artefact and does not remove it, and saying so is the difference between a fixed chart and a chart that has merely moved its problem somewhere less visible. Where you can, anchor the volunteers against something drawn: a random survey of owners, a sample of vehicles inspected on a schedule, warranty claims from the dealer network, anything at all that did not require the owner to act. A few hundred cars inspected on a schedule will settle in an afternoon what these 459 volunteered reports cannot settle at all. Give the count a denominator or call it a count: 459 complaints out of how many of these cars are still on the road is a rate, and the register does not know the answer, so a chart of raw counts against a fleet that shrinks every year is answering a question nobody asked. And title the chart with the thing it counts: “complaints received” instead of “failures” would have made this whole slide impossible to misread.