Companies spend thousands of dollars and hundreds of hours building reports that nobody ever opens. In boardrooms and team chats, managers ask for data, yet the reports they get rarely change how they run the business. “There’s a dashboard in your company right now, sitting there, beautifully built, wondering why nobody calls up and says, ‘How are you doing?’ anymore,” says Josh Silverbauer, Head of Analytics & Conversion Rate Optimization at Intrepid Digital. After ten years working with tools like GA4, Tag Manager, and customer data platforms, he sees this waste of time as a common problem in both established firms and early-stage companies.
Building for Choices Instead of Clutter
Most reporting projects run into trouble right at the start because teams try to show everything they can track. When analysts fill screens with dozens of charts simply because the numbers exist, they end up confusing the people who need clear direction. “It took weeks to make. It’s got bells and whistles, and yet none of it matters. No one cares about your dashboard, and I’ll tell you why,” Silverbauer explains. Instead of helping leaders act quickly, these cluttered views push people to ignore the data and rely on gut feelings.
Fixing this problem starts by asking what actions the report is supposed to guide. Analysts need to know who will use the screen and what real-world problem they want to solve before adding a single chart. “Firstly, build the dashboard around a decision, not around whatever data happens to be lying around,” Silverbauer says. “Ask what choice this thing is supposed to inform and who is making it.”
Different roles inside a company need completely different views of performance. A finance chief looks at broad costs and long-term margins, while an ad buyer cares about daily click costs and creative testing. “A media buyer needs something wildly different from a chief financial officer (CFO),” Silverbauer notes. “Start there, and the tile count usually cuts itself in half without any hard feelings.”
Telling Stories Instead of Assigning Homework
Showing bare metrics without context leaves too much work for the reader. When executives see a random dip or spike on a screen, they have to stop and figure out what went wrong on their own. “A number sitting alone on a slide is asking people to do homework. And people are really good at not doing homework,” Silverbauer points out. If an analyst fails to explain what the data means, the team will simply move on to other tasks.
To make numbers stick, reports need a clear three-step narrative that highlights what is at stake. The analyst must show what the baseline was, what changed, and what will happen if the team does nothing. “So say what you expected, say what’s actually happening, and say what it costs to ignore it,” Silverbauer advises. Framing numbers this way gives managers a clear reason to take action before small issues turn into expensive mistakes.
A well-told story travels through an organization much faster than a complicated spreadsheet. When a report is simple enough for one person to summarize easily, other leaders start sharing it across the company. “That’s the version somebody repeats in a meeting you weren’t invited to, which is honestly the highest form of analytic success,” Silverbauer explains. That level of word-of-mouth adoption shows that the data is finally guiding real business strategy.
Getting Marketing and Engineering to Speak the Same Language
Another breakdown happens when technical teams and growth teams try to collaborate on data setup. Marketers talk about user interest, signups, and sales goals, while developers talk about code events, database tags, and server limits. Because each team uses different words for the same ideas, they often walk away from meetings thinking they agree when they do not.
That gap leads to tracking systems that fail to measure what matters to the business. “Marketing asks in outcome language, engineering hears technical language. Everyone nods confidently, and then three months later, the data is useless,” Silverbauer says. By the time anyone notices the mistake, weeks of developer time have gone to waste.
To prevent that waste, someone must translate business goals into technical requirements before any code goes live. Having that shared understanding early ensures the tracking setup actually captures the numbers marketing needs. “Someone has to speak both dialects, ideally before the tagging goes live,” Silverbauer notes. Doing this work up front saves teams from costly rebuilds later on.
Earning Attention Before Asking for Budget
Silverbauer takes an unconventional view of data work, drawing on his experience outside the technology world as a songwriter. His creative work includes writing musical pieces about the data industry, which shapes how he views communication between teams. “I also write music, including a full rock opera about the analytics industry, which tells you either everything or nothing about how I approach this work,” he says. For him, data presentation is about holding human attention rather than showing off technical skill.
Whether leading a large corporation or running an early-stage company, executives should demand tools that save time rather than add friction. Fancy charts and complex software mean nothing if team members never look at them to make choices. “Good analytics has to earn attention before it earns budget,” Silverbauer concludes. “Make it worth someone’s afternoon, and you will create true value.”
By keeping screens focused on real decisions, framing data as a story, and bridging team communication gaps, companies can fix their unused reports. Analytics should not feel like extra homework for busy staff. When data teams focus on making life easier for decision-makers, their work turns into a clear asset that drives growth.
Follow Josh Silverbauer on LinkedIn for more insights on analytics strategy, data storytelling, and bridging the gap between marketing and engineering.
