If you give a board member a cookie

If you give a board member a dashboard, they’ll probably ask for a report to go with it.

And when you give them that report, they’ll want a trend line.

Then, when they see the trend line, they’ll ask, “Can we segment that by region?”

And once you show them the regions, they’ll wonder how it breaks down by product.

Before you know it, you’re building a full-blown analytics suite… and it all started with one little cookie.

The Parable of the Dashboard Cookie

Data professionals, Salesforce admins, and BI teams everywhere know this story well.

You spend days perfecting a clean, beautiful visualization — something simple, elegant, and insightful. You share it at the board meeting. Eyes light up. Heads nod. Someone says, “This is amazing.”

And then comes the fateful phrase:

“Can we just add one more thing?”

The next thing you know, your “quick win” dashboard now needs five filters, three comparison metrics, a drill-down by month, and integration with a third-party data source that no one’s touched since 2018.

Why This Happens (and Why It’s Actually a Good Sign)

The truth is, this is what success looks like. Curiosity is contagious.

When leaders start asking for more data, it means your visualizations are working. You’ve sparked insight, created engagement, and shown the power of data storytelling.

The problem isn’t that people want more, it’s that we often fail to set boundaries and context for what “more” means.

How to Manage the Cookie Monster Effect

Here are a few ways to keep your cookie jar from emptying too fast:

  1. Start with strategy, not sugar.
  2. Before building a dashboard, define what question it should answer and who it’s for. Dashboards built without intent become cookie platters.  Everyone grabs one, but no one feels full.
  3. Create a “Data Menu.”
  4. Instead of building ad-hoc reports, offer a curated menu of analytics options. Label them like entrees: “Executive Overview,” “Sales Pipeline,” “Customer Health.” This helps stakeholders understand what’s already available.
  5. Educate with empathy.
  6. Remember, their “one small request” probably sounds small to them. Explain the impact in time, complexity, or data quality and suggest better alternatives when possible.
  7. Establish data governance early.
  8. Have a defined process for new report requests. It keeps enthusiasm from becoming chaos.
  9. Celebrate curiosity.
  10. When your board wants more cookies, it means they trust you as the baker. Keep that enthusiasm alive, just don’t let it turn into a sugar crash.

The Moral of the Story

“If you give a board member a cookie,” they’ll want a glass of data to go with it.

But if you build your data foundation right: with clear goals, accessible dashboards, and a culture of curiosity, that hunger for insight becomes your organization’s greatest strength.

Contact Us