Last week, Nick Lisauskas posted an NFL-style scouting report comparing data stack tools to football teams. Snowflake as the Kansas City Chiefs, Omni as the Cincinatti Bengals, Excel as the Pittsburgh Steelers. It was meant to be a quick, fun take on the tools we use every day.
What we didn't expect was the response. Within hours, the post had dozens of comments and reactions, and people adding their own comparisons. Data professionals (and importantly, non-data professionals) jumped in with suggestions: "Oracle = Jets," "BigQuery = Buffalo Bills," "The Bears are basically a TI-83."
What stood out, though, was that a simple sports analogy got more people talking about data tools than most technical deep-dives ever do. And that’s not an accident.
Why This Matters More Than You Think
As data professionals, we spend most of our time translating complex technical concepts into language that stakeholders can understand and act on. The difference between a data team that drives decisions and one that just produces reports often comes down to communication.
Yet somehow, we treat communication as an afterthought. We perfect our SQL, optimize our pipelines, and build beautiful dashboards because those behaviors lead to immediate gratification of a “job well done”. But then, we present our findings with dense technical language and wonder why our deliverables never get put to good use.
The NFL post worked because it took something abstract (the relative strengths and weaknesses of data tools) and made it concrete (teams a lot of people clearly already have strong opinions about). People didn't need to understand the technical nuances of Snowflake's architecture to grasp that it's the current champion that "makes the impossible look easy."
The Science Behind Sticky Ideas
Belive it or not, there's actual research backing this up. In "Made to Stick," Chip and Dan Heath identify six principles that make ideas memorable: simplicity, unexpectedness, concreteness, credibility, emotions, and stories. The sports analogy hit most of these marks.
It was concrete (everyone knows what the Chiefs represent), emotional (people have strong feelings about their teams), and structured as a story (each tool had a narrative arc). Most importantly, it was simple. Instead of explaining Snowflake's multi-cluster shared data architecture, I said it was like Patrick Mahomes. Done.
But this isn't just about social media engagement. The same principles apply when you're presenting quarterly results to the C-suite or explaining a data quality issue to your operations team.
Practical Applications for Your Data Team
Start with what they know. When explaining machine learning to a sales team, don't begin with algorithms. Start with how they already qualify leads, then show how ML amplifies that process. If you're talking to finance about data governance, frame it in terms of SOX compliance - something they already understand and care about.
Use concrete examples over abstract concepts. Instead of saying "we need better data lineage," tell the story of the time a dashboard showed conflicting revenue numbers and it took three days to trace the source. Instead of explaining dimensional modeling, show them how they currently struggle to answer "what was our performance last quarter versus the same quarter last year" and how proper modeling makes that question trivial.
Build bridges, not walls. The worst data presentations are the ones that make the audience feel stupid. The best ones make them feel informed. Your job isn't to showcase how much you know about statistics or database design. It's to help them make better decisions.
Test your explanations. If you can't explain your analysis to someone outside your team in under two minutes, you probably don't understand it well enough yourself. Practice your explanations on colleagues, friends, or family members. If they get confused, your stakeholders will too. For a long time, this even applied to how I answer the simple question “what do you do?” - the person I was speaking to was usually lost in seconds, but I’ve learned better ways to answer this question that the majority of people can connect with like “I build company dashboards and scorecards” or “I help people make business decisions with data”. Even if it feels like trivializing the work you do a bit, it’s much easier for the person to connect with.
Test It Out
Next time you're preparing a presentation or writing a report, try this exercise: pick a completely unrelated domain that your audience knows well (sports, cooking, parenting, whatever) and see if you can explain your key points using analogies from that world. You probably won't use all of them, but the exercise will force you to think about your findings from a different angle.
Even better, ask yourself: if I had to explain this concept to my 12-year-old cousin, how would I do it? Kids are excellent BS detectors. If your explanation relies on buzzwords or circular logic, they'll call you out immediately.
The Bottom Line
Data communication isn't a soft skill. It's a core competency. In a world where every company is supposed to be "data-driven," the teams that actually influence decisions are the ones that can make complex concepts feel obvious.
Whether you're using football metaphors or restaurant analogies or just plain English, the goal is the same: take what you know and help others understand why it matters. Do that well, and you'll find that your perfectly crafted analyses actually get used instead of filed away.
Sometimes the most skillful thing you can do is explain something simply.
Thanks for reading! Want more? Check out our blog and our YouTube channel for deeper dives and walkthroughs. We'll be back each week with more content - subscribe to stay in the loop.
#DataCommunication #Analytics #SouthShoreAnalytics