People Don't Read Data. They Read What Their Brain Can Process.

The data already existed. It was being collected, distributed, and shared regularly. The information was accurate, available, and communicated on schedule.

Yet it wasn't changing behavior.

The interesting question wasn't whether the data was correct. It was why it wasn't landing with people.

Instead of changing the analysis, I changed the way the information was presented. The same underlying data became an interactive visual experience designed to make key insights immediately recognizable, rather than requiring people to search for them.

The response changed almost immediately. People engaged with it faster. Conversations shifted from finding information to discussing what the information meant. The data hadn't changed. The experience had.

That sent me down a research rabbit hole into something psychologists and cognitive scientists have studied for decades. John Sweller's Cognitive Load Theory holds that people have a limited capacity for processing new information at any given time — when unnecessary effort goes into just locating or interpreting something, less capacity remains for actually deciding what to do about it.

There's a related idea called processing fluency: information that's easier to perceive and understand tends to feel more approachable, and often more credible, simply because it's easier to take in. Fluency isn't truth, and it shouldn't be mistaken for it — but it does shape whether people engage with information in the first place.

Design researcher Donald Norman has argued that good design isn't decoration. It reduces the friction between people and the task they're trying to accomplish. The goal was never to make the information prettier. It was to make understanding easier.

That distinction matters, and it's the actual breakthrough here — not a different technology, not swapping one report for another. The real constraint wasn't the availability of information. It was the amount of effort required to turn that information into understanding.

That realization changed the question I was asking. Not "how can I build a better report," but "what prevents people from engaging with information that already exists?"

For me, that question extends well past dashboards. It applies to leadership, communication, education, AI, and every system that depends on people actually making decisions. Sometimes the most valuable improvement isn't creating more information. It's reducing the friction between information and understanding.