This blog post is Human-Centered Content: Written by humans for humans.

In Part 1 of this series, I made the case that data transformation starts with leadership, not technology. We talked about what it takes to build the right foundation: Starting with clarity of purpose before a single platform is selected, getting your organization aligned on shared definitions and understanding why leadership is the engine that drives all of it. If you have not read it yet, go do that first. I will wait. 

The Dashboard Graveyard Is Real (And I Have the Horror Stories to Prove It)

I have built gorgeous dashboards. Ones I was genuinely proud of. Ones where I stayed late getting everything right, obsessing over the layout, the organization of information, stress-testing every filter. And I have watched some of them quietly die. 

I have also watched it happen from the other side, at organizations across healthcare, banking, casino operations and financial services. Someone builds a beautiful dashboard. We are talking weeks of work. The data is clean. The visuals are polished. The filters are chef’s kiss. It goes live with a big email announcement and probably a Slack celebration gif. 

Six months later? Crickets. Nobody is using it. 

Why? Because handing a dashboard to a decision-maker and saying, “Here is your data, good luck!” is not storytelling. It is data dumping. And data dumping puts all the analytical heavy lifting on the person who already has the least amount of time to carry it.  

I have literally sat in meetings (real meetings, with real executives, at real companies) where a perfectly good dashboard was on the screen and the entire room turned into a rapid fire of questions. “What does this number mean?” “Why does this look different from last week?” “Which metric should we actually be focused on?” Ten minutes of confusion before someone finally said “So… what are we supposed to do with this?” 

That is not a technology failure. That is a data storytelling failure. And it is painfully common. 

My colleague Caleb Toews said it well in “Your Dashboards Are Great. Does Anyone Know How To Use Them?“ The gap is almost never the dashboard itself. It is the space between “Here is the data” and “Here is how to actually get value from it.” 

And this is not some niche edge case. Our team has documented the pattern extensively in the “Maturing Analytics: Why Dashboards Fail“ series. Technically solid dashboards miss the mark constantly because we build to the data, not to the decision. Every. Single. Time. I have seen it happen with financial services companies all the way through logistics companies. The industry changes. The pattern does not. 

The fix starts before a single visualization is built. It starts with a leadership mindset that our team has formalized as User-Centered Dashboard Development: Start with the users, not the data. What decisions do they need to make? What questions need answering? Build to those outcomes, and, I promise, the adoption problem largely solves itself. 

Okay But What Does “Data Storytelling” Actually Mean?

I am glad you asked! (I am choosing to believe you asked.)  

It always comes down to four questions. Data storytelling is the practice of structuring and presenting data in a way that guides your audience to an insight and, ideally, to a decision. It answers four questions in sequence: 

1. What happened? 
2. Why did it happen? 
3. What does it mean for the business? 
4. What should we do next? 

I have used this framework across every industry I have worked in, from mortgage operations to hospitality, and the questions are always the same. The data changes. The business context changes. But a decision-maker who cannot answer those four questions from the report in front of them is not going to make a confident decision from it. They are going to schedule another meeting. 

When those four questions are answered through the data itself, before a leader ever opens their mouth in a meeting, the entire energy in that room shifts. Instead of everyone asking, “What does this mean?” the room is already debating “Given what this means, what do we do?” I have personally watched that shift turn a 45-minute, going-nowhere debate into a crisp 10-minute decision. Not because the data got better. Because the story around it did. 

It is not magic. It is not rocket science. It is just really, really good storytelling. 

There is a reason my colleague compared great dashboarding to great music in the “Dashboarding Is Like Music“ series. (It is a great read, go check it out.) The way you organize and sequence information, whether in sound or in data, is what guides your audience toward the insight you want them to reach. The story is not just in the data. It is in how the data is arranged, framed and presented. 

This Is a Leadership Responsibility, Not Something You Can Just Delegate to the Data Team

More often than not, I have seen where data storytelling is treated like it is purely a design or analytics function. “The data team will make the dashboards tell a story.” And look, the data team absolutely plays a role (a big one!), but the most important ingredient is leadership intent. Always. 

I say this as someone who has been on that data team. I have built technically excellent dashboards and reports and sent them into a vacuum because nobody told me what decisions it was supposed to support. So I guessed. I built to what I thought leadership wanted. Leadership got my best guess instead of their actual priorities. Nobody won, and I learned that lesson the hard way. 

The data team cannot give leadership what leadership has not defined. The most important question in any analytics initiative is not a technical one: It’s, “What decision are we trying to enable?” That is a leadership question, and it needs a leadership answer before a single visualization is built. Everything else (the visuals, the narrative, the context, the framing) flows from that clarity. Without it, the data team fills the void with their best guess. And guessing produces dashboards that live in the graveyard we talked about earlier. 

Then there is the other kind of leader. The ones who are deeply engaged in knowing what decisions they want to enable, who push back on visuals that are technically correct but narratively confusing, and who refuse to share a report until it actually answers the question it was built to answer. I have had the privilege of working with leaders like that, and the difference is not subtle. Those organizations move faster, make sharper decisions and build data cultures that actually last. That is not a coincidence. That is what intentional leadership looks like in practice. 

Change Management: The Part Everyone Skips and Then Wonders Why It Did Not Work

