The problem
A board member asks how many first-time donors you had last quarter. A manager wants a count of open cases before a meeting in ten minutes. A salesperson wonders which of their accounts haven't had any activity in a while.
Each of these is a reasonable question. In many organizations, each one becomes a report request, and the report gets built, used once, and forgotten. Over time you end up with hundreds of reports, most of which nobody can find or trusts.
Why it happens
Reports are the main way Salesforce answers questions, so every question starts to look like a report. But reports and questions aren't the same thing.
A report is a saved, repeatable view. It's valuable when you'll look at the same thing again and again, in the same shape. A question is often one-time, specific, and likely to change the moment you see the answer: "OK, now just the big ones."
Using a report for every question is like printing a spreadsheet every time you want to check one number.
When to use what
A simple way to decide:
- Build a report or dashboard when you'll check the same thing regularly (weekly pipeline, monthly giving, case volume), when several people need the exact same view, or when it feeds a meeting or a board packet.
- Just ask a question when it's a one-time need, when you'll probably want to adjust it as you go, or when you only need a number or a short list right now.
- Save the answer when a question you asked turns out to be one you'll ask again. That's the moment it's earned a place.
Most teams find that the majority of their day-to-day questions fall in the middle group. Those are the ones clogging the admin's inbox.
A simpler approach
Keep reports for what you track. For everything else, make it easy to ask.
When people can ask a question in plain English and refine it as they go ("only this year," "only mine," "top 10"), fewer one-off reports get built, the ones that exist stay meaningful, and your admin gets time back for work that matters.
Where Hank fits
Hank answers everyday Salesforce questions in plain English, right inside Salesforce, with a chart when a picture helps. You can keep refining the question without rebuilding anything.
If an answer turns into something you check often, save it as a live view: it refreshes with current information every time you open it, without building a report. Hank doesn't replace your reports and dashboards. He covers the questions in between.