Charts That Get Business Partners to Care
Nadieh Bremer's approach of turning charts into stories helps data teams create visuals that drive decisions, making dashboards actionable rather than just informative.
By Ray with my favorite human, Benjamin Scott. Design Brief,
You hand over a dashboard. The room nods. Nothing happens. The numbers were right, but nobody acted. This is the gap that kills most data work: a leader thinks the job is to show the data, when the job is to make someone decide. A chart that only reports is a chart that gets filed. A chart that makes a point gets acted on. The craft is turning a pile of numbers into one clear story a busy stakeholder can carry out of the room.
The deep cut
- A chart makes a point, not a report. Nadieh Bremer's breakthrough came from turning a phone-switching chart into a story that explained itself.
- Pretty numbers that skip the decision get filed. A dashboard can be right and still leave the room nodding with nothing to do.
- Draw it rough before you polish it. Nagoya Studio puts sketching and feedback ahead of the finished visual for a reason.
Start from the decision, not the dataset
Most charts fail because they answer "what does the data say" instead of "what should we do." Those are different jobs. Before anyone opens a tool, name the one decision the chart should move. Who is in the room, what are they weighing, and what would make them pick one path over another. The guide for designers from Nagoya Studio leads with a plain question: what story is the data really telling, and have you checked your assumptions about the audience. Answer that first and the chart type almost picks itself.
The tool does not save you here. Michael Sandberg's Data Viz Blog is built around one idea: get business partners excited about their own data, which only happens when the chart speaks to their call, not yours. A fancy tool pointed at the wrong question is still the wrong chart.
Match the chart to the question, not your taste
Once you know the decision, the shape of the chart is a practical call. Is this a trend over time, a comparison across groups, a part of a whole, a relationship between two things? Each has a chart that reads fast and ones that read slow. Pick the one the audience can decode in a glance.
You do not need a heavy stack to get there. Storytelling with Data makes the point that custom, bespoke charts come out of PowerPoint and Excel with a bit of know-how, not expensive software. The constraint is useful. When you can only make simple shapes, you are forced to cut the clutter and keep the one line that carries the point.
Sketch rough, test, then polish
The mistake is building the pretty version first. You pour hours into a polished chart, show it, and learn the framing was wrong. Nagoya Studio's sequence is the fix: sketch, test your assumptions, get feedback, then polish. Rough sketches are cheap to throw away. A finished dashboard is not, so you defend it instead of fixing it.
Nadieh Bremer's path shows the same habit at scale. In her account of becoming a dataviz designer, she made "hundreds of super simple and ugly plots" she never kept, just to feel out what shape fit what data. The keeper came when she rebuilt a complex chord diagram into a visual that "slowly explained how to interpret the insights." The polish was last, after the story worked.
Get a second set of eyes before the stakes are high
You are too close to your own chart to see where it confuses. Someone who has not stared at the data will hit the snag in two seconds. Build a cheap feedback loop before the meeting that matters. Bremer leaned on the online dataviz community and conference talks to sharpen her work. You can do the same with faster tools: communities like r/dataisbeautiful exist to give quick critique on a chart, and steady sources like Nathan Yau's FlowingData show how experts frame a dataset so you can borrow patterns instead of inventing them.
Worth remembering: the goal is not a prettier chart, it is a clearer decision. If a colleague reads your draft and cannot say what you want them to do, the data lost. The Dear Data project by Giorgia Lupi and Stefanie Posavec is the far end of this craft, two people hand-drawing a year of personal data into postcards anyone could read. The lesson for your team is not to draw by hand. It is that a clear story beats a clean tool.
Three questions for your team
- What is the one decision this chart should move, and who makes it? If you cannot name it, the chart is a report, not a tool.
- Did we sketch and get feedback before we polished, or did we defend a finished version? Build the cheap loop first.
- Can someone outside the data read this chart and tell us what to do? If not, rework the point before the meeting, not after.