Getting the storytelling right is one thing. Getting people to actually embrace a new way of working with data? That is a whole other mountain to climb. 

And here is the part that gets me fired up, because I have watched organizations spend millions on a perfect technical implementation only to have it quietly fail on the human side. I have seen Snowflake migrations go live flawlessly (beautiful architecture, clean data, the works) and then watched teams immediately go back to exporting everything to Excel because nobody explained why the new approach was better. Nobody brought people along for the ride. 

The technology worked. The change management did not. And nobody talked about it like it was the disaster it actually was. 

User adoption and ROI are consistently the top challenge for data and analytics leaders, and the User Adoption and ROI deep dive from our team spells out exactly why. Neither of these things happen on their own. Both require deliberate leadership investment. 

I have lived this from both sides. When I led a 21-person analytics team, I watched adoption numbers climb when we communicated the “why” clearly and trained people in ways that actually met them where they were. When we skipped that part, even technically beautiful work went unused. The difference was never the technology. It was always the people strategy wrapped around it. 

Treat adoption as a deliverable, not an afterthought. Successful data transformations invest just as much energy in the human transition as the technical one. That means clear communication about what is changing and why. Training that actually meets people where they are (not a two-hour Zoom demo nobody asked for). When I led cross-functional training initiatives at one organization, analytics fluency and tool adoption grew significantly across operations, finance and executive teams. The platform did not change. The people strategy did. And that is exactly what made the difference, because we treated adoption as a deliverable, not an afterthought. 

Every single time a team uses a new dashboard to make a faster, better decision, that is a story worth telling internally. Share it. Celebrate it. Make it part of your culture narrative. Those moments compound, early adopters become advocates, skeptics become believers and what started as a technology rollout gradually becomes an actual culture shift. That is the magic. 

This is not just a BI problem either! Our team wrote about the exact same pattern in the context of AI rollouts in “Your AI Pilot Isn’t Stalled Because of the Technology,” which is worth a read no matter what kind of platform change you are navigating. And if you want a practical playbook for building the data culture and user adoption strategy around all of this, our Data Enablement Field Guide is free and genuinely worth your time. 

Trust: The Thing That Holds All of This Together

None of this works without trust. And trust in data is not something you can assume. It is earned slowly and deliberately through consistency and transparency. 

I spent years in highly regulated industries where bad data was not just an inconvenience. It was a real, genuine compliance risk. In banking and financial services, a wrong number in a report is not a minor embarrassment. It can have real operational and regulatory consequences. That experience shaped how seriously I take data trust, and how personally I feel it when organizations treat it as an afterthought. 

I have watched organizations lose years of hard-won progress because one bad number made it into an executive presentation. All it takes is one inaccurate dashboard to undermine the value of data. Suddenly nothing is trustworthy. Every report came with a disclaimer. Every meeting opened with “But are we sure these numbers are right?” That kind of doubt, once it gets in, is extremely hard to shake loose. I have seen it take 12 months to rebuild confidence after a single data quality incident. Twelve months. 

Leaders build trust in data the same way they build trust in people. By showing up consistently, being transparent about where the data comes from and what its limitations are and creating an environment where questioning the numbers is encouraged, not career-limiting. That is a cultural commitment. It has to come from the top. And it has to be modeled, not just mandated. 

What It Looks Like When It Is Actually Working

I know what it looks like when it is working. Not because I read about it. Because I have been there, done that. Let me paint the picture. 

The meetings are different. Leaders arrive already oriented. Nobody is debating whose numbers are right because the data is telling a clear story and everyone trusts it. The conversation moves straight to the decision.  

I know this because I lived it. At one organization, I led the redesign of the reports, drove the change management, and worked side by side with users until the data was actually answering their questions and helping them make real decisions. Stakeholder engagement jumped 60% in three months as a direct result. Not because the data changed. Because the story did, and because bringing people along was never an afterthought. 

That is the confidence this series is about. The kind that is earned through intentional data storytelling, deliberate change management, and a leadership team that treated both as non-negotiable. It is absolutely achievable. 

You Do Not Have to Figure This Out Alone (Seriously, Do Not)

This journey asks a lot. The technology decisions alone are complex enough. Layering leadership alignment, change management and data storytelling on top of that is genuinely a heavy lift for any internal team, no matter how talented they are. 

That is exactly where the right partner changes the equation. 

At InterWorks, we have walked this with dozens of organizations, from Snowflake and Sigma migrations to Tableau Cloud transitions, agentic AI consulting, and full data solutions. We know the technology deeply. But what we have learned, over and over again, is that what actually determines whether a client succeeds is not the quality of the implementation alone. It is whether the right leadership framework is in place, whether change is being managed with intention, and whether people feel genuinely supported at every stage of the journey. 

We do not just help organizations implement technology. We help them get everything out of it. 

The confidence is achievable. The journey is worth taking. And done right, you do not have to take it alone. 

Up next in the series: Part 3 pulls back the curtain on what you really get when you partner with InterWorks, the people, the expertise, and the culture that makes the difference between a technology implementation and a true transformation. 

Ready to start your own journey from chaos to confidence? Reach out to the InterWorks team and we would love to have that conversation.