The Myth That Executive Readers Want 'Context' Before the Answer
We are terrified of being misunderstood, so we bury the lead under five pages of background. This isn't polite; it's boring. Start with the answer.
The Information Designer London
Client Reporting Lead who is tired of confusing dashboards. He believes a report should answer a question, not just show a list of numbers. Writes here to help consultants and agencies turn their data into deliverables that clients actually read.
Note: “Oliver Metric” is a pseudonym. We use pseudonyms so we can write honestly about real work without naming clients, employers, or teams.
We are terrified of being misunderstood, so we bury the lead under five pages of background. This isn't polite; it's boring. Start with the answer.
We built a portal to save time. We ended up spending all our time resetting passwords. Here is why 'Self-Service' is often a trap.
We thought we were being smart by tracking who opened our reports. We weren't. We were just being creepy. Here is why surveillance is not a strategy.
Cramming 50 metrics into a report isn't transparency; it's a liability. More numbers just mean more questions you can't answer. Here is how to cut the noise.
There is no faster way to lose credibility than sending a report the client cannot open. Fragile links are bad manners. Here is the fix.
We hide the definitions of our metrics on page 50 and then wonder why the client is confused. If a chart needs a legend, put it next to the chart.
If your client needs to click six times to find the ROI, you have not built a report. You have built an obstacle course. Here is how to fix it.
We pile on the detail because we are insecure. We think volume equals value. It doesn't. It equals paralysis. Here is how to edit for impact.
If your report doesn't explicitly state what needs to happen next, it's just a brochure. Here is how to build the 'Decision Page'.
A big grey slice of pie labelled 'Other' is an admission of defeat. It tells the client you didn't look close enough. Here is how to tidy your buckets.
A dashboard should speak. If I have to interpret the charts myself, you haven't finished the job. Use the 'Three Tile' layout to force clarity.
Stop speaking in acronyms. If your report needs a legend, it has already failed. Here is how to rename your metrics so the client actually understands them.
We built a dashboard to empower the client. Instead, we gave them a toy. They played with filters for an hour, asked 17 questions, and made zero decisions.
We think interactivity is modern. The client thinks it is work. Stop hiding the answer behind a click.
Long paragraphs are a hiding place for bad ideas. If I have to excavate your point, you have failed. Cut the waffle.
Tiny fonts are a confession of cowardice. We cram every metric onto the slide because we are scared to choose. Here is how to regain your editorial courage.
Why are we still sending 50-slide decks? The Wi-Fi will break. The client won't read it. The two-page PDF is the polite, efficient alternative.
Stop trying to build a Swiss Army Knife dashboard. You’re just confusing the client and exhausting your analysts. Here is how to split the view.