🙅♀️ Stop making your team open apps
For years I assumed self-serve analytics was the answer: build good dashboards, give everyone access, and the curious ones will look.
Turns out almost no one looked. We had dashboards with 3 lifetime views, and we're a data company (embarrassing to admit).
What actually got read was a Slack message every Monday with the numbers already in it. Zero clicks required.
So I've mostly changed my mind: if a metric matters, push it to where people already are. We leaned into this hard enough that we launched dashboard subscriptions today, so clearly I've picked a side.
But I get the counterargument. Push turns into noise fast, people filter the email by week 3, and pull at least guarantees that whoever's looking actually wanted to know.
Where did you land? Do the metrics go to your team, or does your team go to the metrics?
Check out our launch for Basedash Subscriptions here and let me know what you think!
Replies
This is such a relatable struggle. We tried both and eventually realized it depends on the team. Execs want push (just give me the number), analysts want pull (let me explore), and PMs want a mix.
One thing I'm really curious about—how do you handle the 'noise' problem with your new subscriptions? Do you limit frequency, or is it fully user-configurable? Because if I get pinged for every micro-metric, I'm out. But a well-curated weekly summary? I'm in.
Basedash: AI data analyst
@yosephbet up to the user how often they want to receive it. But we also have a feature called Automations that generates a report with AI and allows the agent to skip if there’s nothing important to report.
@maxmusing Appreciate that, Max! Frequency control + a smart "skip if nothing important" is exactly what I have planned for SelamDesk's weekly reports. Just kept it off the MVP to ship the live agent first, but it's next on my list. Great to see Basedash thinking the same way!