I think the framing should be around what makes sense on a dashboard, not how many metrics total that the entire company (or whatever cohort) wants to collect.

I think the framing should be around what makes sense on a dashboard, not how many metrics total that the entire company (or whatever cohort) wants to collect. A dashboard should not distract from what you're trying to do. It should show only the information you really need [1] so that you can focus on actually driving. I worked at one company where we had so many signals on ours that it looked like the dash of a 747 [2] to me. Pilots go through a lot of training and tests to show that they understand those and how to respond to different scenarios! Software startups are a bit more seat-of-pants than that. We can have dashboards for different purposes and roles, for different activities we want to drive. But the dashboards should focus on use. And if there are metrics that don't fit on any of the dashboards, they're not about driving anything - maybe consider scrapping them. [1] https://www.pinterest.com/pin/58054282668632186/ https://www.pinterest.com/pin/58054282668632186/ [2] https://www.reddit.com/r/cockpits/comments/ayr4z7/boeing_747200_cockpit/ https://www.reddit.com/r/cockpits/comments/ayr4z7/boeing_747...